#No Projects – Teams not Projects

May 30, 2016 0

Allan Kelly outlines the #NoProjects agenda and discusses the role of teams as the unit of production and the team life cycle. Good projects make for bad software. Software which is useful is used and demands change, stop changing it and you kill it. In a world without projects how do you manage work? The answer is teams. Teams are the means of production, work should be based around teams and teams should be stable.

User Stories Are Not Requirements

May 23, 2016 1

The creation of Agile approaches was also a reaction against huge and useless requirements documents, either textual or using modeling techniques like UML. All the values of the past should however not be discarded in the requirements activity. In his book “Agile Software Requirements”, Dean Leffingwell explains how user stories are different from use cases and software specifications.

The Systemic ScrumMaster

May 19, 2016 0

Most ScrumMasters are quite fluent in “Scrum”, but they lack experience in System and Complexity Thinking. Most projects don’t fail because of the wrong tools, but because of people and a missing understanding about the system that we are all part of.

Scaling with an Agile Leader

May 17, 2016 0

Using an Agile approach for software development does not necessarily guarantee success. As Henrik Kniberg wrote at the beginning of his blog post ” Even if the entire organization is neatly organized into scrum teams, you can still end up with an unaligned mess!”. Having an Agile leader can help preventing the unaligned mess.

Is Scaled Agile Framework (SAFe) evil?

May 9, 2016 1

The Scaled Agile Framework (SAFe) is controversial. At first glance SAFe looks a bit like a big scary heavy-weight top-down RUP-zombie. But what about in real life?

Five Rules for a Minimum Viable Product Strategy

May 2, 2016 1

The Minimum Viable Product (MVP) is defined in Wikipedia as “a product which has just enough features to gather validated learning about the product and its continued development.” In this article, Sergiy Andriyenko proposes fives rules to apply successfully a Minimum Viable Product strategy.