Classic MistakesWhy Projects Fail - OverviewCategories of Classic MistakesEffect of Classic Mistakes on Development SchedulesClassic Mistakes - HomeworkClassic Mistakes EnumeratedThe “Welch Grid*”Slide 8Slide 9Slide 10Slide 11Slide 12Slide 13Slide 14Slide 15Slide 16Slide 17Slide 18Slide 19Slide 20Exercise: Develop a Project “Disaster Avoidance Plan”Course Admin: Labs, Going Forward (after this week)CSE Senior Design ICSE Senior Design IClassic MistakesClassic MistakesInstructor: Mike O’DellInstructor: Mike O’DellThis presentations was derived from the textbook used for this class, This presentations was derived from the textbook used for this class, McConnell, Steve, McConnell, Steve, Rapid DevelopmentRapid Development, Chapter 3., Chapter 3.52Why Projects Fail - OverviewWhy Projects Fail - OverviewFive main reasons:Failing to communicateFailing to create a realistic planLack of buy-inAllowing scope/feature creepThrowing resources at a problemN. B. – Software development is COMPLEX and HARD, so people make mistakespeople make mistakes.53Categories of Classic MistakesCategories of Classic MistakesPeople-relatedProcess-relatedProduct-relatedTechnology-related54Effect of Classic Mistakes on Effect of Classic Mistakes on Development SchedulesDevelopment SchedulesDoing a few things right DOES NOT guarantee success!Use of any specific best practice is necessary, but not sufficientnecessary, but not sufficient, to achieve rapid development speedsMissing mostMissing most of the potholes in the road, but falling into one big onefalling into one big one, will ruin your whole day (or project) “One bad apple (mistake) can spoil the bunch”55Classic Mistakes - HomeworkClassic Mistakes - HomeworkBefore next class..1. Review the following slides thoroughly2. If slides are not clear, refer to textbook for further details3. Prepare short (1 page) document listing your “Top 5” concerns about classic mistakes for your team/project. Provide rationale for each.4. Turn in and prepare to discuss in next class.51. Undermined motivation:The Big One - Probably the largest single factor in poor productivityMotivation must come from within2. Weak personnel:The right people in the right roles3. Uncontrolled problem employees:Problem people (or just one person) can kill a team and doom a projectThe team must take action… earlyConsider the Welch Grid6Classic Mistakes EnumeratedClassic Mistakes EnumeratedPEOPLE-RELATEDPEOPLE-RELATED57The “Welch Grid*”The “Welch Grid*”PEOPLE-RELATEDPEOPLE-RELATED* One of several variants, attributed to Jack Welch, former CEO of General ElectricBuy-in, PotentialInfluence, Capabilities, SkillsGOALGOALProblemProblemEvaluateEvaluateEvaluateEvaluateEvaluateEvaluateTrain & Train & EducateEducateTrainTrainTrainTrainEducateEducate& & EvaluateEvaluate58Classic Mistakes EnumeratedClassic Mistakes Enumerated4. Heroics:Heroics seldom work to your advantageHonesty is better than an empty “can-do”empty “can-do”5. Wishful thinking:Not the same as optimismDon’t plan on good luckluck! (Plan on bad luck??)May be the root causeroot cause of many other mistakes6. Noisy, crowded offices:Work environment is importantenvironment is important to productivityNoisy, crowded conditions lengthen schedulesPEOPLE-RELATEDPEOPLE-RELATED59Classic Mistakes EnumeratedClassic Mistakes Enumerated7. Friction between developers and customers/sponsors:Cooperation Cooperation is the keyEncourage participationparticipation in the process8. Unrealistic expectations:Avoid seat-of-the-pants commitmentsRealistic expectations is a TOP 5 issueTOP 5 issue9. Lack of effective project sponsorship:Management must buy-inManagement must buy-in and provide supportPotential morale killerPotential morale killerPEOPLE-RELATEDPEOPLE-RELATED510Classic Mistakes EnumeratedClassic Mistakes Enumerated10. Lack of stakeholder buy-in:Team members, end-users, customers, management, etc.Buy-in engenders cooperationcooperation at all levels11. Lack of user input:You can’t build what you don’t understandEarly input is critical to avoid feature creepfeature creep12. Politics placed over substance:Being well regarded by management will not make your project successfulPEOPLE-RELATEDPEOPLE-RELATED511Classic Mistakes EnumeratedClassic Mistakes Enumerated13. Adding people to a late project:Productivity killerProductivity killerThrowing people at a problem seldom helpsPEOPLE-RELATEDPEOPLE-RELATED512Classic Mistakes EnumeratedClassic Mistakes Enumerated14. Overly optimistic schedules:Wishful thinking/planning on good luck. (Feasibility??)15. Insufficient risk management:Identify unique risks and develop a plan to eliminate themConsider a “spiral” “spiral” (iterative) approach for larger risks16. Contractor failure:Relationship/cooperation/clear Statement of WorkPROCESS-RELATEDPROCESS-RELATED513Classic Mistakes EnumeratedClassic Mistakes Enumerated17. Insufficient planning:If you can’t plan it… you can’t do it!18. Abandonment of planning under pressure:Path to failureCode-and-fixCode-and-fix mentality takes over… and will fail19. Wasted time during fuzzy front end:That would be nownow!Almost always cheaper and faster to spend time upfront working/refining the planPROCESS-RELATEDPROCESS-RELATED514Classic Mistakes EnumeratedClassic Mistakes Enumerated20. Shortchanged upstream activities:See above… do the work up frontup front!Avoid the “jump to coding” mentality21. Inadequate design:See above… do the required work up frontup front!22. Shortchanged quality assurance:Test planning is a critical part of every planShortcuttingShortcutting 1 day early on will likely cost you 3-10 days laterQA me now, or pay me later!PROCESS-RELATEDPROCESS-RELATED515Classic Mistakes EnumeratedClassic Mistakes Enumerated23. Insufficient (project) management controls:Buy-in implies participation & cooperationcooperation24. Premature or overly frequent convergence:It’s not done until it’s done!25. Omitting necessary tasks from estimates:Can add 20-30% to your scheduleDon’t sweat the small stuffsmall stuff!!PROCESS-RELATEDPROCESS-RELATED516Classic Mistakes EnumeratedClassic Mistakes Enumerated26. Planning to catch up later:Schedule adjustments WILL be necessaryA month lost early on probably