January 2017

Speed of development is a benefit of Agile software projects but can have an undesirable side effect. Software that developers deliver in an iteration (e.g., Scrum sprint) might work but not have the same level of quality, reliability, or consistency as more “polished” code. The team might also take credit for finishing a user story

Ideally, all your Agile team members agree with The Agile Manifesto, complete their tasks on time, raise concerns immediately, and are fully committed to the success of your organization and its customers. In the real world, of course, this is rarely the case. Most likely, your team will include people with varying levels of commitment

Maybe you’ve received a mandate from upper management to become Agile. Or maybe your organization has asked you to expand Agile from just software development to other parts of the enterprise. To ensure a successful transformation, the following article (Dynanet_Prevent Agile Crash and Burn) identifies 8 steps to success.