Writing user stories in Agile can be very difficult. Although it appears simple, it can take time to perfect at technique which works with the team. This post provides some useful insights into ways in which you can improve your story writing technique taking some examples from XP, INVEST and BDD using Gherkin.
Sometimes it can be time consuming or difficult to decide what to do next. Often you can end up working on the next item in a list, but this may not necessary be the most valuable thing to do. This simple and visual focusing technique can help teams decide what to take on given that there is limited time and the most value wants to be achieved.
As we have progressed as a scrum team, our board has evolved in line with our continuous improvement ethos. Heavily influenced by the Theory Of Constraints, we introduced WIP limits on user stories and the board by restricting the number of lanes. We have seen team and productivity benefits when adopting some of these simple changes.
The concept of bugs has been around since the early days of software and we treat them the same now as we did then. When working by value from a single backlog, we should think differently by thinking by value. Do bugs really exist ? Do we put bugs in the product backlog ? What value to bug tracking tools really have ?
We decided to change our scrum board to look a bit more fun and interesting. So we created a web like board aka the “Super Hero Scrum Board” based on a “Bulls Eye” concept. Not only is it more fun and interested, but it creates a visual focus on Done.