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.
An interesting session demonstrating how to use some of the ideas that the ToC teaches us and how we apply them to our Agile methodologies.
Retrospectives can be one of the most valuable sessions in Scrum and Agile teams. Often they can become boring and less useful to the team and they can fall into an administrative process with less value. This post is about sharing a recent retrospective session that was fun, engaging and got results using a Top Gear theme to explore, identify and resolve issues to benefit the team and ultimately the business.
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.
Using cumulative flow diagrams to observe workflow within sprints can provide valuable, visual input for teams. Unlike the sprint burndown chats, CFD”s look at the lower level of tasks to see what goes on closer to the work getting done. Used with the burndown, a cumulative flow diagram can be a useful learning aid to support retrospectives, continuous improvement and feedback.
There is nothing worse to destroy a team culture than people working with the confides of a job title. Emphasising roles creates dependencies, bottlenecks and blame cultures and as a result, reduces productivity through knowledge silo’s and counter productive workflow methods.
Barcelona Scrum Gathering 2012. Using TDD and BDD to help your team understand what to build high quality working software.