Development Archives

Clean Code, Ugly Code, Technical Debt and CleanUp Stories

By Dan Rawsthorne | November 13, 2014 |

One of the things most Agilists harp on is the need for Clean Code: Code that can be easily extended and maintained, and that Coders shouldn’t be afraid to work with. But, what does this really mean?

The “Sashimi Method” for Building Software

By Dan Rawsthorne | October 8, 2014 |

So… we know that we’re supposed to be developing software incrementally, using an agile process like Scrum. We know we should be building our software a little bit at a time — coding, testing, and reviewing as we go, right? What does this actually mean? What do the increments look like? How big are they?…

WIP, Scrum and Kanban

By 3Back | February 11, 2013

Work in Progress (WIP) In kanban, the Stories that the Team is currently working on. (see Front Burner) Kanban, is simple work item flow for teams. The word kanban is a Japanese word that comes from Toyota and translates as card.

What Makes Good Stakeholders in Scrum

By 3Back | February 8, 2013

Stakeholders are the reason we develop Product in the first place. Stakeholders are those people that have needs, wants, and desires (desirements).

Stories Too Big – Stories Too Small – Stories Just Right

By Doug Shimp | February 23, 2011 |

Analysis will be controlled such that the stories tend to be just right. About 10 stories in a sprint is a good rule of thumb. We call this application of sizing “The Goldilocks Theorem”, Dan.

Clock Watcher Connie

By 3Back | February 14, 2011 |

Know a team member who sits in meeting with their arms crossed and brows furrowed?
That would be…

Teams: Meet Jake.

By 3Back | January 28, 2011 |

Teams: Thriving on consensus, Jake needs to know all the opinions before we make any decision at all. He takes everything personally! The c…

Why should a ScrumMaster be a Master of Learning?

By 3Back | January 17, 2011 |

Listening to the product. Communicating in daily stand-ups. Solving the problem. They all have one thing in common. Learning. Every time we share inform…

Scrum Values, Visibility and Trust Loops

By 3Back | August 22, 2010 |

Some fundamentally disagree with this statement. For those that disagree Trust is given freely. They give trust freely until such time as a person irrevocably betrays that trust. They believe that this leads to a method of management that creates hostile antagonistic workplaces rife with fear. A pattern of mistrust is established that leads others to be mistrustful and perpetuates a negative cycle of oppression.