Archive for Confessions of a Agile Scrum Master

Requirements in Agile Development

There is often a misconception in Agile software development that there is no longer a need for Requirements. Though it is certainly true that Requirements have been misused and processes have specified large unreadable documents, the need still exists to have a documented concise and user-focused view of the system under construction. Much is written [...]

Agile Dysfunction Series Part 1: Lengthening the Sprint

The Importance of Small Chunks of Work Every Agile Software Development Team understands the importance of tackling work in small chunks the team can commit to truly finishing in a short period of time – meaning specifying, developing and validating.  Small pieces of work are more easily estimated and relatively sized.  Small work items can [...]

Agile Principles & Scrum Practices

The Difference Between Agile & Scrum When asked to explain the difference between Agile & Scrum, I find it helpful to think in terms of principles and practices: Principles of course are those large ideas that guide what we do Practices are the actual things we wind up doing An example of an Agile principle [...]

Software Development Testing. What is the problem?

No one would argue that testing is important. But among the people that I speak with regularly the prevailing opinion is that it is never done enough. What is the problem?

Agile Software Development Teams – It’s Never Been This Good!!!

By · April 19, 2012 · Filed in Confessions of a Agile Scrum Master · No Comments »

I’ve been involved with software development for over 30 years. That’s a lot of projects, roles, deadlines, meetings and team members. In all that time there have been some recurring themes. One of them is the “death march”.