Agile Adoption & Transformation: Principles, Challenges, Pitfalls by Brian Will

Author:Brian Will [Will, Brian]
Language: eng
Format: epub
Publisher: eBook formatted by www.writingnights.org
Published: 2018-06-24T23:00:00+00:00

The Product Increment Crashes and Burns

This should never happen, but sometimes it does! If the development team uses continuous integration and automated unit testing, the basic stability of the system should be guaranteed.

If, for whatever reason, a late-breaking change introduces instability, it is better to cancel or reschedule the sprint review meeting.

The reason for the latter is simple: a) to not waste other people’s time, and b) to avoid creating a bad impression.

It is better to say “It’s not working yet, we have to reschedule” than to sit in a meeting and say “Oops, I don’t know why that’s not working.”

As a matter of process, the development team and the product owner should test drive the product increment before showing it during the sprint review meeting.

A general guideline to follow is to finish up all development, testing, integration, and documentation activities the day before the scheduled sprint review meeting, in order to give the team enough time to make sure everything is in good order.

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.