1 / 38

Rapid Development (Part 1)

Rapid Development (Part 1). Mihail V. Mihaylov RammSoft. In The Beginning Was… The Triangle. Scope. Time. Cost. The Holy Triangle of PM. Scope. Time. Cost. The Holy Triangle of PM. The Holy Triangle of PM. Scope. Time. Cost. In Software Development Time Is the Most Critical Factor.

sheng
Download Presentation

Rapid Development (Part 1)

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. Rapid Development(Part 1) Mihail V. Mihaylov RammSoft

  2. In The Beginning Was…The Triangle Scope Time Cost

  3. The Holy Triangle of PM Scope Time Cost

  4. The Holy Triangle of PM

  5. The Holy Triangle of PM Scope Time Cost

  6. In Software Development Time Is the Most Critical Factor Scope Time Cost

  7. What Rapid Development is not? • It isn't Rapid Development™ —a magic phrase or buzzword • It isn't a glitzy Blaze-O-Matic® or Gung-HO-OO™ rapid-development methodology

  8. What is Rapid Development? • It is a generic term that means "speedy development" or "shorter schedules" • It means developing software faster than you do now

  9. Quotes • I wish I had a simple solution to the development-speed problem. I also wish I had five million dollars.But simple solutions tend to work only for simple problems, and software development isn't a simple problem.Rapid development of software is even less simple. (Steve McConnell) • For every complex problem, there is an answer that is short, simple, and wrong. (H. L. Mencken)

  10. Who Invented it? Steve McConnell http://www.stevemcconnell.com/

  11. Who Is Steve McConnell? • CEO and Chief Software Engineer at Construx Software (http://www.construx.com/) • Technical book writer • Editor in Chief Emeritus of IEEE Software magazine

  12. Steve McConnell’s Books • Code Complete (1993) / (2004) • Rapid Development (1996) • Software Project Survival Guide (1997) • After The Gold Rush (1999) / Professional Software Development (2003) • Software Estimation: Demystifying the Black Art (2006)

  13. More Steve McConnell Facts • In 1998 named one of the 3 most influential people in the software industry • Won twice Software Development magazine's Jolt Excellence award for outstanding SD book of the year

  14. Rapid-Development Strategy • Avoid classic mistakes • Apply development fundamentals • Manage risks to avoid catastrophic setbacks • Apply schedule-oriented practices

  15. The Four Pillars Of RD

  16. Efficient Development Efficient Development

  17. The Four Pillars Of RD

  18. Efficient Development

  19. Software-Development Fundamentals • Management fundamentals • Technical fundamentals • Quality-assurance fundamentals

  20. Management Fundamentals • Planning • Tracking • Measurement

  21. Technical Fundamentals • Requirements management • Design • Construction • Configuration management

  22. QA Practices • Error-prone modules analysis • Testing • Technical reviews • Walkthroughs, Code reading, Inspections (find 60-90% of the defects)

  23. Risk Management • Levels of risk management • Crisis management (Fire-fighting) • Risk mitigation • Prevention • Elimination of root causes

  24. Four Dimensions of Development • People • Process • Product • Technology

  25. People • Peopleware issues have the biggest impact on software productivity and software quality • 10-to-1 difference in productivity among developers • 5-to-1 difference in productivity among teams

  26. Ways to MaximizeHuman Potential • Staff selection • Top talent, Job matching, Career progression, Team balance, Misfit elimination • Team organization • Motivation

  27. Process • Includes management and technical methodologies • Development fundamentals • Risk management • Quality assurance • Rework avoidance • Customer orientation

  28. Product • Product size and complexity • Product’s business area • Product goals

  29. Technology • Programming languages • Frameworks • IDE’s • Other tools • Designers • Debuggers

  30. Which Dimension Matters The Most? It depends

  31. Classic Mistakes • What is so “classic” in them? • What are the reasons for them?

  32. People-Related Mistakes • Undermined motivation • Weak personnel • Uncontrolled problem employees • Heroics (Wishful thinking) • Adding people to a late project • Noisy, crowded offices

  33. People-Related Mistakes • Friction between developers and customers • Unrealistic expectations • Lack of • effective project sponsorship • stakeholder buy-in • user input • Politics placed over substance

  34. Process-Related Mistakes • Overly optimistic schedules • Insufficient risk management • Abandonment of planning under pressure • Wasted time during the fuzzy front end • Insufficient management controls • Planning to catch up later

  35. Product-Related Mistakes • Requirements gold-plating • Feature creep • Developer gold-plating • Push-me, pull-me negotiation • Research-oriented development

  36. Technology-Related Mistakes • Silver-bullet syndrome • Overestimated savings from new tools or methods • Switching tools in the middle of a project • Lack of automated source-code control

  37. Conclusion • Avoid classic mistakes if possible • Explain the potential threat when forced to make classic mistakes • Actively manage the risks • Quit

  38. Thank You! • Google: Спри и помисли! • Email: mikeramm@gmail.com • Personal blogs: • http://mikeramm.blogspot.com • http://spriipomisli.blogspot.com

More Related