Skip to main content

Towards Agile Support

2 years ago, Anton Schultschick, Leader of IT Support for the EE Department of the ETH Zürich attended my /ch/open workshop on Scrum and got curious about Scrum. 6 months ago, he attended my Scrum Jumpstart with the goal of solving a problem: "My support group has to deal with daily business and we have to successfully complete medium term projects. But the needs of daily business are consuming all our time. We keep the IT running, but we have difficulties with projects. How do we reconcile the two?"

The answer wasn't strictly speaking Scrum. Daily business problems require shorter reaction times  than multi-week sprints would allow. But he did bring home many tools which he could apply to the problem. Today he gaves us a look into what he and his team did:
  • Big Visible Task Board(s) galore - for project backlog and the individual projects
  • Weekly iterations for projects 
  • Demos instead of reports
  • Retrospectives
  • Introducing the Product Owner concept into the daily work. Someone who is interested in and will drive results.
Some things he did not do: there is no daily scrum for support -- the discussions proved not to be very useful -- and there is no Scrum Master. He did not go for electronic tools (which provoked some interesting discussion, initiated by a Webinar participant, about why should you use the "primitive" tools -- Short answer: the big visible taskboards are better for communicating with and motivating people -- the people who produce a ticket own the ticket.


Personally, I think this could be the start of a "Scrum for Support" (Let's call it "Scrimmage" - you heard it here first) - a few simple rituals, roles and artifacts which help you do Support well. I've heard Kanban is getting attention in this area, so maybe that's the solution. But there is something essential about the rhythm of a sprint, which Kanban, a flow oriented framework is missing.

There were several people in the room confronted with the same problem, so I hope they will find each other on our Community Site, and start a discussion about what a "Scrimmage" could be!

If you're interested in Kanban, check out Karl Scotlands Lean and Kanban 101 Tutorial at the SwissICT Lean Agile Scrum Conference next month in Zürich. I know I'm looking forward to this talk!

Links:

Comments

Daniel Marbach said…
Hy Peter,
I just announced your cool article on planetgeek.ch! I used some of the words you wrote in the article. Hope you don't mind!
Daniel

Popular posts from this blog

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…

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…

10 Warning Signs, that your team is not self-organizing

How do you know that self-organization is working? The Bern Chapter of Scrum Breakfast Club looked into this questions, and identified the following warning signs (which I have taken the liberty of translating).

The team reports to the Scrum Master at the Daily ScrumPeople wait for instructions from the Scrum MasterTeam members don't hold each other responsible [for their commitments]The same impediment comes up twice"That's the way it is" => resignation"I" instead of "We"Flip charts are lonelyCulture of conflict-avoidanceDecisions processes are unclear, nor are they discussedPersonal goals are more important than team goals
To this list I would add my a couple of my favorites:
you don't see a triangle on the task board (not working according prioritization of stories)after the daily Scrum, people return directly to their desks (no collaboration)there are a least as many stories in progress as team members (no pairing)
P.S. You can join the …