Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

How should the program office describe their technical reviews when they are using agile software development methods?

April 26, 2017agile methods Office program Reviews Software Development Technical

0

Posted

How should the program office describe their technical reviews when they are using agile software development methods?

1 Answer

0

Posted

To be of value in determining the technical maturity of a system, technical reviews must be event driven. Event-driven reviews are not only required by DoD policy (reference the USD(AT&L) policy memorandum, dated Oct 22, 2004), but are also a fundamental part of most industry best practices. Programs using any development method should ensure that method provides for event-driven technical reviews (that is, reviews having entry and exit criteria quantifiable in technical baseline completion terms). Methods that do not have such provisions, while seemingly “agile,” often lack the ability to measure technical maturity to objective measures.