The kick-off is a moment to assure the right understanding of what is required for a given story card before the development work starts. The goal is to give clarity around assumptions made and technical related matters can also be discussed in the moment. For example, the approach on how to test the outcome of a story can be discussed. For that moment we can have a BA and the dev pair that will start developmet. The PO is also welcome to be here, asking questions and facilitating the discussion.
- Do we have sufficient information around the need for that story?
- Does all AC's (from that card) are clear and make sense given the objective of that story card?
- Do we have dependencies for that card to be played?
- Do we have technical information around that card.
The desk-check is a moment to quickly verify what happened in the development of the story. The story is working as supposed to work? ACs are being satisfied? These are quick checks that can be made against a local environment just in order to understand if the main functionalities of the feature are according expectations. For this moment we can have a BA, the person that will conduct the QA and the pair that worked on the story.
- All ACs are satisfied?
- Manual testing was made in order to assure the story goal.
- Do we have automation testing for the story? Which kind of automation we have? Is it giving us security to really know the feature is working as supposed to work?
- Is it following our actual testing pyramid?
- Code produced follows best practices or follows a defined standard?
- Story was double checked in a beta environment?
- Do we have a feature toggle for the card?