1 / 19

Final Exam Review

Final Exam Review. Risk Management. Risk Management Types of risk: schedule, cost, requirements Risk Identification Involve the team Risk Analysis Risk Exposure (RE = Prob. * Size) Probability is 15%, size is 10 weeks .15 * 10w = 1.5w Risk Prioritization

sylvia
Download Presentation

Final Exam Review

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Final Exam Review SE 477: Final Review

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

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

  4. Project Execution • Project Roles • Project Control • Planning • Measuring • Evaluating • Acting • Binary Reporting SE 477: Final Review

  5. Feature Set Control • Minimal Specification • Requirements Scrubbing • Versioned Development • Effective Change Control • Feature Cuts SE 477: Final Review

  6. Resource Leveling • Leveling techniques • Fast tracking – parallel tasks • Activity shifting • Activity splitting • Activity stretching • Resource substitution • Allocating overtime SE 477: Final Review

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

  8. Configuration Control • Items: code, documents • Change & Version control • Configuration Management Plan • Maintenance SE 477: Final Review

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

  10. QA & Testing • SQA Team • Defect Metrics • Why track metrics? SE 477: Final Review

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

  12. Migration • Migration Plan • Migration Strategies • Flash Cut • Immediate Replacement • Parallel Operation • Staged • One part at a time • Importance of 2-way communication • Find-out customer’s key dates • Minimize intrusiveness • Back-out Plan • Data Conversion SE 477: Final Review

  13. Other Final Steps • Roll-Out • Release Check-List • Training • More than just end-users • Users, systems ops, maintenance developers, sales • Documentation • Many types: End-user, sales & marketing, operations, design SE 477: Final Review

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

  15. Post Project Reviews • Focused on process not people • Steps • Prepare survey form • Email team with survey and schedule meeting • Gather data • Conduct meeting • Prepare PPR report SE 477: Final Review

  16. Resource Allocation • Responsibility Assignment Matrix • Who does What • Skills Matrix • Who has what skills • Hiring Guidelines • Hire for trait, train for skill • Smart, gets things done • Balance SE 477: Final Review

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

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

  19. Teams Understanding of human factors Avoid making unrealistic demands on people Staff selection factors Software development groups Group communications The working environment SE 477: Final Review

More Related