1st Conference 2017, Melbourne. Scrum: Declutter. Optimise. Deliver.

How do you unclutter the dogma surrounding Scrum’s 20 year history? Can you find its powerful Lean, user-centred powerhouse for collaborative improvement? Some people throw away Scrum after a while through the false belief that its just for newbies, but when you get back to Scrum’s origins you can find a treasure trove of simple Patterns that help teams improve collaboratively using the Scientific Method.

View the presentation on Prezi: http://prezi.com/yrkbbgottdqn/
This presentation by ZXM’s Partner for Digital Transformation, Matthew Hodgson, at 1st Conference, Melbourne 2017, looked at:

  • Scrum — What is it at its core?
  • Scrum myths
  • Back to basics — Team size, Sprint length and making key Scrum events
  • Scrum as a Lean practice with learning hypotheses
  • How to improve productivity by +200% in a few months by just doing “good Scrum”

About the author

Related Posts:

Better together: Agile + Lean UX

How do you make Design Thinking, Lean UX, and Agile work together. Sprint 0? Design Sprints? Upfront design and planning tends to delay the delivery of value, so there must be a better way to use Scrum but also engage in discovery work at the same time without devolving into parallel design work. Integrating design, user research, and experimentation into Sprints is the key.

READ MORE

How do I run a Sprint Review?

The Sprint Review is one of five events in Scrum. It’s purpose is to inspect the Increment of work, get feedback, and then adapt the Product Backlog. And while many people refer to the Sprint Review as the “demo” or “showcase”, this is only one aspect of the Sprint Review.

READ MORE

How do I run a Daily Scrum?

Many people use the Daily Scrum to provide a status report to the Product Owner or Scrum Master, and even to stakeholders, but this event plays a more critical part in ensuring that the team continues to stay focussed on their goal and adapt their work so they improve their chance of achieving it.

READ MORE

Setting up a New Agile Team

When setting up new agile teams we have found that starting small with the basics and adding patterns as they start to develop capability has helped us get new teams up and running within 2-3 days and acheive a baseline of agile capability within 3 months

READ MORE
search previous next tag category expand menu location phone mail time cart zoom edit close