Combining Agile and Traditional Development

Gary Gack , software process consultant, did an interesting webinar and discussed the combining of Agile and traditional development approaches.  His conclusions are that this does not have a negative impact on either cost or defects.

I also found it interesting that this is pretty much the process used within Galorath:

• Traditional development for clear, large, stable requirements
• Agile for Fuzzy, small, unstable requirements.

I loved Gary’s example of a credit card system as a reimplementation.  New rules coming from the government but we don’t even know the rules yet.   Can’t just do Agile…and give people a partial solution.  The entire system is needed or not at all (although not at all has severe business issues).  Conclusion was Agile for user interface and interest calculation, and traditional for the rest of the system.  Refreshing to see the avocation of combining Agile and traditional.  Good job Gary.

Related posts:

1. Estimation & Agile Development… Plan and Control Agile Projects
2. Agile Development Mature Scrum
3. Peaceful Coexistence of Agile Development and CMMI
4. Agile Estimating User Stories
5. Mapping Agile Principals to SEER for Software (SEER-SEM)

Comments

• Subscribe to this Blog

  Enter your email address:

• Twitter

  Follow Dan Galorath on Twitter.

• Galorath Library

  Galorath maintains a rich library of webinars, presentations, whitepapers, and demos. Register to read our entire library.

• Recent Posts

  • Cost Growth In Weapons Systems Circa 1982
  • Accounting Definitions For Setup
  • Considerations for CMMI Level 4 for Systems/Software product development and deployment
  • MIT Interns Bust Brooks Law?
  • SEER-SEM Effort Increases When Schedule Is Stretched Too Far
  • Acquisition Reform (WSARA) And History
  • Personal Capabilities & Other Non-Technical Parameters Can Make a Big Difference in Estimating
  • Acquisition Reform (WSARA) Webinar Discusses Lessons Learned and Way Forward
  • Dr. Min Newest INCOSE Fellow
  • Churn Rate For On-Demand (Software as a Service) Solutions

• Categories

  • business value
  • CEO
  • Conferences
  • Cost Estimating
  • Design for Manufacturing Estimating
  • earned value
  • Estimating
  • Estimation Process
  • General
  • Hardware Electronics Systems Estimating
  • IC Estimating
  • IT Estimating
  • Lists
  • Presentations
  • Project Management
  • Risk
  • Software Estimating
  • Software Sizing
  • Systems Estimating
  • Systems of Systems Estimating
  • Ten Step Project Estimation Process
  • Thoughts

• Recent Comments

  • galorath on Cost Estimating Body of Knowledge (CEBok) Now Available From SCEA
  • John Leschke on Cost Estimating Body of Knowledge (CEBok) Now Available From SCEA
  • software as a service on Churn Rate For On-Demand (Software as a Service) Solutions
  • Ben on Open Source Software Is Not Free
  • galorath on Defense Acquisition Guidebook From DAU

• Galorath Company

  • Galorath International
  • Galorath.com

• SEER sites

  • SEER for Hardware, Electronics & Systems Project Management
  • SEER for IT – IT Project Cost Estimation
  • SEER for Manufacturing – Project Estimation
  • SEER for Software – Software Estimation

• Meta

  • Log in
  • Entries RSS
  • Comments RSS
  • WordPress.org