Docstoc

Project-Management

Document Sample
Project-Management Powered By Docstoc
					Project Planning and Scheduling – AMES-40089                                      Sachin Dewagan
Winter 2007                                                                               Paul Lee
WBS Dictionary                                                                           Tim Milby
March 4, 2007                                                                     Patricia Mourthé
                                                                                   Vincenzo Sferra




Work Breakdown Structure Dictionary
    1.1          Project Management
    Description: The application of knowledge, skills, tools, and techniques to project
    activities to meet project requirements

    1.1.1.       Project Kickoff
    Description: Meeting held with key personnel and management to formally begin a Project.


    1.1.2.       Project Management Plan
    Description: A formal, approved document that defines how the project is to be executed,
    monitored and controlled.


    1.1.2.1.     Scope Management Plan
    Description: Plan that documents how the project scope will be defined, verified,
    controlled, and how the work breakdown structure (WBS) will be created and
    defined.


    1.1.2.2.     Quality Assurance Management Plan
    Description: Describes how the Project Management Team will implement the company’s
    quality policy.


    1.1.2.3.     Time Management Plan
    Description: Describes the Company’s policy on the pricing of time, how to conduct a time
    audit, and how to identify and control poor time management practices.


    1.1.2.4.     Cost Management Plan
    Description: Describes the format and establishes the activities and criteria for planning,
    structuring and controlling the project costs.


    1.1.2.5.     Communication Management Plan
    Description: Describes the communications needs and expectations of for the project, how
    and in what format information will be communicated; when and where each
    communication will be made; and who is responsible for providing each type of
    communication.




3/2/2010                                                                                          1
Project Planning and Scheduling – AMES-40089                                     Sachin Dewagan
Winter 2007                                                                                Paul Lee
WBS Dictionary                                                                          Tim Milby
March 4, 2007                                                                    Patricia Mourthé
                                                                                  Vincenzo Sferra



    1.1.2.6.     Human Resource Management Plan
    Description: Describes how Human resource requirements will be met.


    1.1.2.7.     Procurement Management Plan
    Description: Describes how procurement processes from developing procurement
    documentation through contract closure will be managed.


    1.1.2.8.     Risk Management Plan
    Description: Describes how Risk Management will be structured and performed on the
    project.


    1.1.3.       Software Development Plan
    Description: Describes how the company’s software development will be managed.


    1.1.3.1.     Software Verification
    Description: Describes the processes used in verify the software meets minimum
    requirements for testing.


    1.1.3.2.     Software Validation
    Description: Describes the processes, and test procedures used to confirm the software
    meets the requirements outlined in the requirements definition.


    1.2          Requirement Definition
    Description: Defines all requirements of the project


    1.2.1        User Access Definition
    Description: Define how the users will sign on to the message center.


    1.2.2        Interview Stakeholders
    Description: initial meeting to define requirements and expectations of the project.


    1.2.3        Form Content
    Description: Describe the information the user will provide to submit reviews and
    comments.




3/2/2010                                                                                         2
Project Planning and Scheduling – AMES-40089                                     Sachin Dewagan
Winter 2007                                                                             Paul Lee
WBS Dictionary                                                                         Tim Milby
March 4, 2007                                                                    Patricia Mourthé
                                                                                 Vincenzo Sferra



    1.2.4        Data Entry Types
    Description: Define types of data in the interactive forms.


    1.3          Pilot Version
    Description: Initial version of the software release to identify bugs and recommend fixes
    before final release.


    1.3.1        Phase Design
    Description: Define the planning and conceptual phase of the application.


    1.3.1.1      User Interface
    Description: The Graphic interface the user sees when logging into the program.


    1.3.1.2      Rules Definition
    Description: Rule sets that are unique to Message In A Bottle software that defines how
    the system works.


    1.3.1.3      Database
    Description: Storehouse for unique data generated for and by the software.


    1.3.1.4      Design Review
    Description: The initial series of Integrated Product Team (IPT) and Configuration Control
    meetings to review and comment on requirements and correct the software design.


    1.3.2        Phase 1 Development
    Description: Develop the software necessary to create a workable application incorporating
    all elements and components defined in the design phase.


    1.3.2.1      Code
    Description: Computer language that allows the software to function and allow input and
    produce output.


    1.3.2.1.1    User Interface
    Description: Implement 1.3.1.1




3/2/2010                                                                                         3
Project Planning and Scheduling – AMES-40089                                       Sachin Dewagan
Winter 2007                                                                               Paul Lee
WBS Dictionary                                                                           Tim Milby
March 4, 2007                                                                      Patricia Mourthé
                                                                                   Vincenzo Sferra



    1.3.2.1.2    Rules
    Description: Implement 1.3.1.2


    1.3.2.1.3    Database
    Description: Implement 1.3.1.3


    1.3.2.1.4    Code Review
    Description: Review of the coding of each element of the software package.


    1.3.2.2      Unit Test
    Description: Stand alone test of the software in a non-networked environment to verify
    whether the software is accomplishing what was expected to accomplish.


    1.3.2.2.1    User Interface
    Description: See 1.3.1.1


    1.3.2.2.2    Rules
    Description: See 1.3.1.2


    1.3.2.2.3    Database
    Description: See 1.3.1.3


    1.3.2.2.4    Unit Test Review
    Description: A review of the test results from the Unit Test.


    1.3.2.3      Integration Test
    Description: Test of the integration of the software into a networked environment with
    interfaces to other systems enabled.


    1.3.3        User Feedback
    Description: Comments from users concerning usability of the system.


    1.4          Final Version
    Description: Final release of the software after all unit and integration testing and bug
    fixes are applied.




3/2/2010                                                                                         4
Project Planning and Scheduling – AMES-40089                                    Sachin Dewagan
Winter 2007                                                                             Paul Lee
WBS Dictionary                                                                         Tim Milby
March 4, 2007                                                                   Patricia Mourthé
                                                                                Vincenzo Sferra



    1.4.1        Update User Requirement Definition Document
    Description: Applying additions to the Requirements Definition Document.


    1.4.2        Phase 2 Design
    Description: Revise initial software planning and concept to meet new requirements.


    1.4.2.1      User Interface
    Description: See 1.3.1.1


    1.4.2.2      Rules Definition
    Description: See 1.3.1.2


    1.4.2.3      Database
    Description: See 1.3.1.3


    1.4.2.4      Final Design Review
    Description: Final review of product design.


    1.4.3        Phase 2 Development
    Description: Final Phase of software and interface development.


    1.4.3.1      Code
    Description: See 1.3.2.1


    1.4.3.1.1    User Interface
    Description: See 1.3.1.1


    1.4.3.1.2    Rules
    Description: See 1.3.1.2


    1.4.3.1.3    Database
    Description: See 1.3.1.3


    1.4.3.1.4    Final Code Review
    Description: Final review of the coding of each element of the software package.




3/2/2010                                                                                      5
Project Planning and Scheduling – AMES-40089                                    Sachin Dewagan
Winter 2007                                                                               Paul Lee
WBS Dictionary                                                                           Tim Milby
March 4, 2007                                                                    Patricia Mourthé
                                                                                 Vincenzo Sferra



    1.4.3.2      Unit Test
    Description: See 1.3.2.2


    1.4.3.2.1    User Interface
    Description: See 1.3.1.1


    1.4.3.2.2    Rules
    Description: See 1.3.1.2


    1.4.3.2.3    Database
    Description: See 1.3.1.3


    1.4.3.2.4    Final Unit Test Review
    Description: Final review of the test results from the Unit Test.


    1.4.3.3      Integration Test
    Description: See 1.3.2.3


    1.4.3.3.1    Update Integration Test
    Description: Update of test cases base on Integration Testing.


    1.4.3.3.2    Execute Integration Test
    Description: Actual performance of Integration Testing.


    1.4.3.3.3    Final Integration Test Review
    Description: Final review of the results of all Integration Testing.


    1.5          Acceptance Test
    Description: Formal test to accept the software


    1.6          Training
    Description: Online, on the job training and formal classroom training designed to teach
    the user the fundamentals of the software system and its uses.


    1.6.1        User Manual
    Description: Guide or hardcopy of the uses of the software via the User Interface.




3/2/2010                                                                                        6
Project Planning and Scheduling – AMES-40089                                       Sachin Dewagan
Winter 2007                                                                               Paul Lee
WBS Dictionary                                                                           Tim Milby
March 4, 2007                                                                      Patricia Mourthé
                                                                                    Vincenzo Sferra



    1.6.2        Preparation
    Description: Steps required to prepare the software for use.


    1.6.3        Deliver Training
    Description: Training delivered to the user via online, on the job training or in a formal
    classroom setting.


    1.7          Delivery/Launch
    Description: Final delivery of the program to the key stakeholders and sponsors.


    1.8          Maintenance (60 Day)
    Description: Recommended maintenance interval for the system.


    1.8.1        Support (On Call)
    Description: Support provided to ensure use and proper function of the system.


    1.8.2        Troubleshooting
    Description: Provided during support. Those steps that are necessary to identify and
    resolve functional software issues.


    1.8.3        Trouble Report Fixing
    Description: Review of Trouble Reports and coding alteration to correct deficiencies or
    errors in the software.




3/2/2010                                                                                         7

				
DOCUMENT INFO
Shared By:
Categories:
Stats:
views:666
posted:3/3/2010
language:English
pages:7
Description: Project-Management