All posts filed under: scrum

The Role of the Scrum Master

Leave a comment
scrum

I’ve stumble upon this list, and I like it – as it clarifies again a bit the role of the Scrum Master. Source: https://age-of-product.com/70-scrum-master-theses/ Scrum is not a methodology, but a framework. There are no rules that apply to each and every scenario — just practices that have worked before in other organizations. Successful practices of other organizations cannot simply be copied to your own. Every practice requires a particular context to work. You need […]

Done!

Leave a comment
scrum

The most important objective of a sprint in Scrum is to deliver a DONE product increment – a piece of working software delivering value for the end-user. That is the goal today, and always has been the goal. In a context, in which multiple Scrum teams work on the same product, it’s the goal – and only goal –  to deliver each (and every) sprint an integrated product increment – so no UNDONE work left […]

Scrum – It is what it is.

Leave a comment
scrum

And I don’t intend to say that with a negative perspective. Quite often people wonder why Scrum – a framework for complex product development – has the rules as described in the Scrum Guide. The authors of Scrum (Ken Schwaber and Jeff Sutherland) say that the framework contains the roles, events, artifacts, and the rules that bind them together necessary to operate. Adding, changing or removing something will not make it Scrum anymore and a […]

Scrum Master

Leave a comment
scrum
Scrum Master

“A good Scrum Master helps the team to solve their problems, helps them to reach the sprint goal.” “A great Scrum Master helps the team to solve the most crucial problems, creates an environment for the emerge of new practices and emerging knowledge.” Source: A Scrum Master’s Practical Toolbox Image: http://paulheidema.com/wp-content/uploads/2014/04/Blog-graphic-scrum-master.png

Challenging Sprint Retrospectives

Leave a comment
continuous improvement / scrum

For the readers: A reference for organising retrospectives is the book “Agile Retrospectives – Making Good teams Great”, by Esther Derby & Diana Larsen. They describe the main steps of an agile retrospective. The prime directive of retrospectives has been formulated by Norman Kerth in his book “Project Retrospectives: A Handbook for Team Reviews”. “Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they […]

Ken Schwaber’s original Scrum Paper (1995): “SCRUM Development Process”

Leave a comment
scrum

ABSTRACT. The stated, accepted philosophy for systems development is that the development process is a well understood approach that can be planned, estimated, and successfully completed. This has proven incorrect in practice. SCRUM assumes that the systems development process is an unpredictable, complicated process that can only be roughly described as an overall progression. SCRUM defines the systems development process as a loose set of activities that combines known, workable tools and techniques with the […]

What is the Daily Scrum for?

Leave a comment
anti-patterns / scrum
Daily Scrum

The daily scrum / daily stand-up / daily huddle. Oh well. The good questions are: 1. What have you done yesterday that contributes to reach the sprint goal? 2. What will you do today that contributes to reach the sprint goal? 3. Do you encounter any impediments/issues/problems that prevent you from reaching the sprint goal? The habit of each person listing all the things he has done yesterday, and what he will do today is […]

True cross-functional product development

comments 2
scrum
Real sprints

“Cross-functional” collaboration in (agile) product development means that the whole (complete) product “development” team is participating. Scrum talks about a “development” team, without distinction of role. As such, “developer” means any competence or skill required to create the product or service, not limited to “programming” (writing code). Lean UX heavily promotes the whole product development team participating during the complete product development cycle, from the very beginning. The whole team approach aims to create a […]

Scrum… is a means to an end, a tool designed for a purpose: people, agility, value.

comment 1
scrum
The house of Scrum

There’s no need to re-describe Scrum. If you’re on a journey to discover Scrum, I welcome you. I do advice you to learn more than Scrum, and to also discover agile & lean. I greatly recommend the collection of articles by Mike Cohn and Alistair Cockburn. After attending a few presentations and after reading the small book “Scrum, a pocket guide”, I pleasantly appreciate Gunter’s writing on the topics of Agility and Scrum. I do […]

Descaling organisation with LeSS (Large Scale Scrum)

Leave a comment
scrum

As you explain, the framework is simple. Likewise Scrum, it’s painfully simple. As Ken Schwaber once said (I believe): “Scrum is like your mother-in-law, it points out all your faults.” Each organisation has an enormous untapped potential to deliver more value, more rapidly, more frequently. But reality is different, small and large organizations have and maintain (anxiously) the traditional organizational model. How difficult is it to transform to a networked organization, stimulating self-organisation and a […]

My impression of LeSS (Large Scale Scrum) practitioner course

comments 2
scrum

Large Scale Scrum (LeSS) is for me an honest framework which embraces Scrum (for 1 team). LeSS does not introduce any additional layers of governance, it does not compromise to fit with existing traditional organization structures, it does not compromise on the delivery of value. Indeed, LeSS is much more about organisational (re)design than about introducing Scrum. Before “scaling up” to multiple teams, an organization must be able to adopt Scrum on the team level, […]