Final Exam Review June 2 2011 SE 477

Final Exam Review June 2, 2011 SE 477: Final Review 1/19

Risk Management q Risk Management Ø Types of risk: schedule, cost, requirements q Risk Identification Ø Involve the team q Risk Analysis Ø Risk Exposure (RE = Prob. * Size) Ø Probability is 15%, size is 10 weeks §. 15 * 10 w = 1. 5 w q Risk Prioritization Ø 80 -20 rule; large size or prob. 1 st; grouping; ignoring June 2, 2011 SE 477: Final Review 2/19

Risk Management q Risk Control Ø Plan q Risk Resolution (5 Types) Ø Avoidance (ex: scrub) Ø Assumption (just monitor) Ø Control (contingency) Ø Knowledge Acquisition (learn/buy/prototype) Ø Transfer (off project, team, critical path) q Risk Monitoring Ø Top 10 Risk List q Mitigation vs. contingency planning June 2, 2011 SE 477: Final Review 3/19

Project Execution q Project Roles q Project Control Ø Planning Ø Measuring Ø Evaluating Ø Acting q Binary Reporting June 2, 2011 SE 477: Final Review 4/19

Feature Set Control q Minimal Specification q Requirements Scrubbing q Versioned Development q Effective Change Control q Feature Cuts June 2, 2011 SE 477: Final Review 5/19

Resource Leveling q Leveling techniques Ø Fast tracking – parallel tasks Ø Activity shifting Ø Activity splitting Ø Activity stretching Ø Resource substitution Ø Allocating overtime June 2, 2011 SE 477: Final Review 6/19

Change Control q Average project has 25% requirements change q Sources of change q Change control is a process q Overly detailed specs. or prolonged requirements phase are not the answer q Change Control Board (CCB) Ø Structure, process, triage June 2, 2011 SE 477: Final Review 7/19

Configuration Control q Items: code, documents q Change & Version control q Configuration Management Plan q Maintenance June 2, 2011 SE 477: Final Review 8/19

Earned Value Analysis q BCWS q BCWP Ø Earned value q ACWP q Variances Ø CV: (Cost Variance) = BCWP – ACWP Ø SV: (Schedule Variance) = BCWP – BCWS q Ratios Ø SPI (BCWP / BCWS), CPI (BCWP / ACWP) Ø CR (SPI x CPI) q Benefits Ø Consistency, forecasting, early warning June 2, 2011 SE 477: Final Review 9/19

QA & Testing q SQA Team q Defect Metrics Ø Why track metrics? June 2, 2011 SE 477: Final Review 10/19

Defect Metrics q Open Bugs (outstanding defects) § Ranked by severity q Open Rates § How many new bugs over a period of time q Close Rates § How many closed over that same period § Ex: 10 bugs/day q Change Rate § Number of times the same issue updated q Fix Failed Counts § Fixes that didn’t really fix (still open) § One measure of “vibration” in project June 2, 2011 SE 477: Final Review 11/19

Migration q Migration Plan q Migration Strategies Ø Flash Cut § Immediate Replacement § Parallel Operation Ø Staged § One part at a time q Importance of 2 -way communication Ø Find-out customer’s key dates q Minimize intrusiveness q Back-out Plan q Data Conversion June 2, 2011 SE 477: Final Review 12/19

Other Final Steps q Roll-Out Ø Release Check-List q Training Ø More than just end-users § Users, systems ops, maintenance developers, sales q Documentation § Many types: End-user, sales & marketing, operations, design June 2, 2011 SE 477: Final Review 13/19

Project Recovery q 3 Approaches Ø 1. Cut the size of the software Ø 2. Increase process productivity Ø 3. Slip the schedule, proceed with damage control q People Steps Ø Morale; focus; re-assign q Process Steps Ø Fix classic mistakes; mini-milestones q Product Steps Ø Stabilize; trim features; take out the garbage June 2, 2011 SE 477: Final Review 14/19

Post Project Reviews q Focused on process not people q Steps Ø Prepare survey form Ø Email team with survey and schedule meeting § Gather data Ø Conduct meeting Ø Prepare PPR report June 2, 2011 SE 477: Final Review 15/19

Resource Allocation q Responsibility Assignment Matrix Ø Who does What q Skills Matrix Ø Who has what skills q Hiring Guidelines Ø Hire for trait, train for skill Ø Smart, gets things done q Balance June 2, 2011 SE 477: Final Review 16/19

Teams q Start with objective Ø Problem resolution, creativity, tactical execution q Decentralized vs. Centralized q Large teams Ø Decompose via hierarchy, into optimal sizes q Optimal size? Ø 4 -6 developers q Hiring Ø Hire for trait – train for skill June 2, 2011 SE 477: Final Review 17/19

Team Models q Business team Ø Technical lead + team; most common Ø Can be strong or loose hierarchy q Democratic team organization Ø Self-organizing teams q Extreme programming groups q Chief-programmer team Ø Surgical team; star at top; ego issues q Skunk works team Ø Off-site; pro: buy-in; con: minimal visibility q Feature team Ø Interdisciplinary; balanced q SWAT team Ø Highly skilled/specialized; Ex: security team June 2, 2011 SE 477: Final Review 18/19

Teams q Understanding of human factors q Avoid making unrealistic demands on people q Staff selection factors q Software development groups q Group communications q The working environment June 2, 2011 SE 477: Final Review 19/19