Planning Phase
Figure 3: Planning phase process/data model
|
|
|
Define Requirements
|
“Early in the planning phase, the team analyzes and documents requirements in a list or tool. Requirements fall into four broad categories: business requirements, user requirements, operational requirements, and system requirements (those of the solution itself).” (MSF Process model |
|
Trace Requirements to Features |
“As the team moves on to design the solution and create the functional specifications, it is important to maintain traceability between requirements and features. Traceability does not have to be on a one to one basis. Maintaining traceability serves as one way to check the correctness of design and to verify that the design meets the goals and requirements of the solution.” (MSF Process model |
|
Define Functional Specification |
“The team prepares the functional specification.” (MSF Process model |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
“This begins with a systematic analysis of user profiles (also called “personas”) which describe various types of users and their job functions (operations staff are users too). Much of this is often done during the envisioning phase. These are broken into a series of usage scenarios, where a particular type of user is attempting to complete a type of activity, such as front desk registration in a hotel or administering user passwords for a system administrator. Finally, each usage scenario is broken into a specific sequence of tasks, known as use cases, which the user performs to complete that activity. This is called “story-boarding.”” (MSF Process model |
|
|
|
|
|
|
|
|
|
|
|
Table 3: Planning activities
In the planning phase a functional specification is created from the requirements. Features selected are included in this specification (a MoSCoW Method is often used for the features so they can be prioritized more easily). Also the basic design and planning are created in this phase. The design however is in this phase not frozen as changes may be made in the development phase.
|
|
|
“Documentation of requirements in a list or tool.” (MSF Process model |
|
“Document on how the team plans to implement the risk management process within the context of the project.” (MSF Risk Management Discipline ) |
|
“All plans are synchronized and presented together as the master project plan.” (MSF Process model |
|
“A plan or plans for the deliverables that pertain to the role and participates in team planning sessions.” (MSF Process model |
|
|
|
“Time estimates and schedules for Deliverables.” (MSF Process model |
|
“The various schedules are then synchronized and integrated into a master project schedule.” (MSF Process model |
|
“The functional specification describes in detail how each feature is to look and behave. It also describes the architecture and the design for all the features.” (MSF Process model |
Table 4: Concepts in the planning phase
Read more about this topic: Internet-Speed Development, The Phases of Internet-Speed Development
Famous quotes containing the words planning and/or phase:
“...A shadow now occasionally crossed my simple, sanguine, and life enjoying mind, a notion that I was never really going to accomplish those powerful literary works which would blow a noble trumpet to social generosity and noblesse oblige before the world. What? should I find myself always planning and never achieving ... a richly complicated and yet firmly unified novel?”
—Sarah N. Cleghorn (18761959)
“It no longer makes sense to speak of feeding problems or sleep problems or negative behavior is if they were distinct categories, but to speak of problems of development and to search for the meaning of feeding and sleep disturbances or behavior disorders in the developmental phase which has produced them.”
—Selma H. Fraiberg (20th century)