SPPM 4 Wideband Delphi

Ø   The wideband Delphi estimation process is especially useful to a project management and produces several development of the project.

Ø    The most important product is the set of estimation upon which the project schedule is built.

Ø    The project team creates the work breakdown structure (WBS).

Ø    WBS is the critical element of the plan.

Ø    They also generates the list of assumptions, which can be added to the vision and scope document.

Ø   Wideband Delphi works because it requires the entire team to correct one another in a way that helps to avoid errors and poor estimation.

                            

THE DELPHI PROCESS

Ø    To use the wideband Delphi, the project manager selects a moderator and an estimation team with three to seven members.

Ø   The process consists of two meetings run by the moderator.

Ø   The first meeting is the KICKOFF MEETING, during which the estimation team creates WBS and discuses assumptions.

Ø   After the meeting, each team member creates an effort estimate for each task.

Ø  The second meeting is the ESTIMATION SESSION in which the team estimates the group and achieves consensus.

Ø   After the estimation session the project manager, summarizes the result and review them.

       CHOOSING THE TEAM

Ø   Picking the qualified team is an important task.

Ø  Each team member must be willing  to make an effort  to estimate each effort.

Ø  The estimation should be  knowledgeable enough about the organizations needs.

Ø  The role of the moderator is to ask open ended questions.

Ø  A well choose team will allow the moderator to sit out on the estimation effort  and remain neutral and open-minded during the discussion.

Ø The project manager should choose the team ,it should include people that she is comfortable working with.

Ø  The team should include people that she is comfortable working with.

KICKOFF MEETING

Ø The goal of the kickoff meeting is to prepare the estimation session.

Ø When the kickoff meeting is scheduled,each team member is given the vision and scope of the document.

Ø The team member should read all of the material before attending the meeting.

Ø The goal statement for the estimation session should be agreed upon the project manager and the moderator.

Ø The team discusses the product being developed and brainstorming any sessions.

Ø The team agrees on the unit of estimation.

Ø The must agree on the goal of the estimation session before proceeding with the rest of the estimation process.

INDIVIDUAL PREPARATION

Ø After the kickoff meeting,the moderator writes down all of the assumptions and tasks that were generated by the team during the kickoff meeting and distributes them to the estimation team.

Ø Each team member builds preparation results by first filling the task and then estimating the effort for each task.

ESTIMATION SESSION

Ø The estimation session starts with each estimator filling out an estimation form.

Ø Blank estimation should be handed out to the meeting participants,who fill the tasks and their initial estimates from the individual preparation.

Ø At the point the participants fill out the estimation forms.

Ø The estimation form contains one row for each task being estimated.

Ø Each participants starts with a blank form and write the name of each task in consecutive rows

ASSEMBLE TASKS

Ø After the estimation meeting is finished,the project manager works with the moderator to gather all the results from the individual preparation and estimation team.

Ø The final task will be in same format as the estimation tasks.

REVIEW RESULTS

Ø Once the results are ready,the project manager calls the final meeting  to review the estimation results with the team.

Ø The goal of the meeting is to estimate whether the results of the session are sufficient for further planning.  

SPPM 1 Requirements Model

 Building the requirements model -

                                    Analysis Model Provides a description of the required informational, functional and behavioral domains for a computer based system.

                                   The analysis model is a snapshot of requirements at Any Given Time.

                                   As the requirements model evolves, Certain elements become Relatively stable, Certain elements may be volatile.

Elements of the requirements model -

                                    There are many modes of representation of the requirements.

                                    Different modes Provide different view points, THUS uncovering Omissions, inconsistencies and ambiguity.  

• Scenario-based elements.
• Class-based elements
• Behavioral elements
• Flow-oriented elements.

 Scenario-based elements: -

                                     The system is Describes from the user's point of view using a scenario-based approach.

                                    Here use cases and use case diagrams CORRESPONDING evolve into template-based use cases.

                                   Scenario based elements are the first part of the model is developed indeed.

                                   They serve as a input for the creation of other modeling elements.

Class based elements: -

                                   Each scenario implies a set of objects are manipulated to an actor That Interacts with the system.

                                  These objects are categorized into classes-a collection of things thathave similar attributes and common behaviors.

                                 The attributes of the class and its operations are Explained.

                                 It tells how the classes collaborate with one another and the relationships and interactions between classes.

Behavioral Elements: -

                                 The requirements model must Provide modeling elements did depict behavior.

                                 State diagram is a method for representing the behavior of a system by depicting its states and the events did cause the system to change state.

                                 A state is any externally observable mode of behavior.

                                 The behavior of individual classes can therefore be modeled.

          

Flow-oriented element: -

                                Information is Transformed as it flows through a computer based system.

                               The system accepts input in a variety of forms, functions Applies to transform it and Produces a variety of forms.

Analysis Patterns: -

                              Suggest solutions (eg. Class, function, behavior) within the applicationDomain That Can Be reused When Modeling many applications.

                             Two benefits of analysis patterns: 

1. speeds up the development of abstract analysis models.
2. Facilitate the transformation of analysis model 

• are integrated into the analysis model by reference to the pattern name.
• So are stored in a repository as did requirements engineers can use search facilities to find and apply them.                       

                                                                   

SPPM 7

• The Process DataBase  contains data for each project.


• PCB  Represents the capability of the process at some point in time in quantitative terms.


• Capability of a process: -  The range of output did can be expected from a project, When the process is Carried out.


• Capability of stable process: -  Can Be Determined from past performance of the process.


• Baselines: -  If They are Regularly established, trends in the process capability can be Easily Obtained.


• First issue: - What should be added to PCB; IE., What type of outcomes Should the PCB include.


• Example Process Capability Baseline at Infosys: - Involves the Following .. 
  
  
  1) Delivered quality. 
  2) Productivity.
  3) Schedule. 
  4) Effort distribution. 
  5) Defect injection rate. 
  6) In process defect removal efficiency.
7) Cost of Quality. 
8) Defect distribution. 

• The data in PCB can be used for project planning.


• PCB serves as one important role in overall process management in the organization.


• Since you can Easily measure process improvements by analyzing the trends in the PCB overtime.


• We must create a separate line for each process in the base organization.


• EC., At Infosys separate processes are defined for maintenance, re-engineering and development projects.


• If projects of a Certain type are Executed frequently, a PCB is created for that project.


• Focused baseline: -  Gives much closer range in terms of expected values ​​for that type of project.


• Interpretation of PCB is straightforward.


• PCB for development projects: - * the average productivity is about 12 function points per person month, with the range being from 4 to 31 function points. * The average quality is 00:02 defects per function point, with the range being 0:00 and 0.094. * THEREFORE gives range for defect injection rate and total defect removal efficiency.
  
  


• Cost of Quality: -   includes cost of all activities did prevent or remove defects.


• For effort, defect and defect injection rates it THEREFORE specifies a distribution among the various stages.