Well my current experience is that the answer is a sounding YES.
Developers love to develop software using Scrum. The motivation and positive energy just explodes. People talk together, build as a team better products and enjoy the daily activities.
Stakeholders and in particular customers or users embraces the advantages they get.
Still a whisper can be heard that yes is not without consequences for the organization.
Wednesday, February 24, 2016
Thursday, January 21, 2016
Minimizing Undone Work when Working with Regulatory Departments
The Scrum and agile mantra is to have a "ready to ship" product each time a sprint is completed. You must avoid any incomplete activities at any price.
Incomplete activities are also called Undone Work; they are technical debts in your software, hindering its delivery to customers.
Regulatory and traditional quality insurance departments requests all kinds of documents such as review, test results, risk analysis matrix to insure that their view of quality is fulfilled.
Scrum sees quality similar to the lean production approach. Quality is build into the product and you do not need any documents proving you have fulfilled this goal. Your sole goal is to optimize the process to produce best products, not to repair them after production.
Subscribe to:
Posts (Atom)

