【文章內(nèi)容簡介】 Risk assessment document Project structure document Describes what you want to do and how you plan to do it Describes the risks the project entails Describes the project’s anizational structure Deliverables for Vision Approved Owner Product management Program management Program management Content Purpose Problem statement Vision statement Solution concept User profiles Business goals Design goals Why you want to do it What you want the product to be What you will do Who will use the product What you want to acplish How you plan to acplish it Contents of the Vision Document Risk Assessment Document Assessing preliminary project risks and planning their management ? Is created during the fivestep risk management process ? Is the initial assessment of project risk ? Lays the groundwork for ongoing risk management ? Provides a basis for scheduling and decisionmaking Project Structure Document Describing the project’s anizational structure and project management process ? Lists information on team members ? Includes team logistical information ? Describes team processes ? Acts as a repository for project documentation templates Agenda ? Overview ? Team Model ? Risk Management ? Process ? Vision approved milestone ? Project plan approved milestone ? Scope plete milestone ? Release milestone Lesson 1:Planning Phase Achieving the project plan approved milestone Importance of Planning Repair Cost of Design Defects by Phase 100 80 60 40 20 Envisioning Planning Developing Stabilizing Further Defining the Scope Features Planning Project Plan Approved Milestone Vision Approved Project Plan Approved Scope Complete Release Signals agreement on ? Project tradeoff strategy ? Project risks ? What will be built ? When it will be built ? How it will be built ? Who will build it Team Focus During Planning Product management Program management Development User education Testing Logistics management Role Focus Design。 munications plan and schedule Design。 functional specification。 master project plan and master project schedule Design。 development plan and schedule。 proof of concept development Design evaluation。 testing plan and schedule Design evaluation。 logistics plan and schedule Design。 user performance support。 user education plan and schedule Suggested Interim Milestones Functional Specification Drafted Project Plan Approved Master Project Schedule Drafted Master Project Plan Drafted Design Process Overview Logical Design Conceptual Design Scenarios Physical Design Components, User Interface, and Physical Database Objects and Services, User Interface, and Logical Database Relationship to Planning Project Plan Approved Physical Design Baseline Conceptual Design Logical Design Physical Design Vision Approved Logical Design Baseline Conceptual Design Baseline MSF Application Model Business Services User Services Data Services Application 1 Application 2 Deliverable Purpose Functional specification Master project plan Master project schedule Revised master risk assessment document Describes what will be built Describes how it will be built Describes when it will be built Describes any issues in building it Deliverables for Project Plan Approved Owner Program management Program management Program management Program management Contents of the Functional Specification Content Purpose Vision summary Design goals Requirements Usage summary Features Dependencies Schedule summary Issues Appendixes What you want the product to be, justification for it, and key highlevel constraints What you want to achieve with the product What you require from the product When the product will be used and who will use it What exactly the product does Other factors the product depends on Key dates and deliverables What risks might impact the project Design process output Master Project Plan Consolidating feature team and role work plans ? Describes how feature teams and roles will execute their tasks ? Synchronizes the plans across the team ? Includes ? Development plan ? Test plan ? Training plan ? User support plan ? Communications plan ? Deployment plan Master Project Schedule Consolidating feature team and role work schedules ? Describes when feature teams and roles will execute their tasks ? Synchronizes the schedules across the team ? Includes ? Product ship date ? Development schedule ? Test schedule ? Training schedule ? User support schedule ? Communications schedule ? Deployment schedule Master Risk Assessment Document Consolidating feature team and role risk assessments ? Provides an overall view of project risk ? Synchronizes the assessments across the team ? Drives highlevel decisionmaking and prioritization of effort Lesson 3:Scheduling Principles Some of the principles and practices that help make scheduling more accurate Principles of Accurate Scheduling ? Bottomup estimating ? Fixed–ship date mindset ? Riskdriven scheduling ? Scheduling for an uncertain future ? Adding buffer time ? Using interim development milestones ? Using discrete tasks Bottomup Estimating ? What it means ? Having those who do the work estimate the effort ? Rolling up tasklevel estimates ? Recognizing that experience is the best estimating technique ? Why it is important ? Increases the accuracy of the estimate ? Fosters team buyin of the schedule ? Motivates effi