Skip to main content

Towards Agile Talking Points [was: Towards an Agile Litmus Test]

Last week, I published a poll which tried to identify criteria for an agile litmus test.  I wanted some talking points to complement the Nokia test as I start to coach a new agile project. There seem to be strong feelings against testing. The inquiry generated little enthusiasm on dzone, whereas Michael's criticism of these tests came up strongly positive.

As I started the above mentioned project, I discovered that the questions I proposed were not that helpful.  The real problems become obvious very quickly as I watched the team do its sprint retrospective and sprint planning. Reacting to what I see is more important than doing an academic evaluation.

As I write this article, 8 people have voted on the poll. Not exactly the wisdom of crowds, but you can get an idea of what people consider important. Here are the top vote getters:
  1. Colocated: Is the team colocated? - 8
  2. User Stories: Do you define the product in terms of user stories? - 8
  3. Releases: Have you delivered running, tested, usable functionality to users at least twice in the last six months? - 7
  4. Continuous: Do you do continuous build / test / deploy? - 7
  5. Retrospective: Does you team conduct a retrospective after every iteration? - 7
  6. Testers: Do you have testers? - 6
  7. Bug DB: Do you have a bug database? - 6
  8. Access: Does it take less than three days from when you have a question to when an expert answers it? - 6
  9. Build: Can you build in a single step? - 6
  10. Talk: Does everyone talk to each other, constantly? - 6
One of the more interesting suggestions in ensuing the discussions was, When starting a project, I should not be looking for practices, but rather but looking for smells (or symptoms). I could identify a couple from the questions in the poll:
  • How many releases have you put out in the last 6 months? ( 0 or 1 is a problem)
  • How much effort is required to build and test the software?
  • Does fear play a role in deciding when to give the boss bad news?
I still think it is useful to have some tools and approaches, readily available in my backpack, for "debugging" an agile development project. Some would be used when talking to management about their problems, to convince them of the need to do something. Others might be asked of the team in the course of a retrospective. Still others might find their way into an Agile RFP, so that non-agile companies don't make the cut.

Question for you, gentle reader: What are the symptoms and smells of bad software development and especially bad agile development?



Comments

Popular posts from this blog

Sample Definition of Done

Why does Scrum have a Definition of Done? Simple, everyone involved in the project needs to know and understand what Done means. Furthermore, Done should be really done, as in, 'there is nothing stopping us from earning value with this function, except maybe the go-ahead from the Product Owner. Consider the alternative:
Project Manager: Is this function done?
Developer: Yes
Project Manager: So we can ship it?
Developer: Well, No. It needs to be tested, and I need to write some documentation, but the code works, really. I tested it... (pause) ...on my machine. What's wrong with this exchange? To the developer and to the project manager, "done" means something rather different. To the developer in this case, done means: "I don't have to work on this piece of code any more (unless the tester tells me something is wrong)." The project leader is looking for a statement that the code is ready to ship.

At its most basic level, a definition of Done creates a sh…

Scaling Scrum: SAFe, DAD, or LeSS?

Participants in last week's Scrum MasterClass wanted to evaluate approaches to scaling Scrum and Agile for their large enterprise. So I set out to review the available frameworks. Which one is best for your situation?

Recently a number of approaches have started gaining attention, including the Scaled Agile Framework ("SAFe") by Dean Leffingwell, Disciplined Agile Development (DAD), by Scott Ambler, and Large Scale Scrum (LeSS), by Craig Larman and Bas Vodde. (Follow the links for white papers or overviews of each approach).

How to compare these approaches? My starting point is Scrum in the team. Scrum has proven very effective at helping teams perform, even though it does not directly address the issues surrounding larger organizations and teams. An approach to scaling Scrum should not be inconsistent with Scrum itself.

Scrum implements a small number of principles and constraints: Inspect and Adapt. An interdisciplinary Team solves the problem. Deliver something of va…

What is the role of a Business Analyst in Scrum?

When I teach a CSM class, my goal is that my participants go home delighted (and of course that they learn about Scrum, that they are motivated to do Scrum, and can pass the online CSM exam). So after every class, I ask for feedback, in particular what could I do to get a better score. And for the next class, I strive to implement or address two or three of the points raised by my participants.

One issue that was raised was unanswered questions. It is annoying to ask questions and not get answers! Time is limited, so it is not always possible to answer all questions, so I thought, why not answer them on my blog? So here goes, first question:
What is the role of a Business Analyst in Scrum? This question is a challenge because Scrum doesn't answer this question! Scrum is a simple, team-based framework for solving complex problems. The roles and ceremonies in Scrum are designed to ensure that inspect and adapt can occur regularly with complete and correct information. Scrum does not…