Advantages and Disadvantages of Project Network Diagram

Document Sample
Advantages and Disadvantages of Project Network Diagram Powered By Docstoc
					Assignment 1                                              ISYS302                                                           2009


                       ISYS302 Management of IT Systems and Projects

                                                   Assignment #1

                                      Due Date: 4p.m. 3trd April 2009
This assignment will be composed of three components; an MS Project section; a MS
Sharepoint/webpage section and a written report.


                                       Part 1: MS Project (50%)
The following table comprises the scope statement of the project.

Scope Statement
    Project Title: Inox Industries Expertise Finder system implementation
    Date:       Mar 6, 2009 Prepared by Dr. Peter Busch, Chief Metallurgist, Inox Industries
    Project Justification: Inox Industries is a steel making firm that specializes in stainless steel production, as
    its name suggests. The firm employs 300 people; 10 staff comprise management, the R&D section and the IT
    support section employee 50 staff members (40 staff members comprise the R&D section; 10 staff members
    make up the IT support group). The remaining 240 staff are directly concerned with steel manufacture on the
    ‘factory floor’.

    Senior management at Inox Industries have suggested this project as a means of garnering expertise that exists
    in the firm with regard to steel marking processes. Steel production at Inox is 10% below the national steel
    production average for a firm of comparable size. To remain competitive Inox needs to draw better upon the
    knowledge that exists in their firm. Estimated savings are expected to be $1000/employee per year for five
    years.

    Expertise recommender systems attempt to capture the expertise of knowledgeable people within a company
    so that other less experienced personnel can make use of this knowledge in their day to day tasks. For the
    longer term future of the organisation, the knowledge stored in expertise recommender systems aids to their
    strategic advantage.

    You are the project manager, you are one of the 10 IT staff, you have another 9 IT staff who can help you with
    this system implementation.
    Product Characteristics and Requirements:
    1. The expertise recommender system must run on the company’s existing intranet using current hardware
         and software as much as possible.
    2. The new system should be user friendly.
    3. The main requirements of the system are to:
              • Allow potentially all employees to access stored expertise in areas of steel making, molecular
                   structure of steel, tensile strengths of different steels, areas of application where particular steel
                   types would be utilized and so forth.
              • The expertise recommender system should also enable staff to determine which of their
                   colleagues have expertise in specific areas, should the system itself not store such specialised
                   knowledge.
              • The system should be up to date insofar as staff who may have left the company are so recorded,
                   meaning that expertise may need to be sought from outside the organisation.
              • The system should provide all location details for current staff, including their position
                   description and biographical information.
              • Provide a means for staff to enter areas of expertise they may have. Such expertise descriptions
                   will be in the form of keywords chosen from a thesaurus in the system; staff will also be able to
                   add vetted keywords, should satisfactory keywords not exist.
    Summary of Project Deliverables
    1.        Requirement definition: Define the requirements for the new system. Included in this development
              stage is interviewing all staff of the organisation on their areas of expertise. Two business analysts
              will be required. Domain experts will need to be approached. There are five domain experts who
              specialize each in a particular area of steel production, however you will need to speak to other staff

                                                           Page 1                                                    Peter Busch
Assignment 1                                            ISYS302                                                         2009

              in the organisation to garner as much expertise as you consider reasonable. A knowledge engineer
              will help you here.
    2.        System design: The expertise recommender system will need to be modeled in UML. You will
              require two business analysts for this role.
    3.        Coding the system: The intranet based recommender system will include steel making information.
              Three programmers are needed. Furthermore a knowledge engineer will be required.
    4.        Testing: Testing is required and will involve one technical analyst.
    5.        Technical writing: One technical writer will write the manuals for the Expertise recommender
              system.
    6.        Training: Training will be provided for the new system, both on-line and in-class. One IT trainer
              will handle the training.
    7.        Roll out and support: There will be a well-defined plan for rolling out the new system, supporting
              users, and providing updates, enhancements, or other support, as required. All IT staff are involved in
              roll out and post implementation support.
    Project Success Criteria: Our goal is to complete this project in 1.5 years for no more than $950,000. N.b.
    this project is not the only activity of the IT team; it is only part of their workload.

    With an expertise recommender system in place, Inox Industries it confident is can increase the efficiency of
    its steel making, and with the savings gained, perhaps even branch out in to more specialised ferrous-alloy
    steel products.

    You have 9 staff available to you to aid you in developing the system; you are the project manager, making 10
    IT staff in total.

1. Implement the above project scope into MS Project 2007. The following form an idea of the
    tasks/subtasks to be implemented. Remember the staffing, cost and timeframe constraints you
    have been provided with (35%):

 Initiating                                                     Modelling in UML
   Form project team                                            Check constraints on models
   Develop project charter                                      Make final decision on platform to be adopted
 Planning                                                      Coding
  Develop project plan                                          Coding
  Develop and refine other plans                                Error checking
  Define risks and risk management approach                     Testing
  Create WBS                                                   Roll Out
 Requirements Analysis                                          Undertake technical writing of completed system
  Define requirements                                           Communicate roll out plan to users
  Evaluate current systems                                      Conduct user training
  Define user requirements                                      Release internal PR
  Define content requirements                                  Support
  Define system requirements                                    Determine what support resources are needed
  Define specific functionality                                 Make appropriate staffing changes
  Interview domain experts                                      Determine support process
  Interview other key personnel                                 Conduct Post Implementation Review (PIR)
  Transcribe interviews, garnering information                 Closing
 System Design                                                   Prepare and deliver final report and presentation

1.1 How long will the project take in days and weeks? Why is this the case? How have you
    calculated this? (5%).

1.2 Compare the advantages/disadvantages of displaying the schedule as a network versus a Gantt
    Chart (5%).




                                                         Page 2                                                  Peter Busch
Assignment 1                                     ISYS302                                                2009

2. Provide the critical path for your implementation. Illustrate your critical path using a sequence
   of nodes and edges along the following lines. You may just use the network diagram feature in
   MS Project to illustrate your point, rather than redrawing from scratch (5%):




              Conduct      8                              3
              interviews                      Analyse
                                              requirements


      Start                4
                                                Investigate                     Produce
                 Investigate                                                                   Finish
                                                packages                        report
                 other
                 systems                                      8             5
                                            Investigate
                                            hardware

                                                          5



       Figure 8.13 Network diagram illustrating durations & critical path (source: Schwalbe 2006).


                                   Steps in undertaking part 1
   1. Implement the project scope into MS Project 2007 with the parameters you have been
      provided, indenting subtasks appropriately.

              a. Use the outline numbering feature to display the outline numbers. For example your
                 WBS should start with
                     i. 1.0 Initiating.
              b. Enter any durations or dependencies.
              c. Show over-allocation and then corrected/leveled allocation of staff workloads.
              d. Show costing (hourly rate) for your staff members.

   2. Create a word document. In part 1 of the document you need to paste in:

              a. MS Project WBS charts, including
                    i. Gantt chart.
                   ii. Network diagram.
                  iii. Resource graphs (before and after showing correction for over-allocations).

   3. Answer questions 1.1 and 1.2 in your Word document.
   4. In the same MS Word document illustrate your critical path (Q.2) for your WBS along the
      lines of the network diagram illustrated above. Be sure to number the days/months etc. so as
      to clearly show why the critical path is what it is (only possible when showing duration of
      tasks).
   5. In the same Word document, write part 3 of the assignment.




                                                  Page 3                                         Peter Busch
Assignment 1                                    ISYS302                                               2009

                              Part 2: MS Sharepoint (25%)
3. Using MS Sharepoint (or another tool), create 5 simple non-dynamic (web) pages profiling your
   domain experts. The keywords in the areas of metallurgy you give your 5 domain experts can
   be used when your company (Inox Industries) actually implements the expertise recommender
   system. Furthermore these pages could be used for social networking in the company. The pages
   will eventually be hosted on the company intranet.

   Paste screen dumps of your pages in the word document as well.

                          Part 3: Written report topic (25%)
4. In the third part of the assignment you will be writing a report of 1,000 words (not including
    your reference list/bibliography). It does not matter if you write more than 1,000 words, it will if
    you write less! I will expect soft and hard copy submitted, so I will be checking the word
    length!

   There have been a number of ‘readings’ over the past couple of weeks. You may use these to
   help you structure your arguments.

   Briefly summarize the works of Maslow, Herzberg, McClellan, McGregor, Ouchi,
   Thamhain and Wilemon.

   How do their theories relate to project management?

   Your report will include at least 7-8 references. Naturally you will have drawn upon these
   references in the BODY of your report, not just listed the references at the end!

   I include the following section to provide you with an idea of writing at academic/professional
   level.




                                                 Page 4                                         Peter Busch
Assignment 1                                      ISYS302                                                 2009

                        Writing at university and in professional life
Writing at university level means academic writing. Academic writing is not like writing a novel.
Informal writing styles are not encouraged. You are required to substantiate what you write/say in
your academic and professional lives. It is only in rare instances where you will be permitted to
write works of fiction at university, it is also for similar reasons that the first person singular (I feel,
I think, I did, My feeling is …), is generally to be avoided in writing university assignments (there
are some exceptions to this rule, for example law faculties often adopt the first-person-singular in
their writing style).

As insulting as this may seem, as a student you are not considered to be an expert at anything (that
usually comes with the title Dr. and then later Professor). The point is you need to state the source
of your information in assignments. Furthermore it is generally considered politically-correct to
avoid gender-specific writing styles; in other words don’t refer to authors/people/whoever as he,
unless they actually are male.

For the purposes of this assignment, we will use the Harvard referencing style, although if you are
comfortable with footnoting, please do so.

                                           Citing vs. quoting

      1. Where an idea is ‘adopted/adapted’ from an author but restated in your words one uses
         citing as a means of establishing where the information was derived from. For example

          …… Smith (1990) was inclined to believe that … blah blah blah, … (where blah blah blah
          are your words, but the author’s ideas). No page number needs to be included for citing
          authors (but you must include the author’s surname, and date of publication of the
          reference where you have derived the information from).

          No, you cannot cite your friends (or lecture/tutorial/practical material).

      2. Where the words have simply been lifted/copied directly by you, is referred to as quoting
         someone. For example ….. it was felt that “of all the database schemas, the object
         relational approach is …..” (Zhang 1990 p. 53). In this case quotation marks are used as
         well as a page number stating where the information directly came from.

      Where you have quote that is longer than say 20 words, you indent these as a separate
      paragraph from the main body of your text and you single space the block quote, like so

          When faced with a small problem domain, system development can be all about
          modeling of user functional requirements. However, when faced with a large
          problem domain, such as with an enterprise information system, system
          development must recognize the demands placed on it by the non-functional system
          qualities. The quality of interest in this paper is supportability (Maciaszek and Liong
          2003; Maciaszek et al. 2004). Supportability is really the combination of three
          qualities – understandability, maintainability and scalability. An unsupportable
          system is a legacy system (Maciaszek 2005 p. 17).

      Note, no quote marks are necessary, but you still include author surname, year of publication
      and page number.

      You do not need to italicise block quotes (or normal quotes for that matter).

                                                   Page 5                                          Peter Busch
Assignment 1                                   ISYS302                                               2009


Lecture notes/course notes (and ideally even textbook citations), DO NOT count as
references!! These are not to be referred to in written assignments/reports (this is considered
amateurish).

                                          Report structure

The word processed report will include

       - table of contents
       - sub-titles
       - list of references OR bibliography

Please note: a list of references includes just those specific references you cited and/or quoted from,
whereas a bibliography includes the references as well as any other texts (electronic or paper) you
may have used in producing the assignment (e.g. you may have looked up a word in a dictionary).

The assignment should be space and a half or double-spaced.

The reference list or bibliography should be single-spaced.

Your paragraphs may either be left-aligned or justified.

                                    Bibliography/Reference list

The minimum level of detail for each book/journal reference used in either a list of references or
bibliography is as follows.

For a book:

     Busch, P., (2008) Tacit Knowledge in Organizational Learning IGI-Global Hershey
          Pennsylvania U.S.A.

For a journal article/conference paper:

     Richards, D., Busch, P., Venkitachalam, K., (2007) “Ethnicity-based cultural differences in
             implicit managerial knowledge usage in three Australian organizations” Knowledge
             Management Research and Practice 5(3) pp:173-185.

For electronic publications (e.g. ones you’ve pulled off the internet):

      Busch, P., (2002) “The 1831 pattern British General Officers Ivory Hilted Scimitar” The
              Oakeshott Institute URL: http://www.oakeshott.org/1831art.html (accessed on 7th.
              March 2009)

      Busch, P., (1999) “Historical swords: The 1828/65/68 Pattern Highland Officers Basket
              Hilted Broadsword” Swordforum Magazine Online Fall URL:
              http://www.swordforum.com/fall99/1865.html (accessed on 7th. March 2009)

At the end of your assignment, you simply place all types of references together in alphabetical
order of author surname. You do not list them separately by book, conference paper and electronic
publication.


                                                Page 6                                         Peter Busch
Assignment 1                                    ISYS302                                              2009

                                       Number of references

As third year students, I would expect to see at least 7-8 references in your reference list (more if a
bibliography), meaning you have also cited or quoted from these references within the body of your
report (not just pasted some references at the end of your report, without referring to them within
your report!!).

I WILL mark you down if you are not citing or quoting!!

                                         Your reference list

Your reference list/bibliography (note there is a difference) could include some of the following
(note my formatting for references … this is what you have to do for your references too!!).

Ahituv, N., Zviran, M., Glezer, G., (1999) “Top management toolbox for managing corporate IT”
           Communications of the ACM 42(4) April 1999 pp. 93-99 .

Ben-Menachem, M., Gelbard, R., (2002) “Integrated IT management tool kit” Communications of
         the ACM 45(4) April pp:96-102.

Brewer, J., (2005) “Strategies for making connections with industry: Project managers: can we
           make them or just make them better?” Proceedings of the 6th conference on Information
           technology education SIGITE October pp. 167-173.

Brock, S., Hendricks, D., Linnell, S., Smith, D., (2003) “A Balanced Approach to IT Project
           Management” Proceedings of the 2003 annual research conference of the South African
           institute of computer scientists and information technologists on Enablement through
           technology SAICSIT '03 South African Institute for Computer Scientists and Information
           Technologists pp. 2-10.

Gowan, A., Mathieu, R., (2005) “The importance of management practices in IS project
          performance: An empirical study” Journal of Enterprise Information Management
          18(2) pp. 235-255.

Peslak, A., (2006) "The Impact of Personality on Information Technology Team Projects" SIGMIS-
            CPR’06 April 13–15th Claremont California USA pp. 273-279.

Roy, V., Bernier, C., Léveillé, L., (2006) “The high wire balancing act of the IS project director”
          ACM SIGMIS Database 37(1) Winter Pages: 8-39.

Sauer, C., Liu, L., Johnston, K., (1999) “Enterprise-level project management capabilities: a
           comparison of the construction and IT services industries” Proceeding of the 20th
           International Conference on Information Systems Charlotte, North Carolina pp. 440-
           445.

Sauer, C., Southon, G., Dampney, C., (1997) “Fit, failure, and the house of horrors: toward a
           configurational theory of IS project failure” Proceedings of the eighteenth International
           Conference on Information Systems (ICIS) Atlanta, Georgia pp. 349-366.

Seddon, P., Graeser, V., Willcocks, L., (2002) “Research Contributions: Measuring
           organizational IS effectiveness: an overview and update of senior management
           perspectives” ACM SIGMIS Database 33(2) June pp: 11-28.



                                                 Page 7                                        Peter Busch
Assignment 1                                      ISYS302                                               2009

                                            Deliverables
                                               Soft copy
1. One MS Project (2007) file (soft copy).

2. Your five simple web pages.

3. One MS Word file (soft copy) containing your MS project solutions (section 1), which will
   include:

       a.      MS Project WBS charts, including

                  i. Gantt chart.
                 ii. Network diagram.
                iii. Resource graphs (before and after showing correction for over-allocations).

       b.      Your answers to 1.1 and 1.2.
       c.      Your critical path diagram.
       d.      Your five simple web pages (screen dumped)
       e.      Your final report (section 2). Remember this will still be laid out as a report with title
                page, table of contents etc.

                                              Hard copy
4. Print out your MS Word file only.

                                              Submission
5. Place your soft copies (7 files) in your submission folder on Blackboard.

6. Place the hard copy (1 file) of the Word document in the ISYS302 assignment submission box
   in the foyer (E6A).




                                                   Page 8                                         Peter Busch

				
DOCUMENT INFO
Shared By:
Categories:
Stats:
views:6052
posted:12/6/2010
language:English
pages:8
Description: Advantages and Disadvantages of Project Network Diagram document sample