Important Topics

Q: Project Team? Project Risk ? planning and organization ?
pg no(-) L35

Project Team:

1. Only means to reach to goal.
2. Vital step - team selection.
3. special attention to create teams - who respect each other.
4. size of team depends on complexity of project.
5. tech knowledge and experience also matter

Project Risks:

1. project will be at risk if expectation to projects will not controlled or if the results are ill defined or misunderstood.
2. Before elimination need to identify and address the risk.
3. Need to discuss with the team managers and end users.
4. Need to know the cause and took measurement to minimize the risk factor
5. It can be accessed under 3 categ
1. business risk
2. technology risk
3. project size risk
6. Control from initial stage. by following standards
7. train your team
8. Technical risk when new technology introduced

Q: Explain SPR assessment
pg no(-) L29

1. Software accessment interview is a group activity for each project going to analyze.
2. SPR consultant meeting with the manager and 7 technical staff at a time
3. Participants have questions to give answer.
4. the official accessment is filled by the SPR consultant after accesssing the group.
5. in case of differnet opinion all the POV's are recorded
6. Next these issues resolved.
7. SPR are structured interviews based on scripted questions.
8. questionnaire with mcqs 250/ 100 sets  
9. once the project samples analyzed. the answer input in statistical tool to show stats and standard deviations
10. then the weak ares are revealed and which is essential to software process improvement
11. than next client is able to adopt the software process improvement program
12. Next 6-stage improvement program requires

Six-Stage Improvement Program

1. Focus on management technologies 
2. Focus on software processes and methodologies 
3. Focus on new tools and approaches  
4. Focus on infrastructure and specialization  
5. Focus on reusability  
6. Focus on industry leadership
     

Q: Which stage we should collect data? When to Collect Data

pg no(138-)

1. data collection planing need to start when product planning started.
2. It required in many stages 
3. some data need to collect when project starts while other later.
4. also collected during inspection and reviews
5. some data collected when changes applied to enhance the product
6. data collection should be an essential part of development process
7. In the same way if process/activity need to analyze .its required to prepare the measuring list.

Q: Ideal Model ? Establishing phase ? explain set context and build sponsorship ?
pg no(32-) L28

• Ideal Model - It is a life cycle model for software process improvement
• Based upon CMM
• it provides usable and understandable approach/ steps in a way to Software Process improvement.
• it has phases, activities and principles.
• it provides the disciplined engineered work, which is foundation of long term improvement plan.
• IDEAL model is named for the five phases it describes: initiating, diagnosing, establishing, acting, and learning

set context and build sponsorship are the steps of initiating phase

Set Context -

1. Once the need of change identified: the management set context of work to be done.
2. "setting context" explain where this efforts fit in current business strategy
3. what business goals it have
4. who it is affecting the ongoing work.
5. its benefits?

Build Sponsorship - 

1. effective sponsorship is required for software improvement
2. As on the way to improvement system, may organization faces the chaos and uncertainity 
• So critical management support required at the beginning
3. sponsers are most effective if they give personal attention and stick with it.

The Establishing Phase

1.  Purpose of the establishing phase is to develop a detailed work plan 
2.  Finally, specific actions, milestones, deliverables, and responsibilities are incorporated into an action plan
3. Step in Establishing Phase
1. Set Priorities
2. Develop Approach
3. Plan Actions

Q: people CMM level 3 /level I
pg no(86-) L36

People CMM

1. It helps to manage and develop organizations workforce.
2. it employs the process maturity framework CMM consists of best practices.
3. It is a tool that helps you successfully address the critical people issues in your organization

Seven Principle of Workforce Management

1. Employment security

2. Selective hiring of new personnel

3. Self-managed teams and decentralization of decision making

4. Comparatively high compensation contingent on organizational performance

5. Extensive training

6. Reduced status distinctions and barriers

7. Extensive sharing of financial and performance information

Process Maturity 5 levels 

1. continuous process improvement in five stages
2. it is a process standard and consists of best practices
3. It integrates the improved practices into staged model & hence guide to cultural transformations

1st level

1. initially in project there is no consistent way of performing the work.
• so work processes are ad-hoc
2. As no well-understood working way so- mangers have no proper way to estimate the project completion
3. to meet the deadlines. the teams started doing mistakes.
• which can be easily detected
4. projects loss control in less-mature organization. as no control of cost schedule and quality.

3rd level

1. organization identifies the best practices and 
• integrate them into a common practice
2. once people followed the common practices. organizations can depict which practice works best in which environment.
3. prepared documentation to train others following it
4. critical practices also kept in repo for later anaylsis

Q: List measuring scale n explain nominal n ordinal
pg no(116-) L 40

1. Nominal
2. Ordinal
3. Interval
4. Ratio
5. Absolute

1. Nominal

1. Define class or categories and 
1. place each entity in the specific class/category
2. based on the value of attribute
2. It is called nominal measurement
3. classes are not ordered
4. Example 
• location of software faults (specification, code, design)  

2. Ordinal

1. The ordinal scale is useful to augment the nominal classes with information related to classes.
2. It gives ordering to classes which not possible by nominal scale
• which further leads to analysis
3. Now the empricial system consist of classes
• ordered with respect to its attributes
4. Complexity of software modules is described as
• Trivial
• Simple
• Moderate
• Complex
• Incomprehensible

Q: TSP ? Teambuilding Principles ? TSP BOK ? Team Operational Processes

Team Operational Processes:

1. it is required for disciplined work by engineers
2. It precisely defined how the work is to be done.
3. it is in form script which should be followed when doing work.
4. The TSP provide operational process to enlist the team building steps
5. defining it requires skill and effort

TSP Foundations and Fundamentals

• it outlines the foundation on which TSP built
• Fundamental concept requires for practitioner to implement it.

5 knowledge areas

1. knowledge work
2. TSP Prerequisite Knowledge
3. TSP Principles
4. TSP Process Elements and Measures
5. TSP Quality Practices

Team Foundations

• team of people work together and that team also have skills and are effective
• Are capable of doing highly complex nature tasks
• and they do large-scale task having many interdependence tasks

7 knowledge areas

1. Teams and Team building
2. Team Types, Styles, and Dynamics
3. Team Formation and Membership
4. Team Member Responsibilities
5. Team Member Roles
6. Team Leader Role
7. Coach Role

Project planning with TSP

• it begins when organization going to implement new technology following small pilot projects
• TSP certified coach helps them to select the team and
• to provide PSP and TSP project planning and tracking methodology
• once trained they participate in TSP Launch
• TSP launch is series of team building activites and composed of ten meetings
• TSP coach work with managers leaders and team members to organize each and every step.
• team present plan to managament and
• after acceptance started working on it.
• Its knowledge areas describes
• requirements activites and guideposts
• to implement Pilot PSP Project and launching TSP teams

5 knowledge areas

1. Change Management Fundamentals
2. Piloting TSP in an Organization
3. Preparing Management and Teams for TSP Implementation
4. The TSP Launch Meetings
5. The TSP Relaunch

Project Implementation and Tracking with TSP

• to correct and accurate the data
• to fix the small problems which becomes bigger
• using status tracking

5 knowledge areas

1. Weekly Meetings
2. Checkpoints
3. Communicating with Stakeholders
4. Replanning
5. Phase, Cycle, and Project Postmortems

Gathering and Using TSP Data

• PSP relies on individual data
• TSP methods rely on data collection and analysis 
• Data provide a baseline for making estimates and plans

5 knowledge areas

1. Data Recording
2. Gathering and Using Size Data
3. Gathering and Using Schedule Data
4. Gathering and Using Quality Data
5. Gathering and Analyzing Postmortem Data

Scaling Up the TSP

• begins with one or two small-scale pilot projects

3 knowledge areas

1. Organizational Implementation
2. TSP Process Variations
3. Large-scale TSP Teams