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.
The definition of done is one of the most simple yet most effective activities you can use with your Agile team. This post explains some the reasons why the definition of done is important and provides some useful tips on recognising how to create one for you team using some examples.
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.
Thought Works Studios Best Card Wall competition.
Inspired by the Book “The Goal” by Eliyahu M. Goldratt, this presentation explores the effects of applying the Theory of Constraints. A simulator was used to mock a physical workflow over 500 days and the result are discussed. A thought provoking topic which explores a fundamental principle of Agile workflows as well as comparisons to manufacturing environments.
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.
There are many benefits of using MVC and lot’s of frameworks are built on it. When structuring your code it is useful to understand the basics. This post is a really simple of the MVC structure abstracted into layman’s terms using an everyday example we should all be aware of.