Management - Do you have a "Release Update/Debrief Meeting" on a weekly basis?

Updated by Tiago Araújo [SSW] 11 months ago. See history

123
No component provided for introEmbed
  1. Status of original work items - are they all done?
  2. External Test Please - go through the application and get the clients thoughts. Many issues they see, will already be reported by the internal "Test Please". Send emails to the new ones.
  3. Triage these additional work items - try to move all to the next release
  4. Approval for additional work items/budget overruns - talk $$ e.g. look at the "Actual" and "Estimate" figures on the top of the report
  5. Release sign-off - "Yes" or "No"?

If "Yes"

  1. Ask the client for a mark /10 for the release
  2. Ask the client if you can do a deployment to Production?
  3. Ask for Approval for next release

There are tools to help you do this:

Image

Figure: The actual output of the Release Update Report

If you are at the end of a main section of work, promote your success

Acknowledgements

Adam Cogan
Related rules

Need help?

SSW Consulting has over 30 years of experience developing awesome software solutions.

We open source.Loving SSW Rules? Star us on GitHub. Star