This is the governing body for certification in Disciplined Agile.
LIVE CHAT 24 HOURS PER DAY
Ensure Stakeholder Readiness - Active Stakeholder Participation
All the presented options will work better if we will involve the stakeholders in the development life-cycle and we will also prepare the transition and deployment together (not only communicate).
Ensure Production Readiness – Option: alpha version
Fore cases with high incertitude, high complexity (as major versions or major product upgrades) could help to have also an alpha version (integrated, tested, but without all the features, only with most valuable ones) of the product that could be validated with the customer. Could be a sub-option of the beta/pilot option.
Ensure Production Readiness – Option: reverting to the last version
Fore cases with high complexity, reverting to the last version (after deployment and critical problems) could help a lot. For example. from Kent Beck talks and articles I understand that Facebook put this aspect before other validation ways.
Had a quick look.
I work in an organisation currently that has got some real strict and draconian governance rules and regulations (I call them hoops that needs to be jumped through) to get something out into production. This include legacy governance rules as well as security and compatibility rules.
Just a question: Are there prescribed options (perhaps with ITIL or CSM or anything else that may be out there) that we need to mention?
We've just published the excerpt for the Transition phase goal Ensure the Solution is Consumable.
Please post your feedback here.
Thank you in advance.
© 2013-2019 Project Management Institute, Inc.
14 Campus BoulevardNewtown Square, PA 19073-3299 USA