Last update: 02/06/2016 13:53
Here's a real example of the remarks formulated by the Agile Ambassador (Scrum Master) of an Agile Team.
Here are my remarks (no blame, just brutal facts) of the standup meeting of this morning. In blue, the remark, in green what we should do and why we need to do it (comments are welcome and we may need to take this for the retro of the end of the week). We of course change few names so that it can be spread in the hope it can help others too…
- Started at 09:34 - Janet online at 09:35 … we need to make sure everything is prepared to start sharp on time, which is 09:30 in our case (so that nobody wastes time)
- New tasks discovered during standup not reflected on Kanban board (e.g. new page) … we need to make sure these get reflected immediately (and prioritized on the spot with the help of our Product Owner) otherwise we tend to forget them
- Homepage deployed to beta: no card … we need to make sure all we need to do is reflected on the board so that we realize how much work is involved
- Jira not used for cards and tickets in Jira not reflected on Kanban (except new card that Dave put on the board for a defect) … there also, we need to make sure everything is reflected, not only for other people to notice (so that they realize how much work is on our plate), but also for us as to not forget about tiny details that may reveal important in the end
- Speaking about tasks without showing them on the board (are they reflected on the board?) … it is better to stand up, to go to the board, to show (point to…) what you've dealt with, and move the cards to the right of the board
- Tobania here twice a week … it would simplify communication to have GreatConsulting here 2x/week and it would also synch most parties (NewConsulting is supposed to be here as of next week)
- No work foreseen to prioritize backlog … even though marked as of PRIME importance, I noticed that no one is really paying attention to it, leaving it out of our view. Once again, this is of PARAMOUNT IMPORTANCE. We should no longer skip it!
- No new ticket to organize Sprint Planning for iteration #2 … together with the prioritization of tickets/cards of Sprint 1, we urgently need to organize the planning of Sprint 2; if not done today, we will be 60% behind!
- No goal set on iteration #2 … closely related to the remark above and before above, is the fact that we have no easy goal to remember what Sprint 2 is all about. We need a 1-sentence objective for every sprint (just a few words can also do)
- Many cards in “Doing” were not discussed … we need to see more the point of view of a task and not let cards stagnate in muddy water. This will also improve our morale!
- Shortcomings of Sprint 1 are still missing on the kanban board … this needs to be written down as the demo goes on so that we do not forget about these things later on. If needed, I will be happy to give a hand because I know it is not easy to demo something and to take notes simultaneously
- “Impediments Lot” not examined and not materialized as tasks on the board … impediments need to translate into actions, actions need to translate into cards on the kanban board. If this is not done, then the impediments hardly get resolved.
- Common “Code repository” not on kanban board … this is essential for a sound organization of the department so that we can also simplify deployments and, hence, testing. As we have seen during the last sprint, deployment and getting all things right seems to be a time monger (more than 6h to adjust). We need to make sure this gets done in a fraction of the time for this sprint (or aren’t we in a position to do so?)
- Standup meeting finished almost on time (09:46) … but continued with content … that should be discussed in a Sprint Planning session so that all parties would benefit the discussion (lasted until 09:57)
I hope that this will help us improve over time.