“The gaps that I will note below are those things not mentioned in the Scrum Guide.”
An extract from this recent post –
The 2016 Scrum Guide doesn’t mention:
- Jenkins, Git,
- Senior Scrum Master
- Gluten free food types…
I could add more ‘things’ that the scrum guide doesn’t contain. What’s the point?
I have an issue with this post, as I probably do with SAFe and other scaling approaches that have ‘certification’ sitting behind them, with c$900 yearly renewal fees.
From the Guide – Scrum is ‘…framework within which you can employ various processes…’. Scrum can address ‘complex adaptive problems’ and uses empirical process control to allow for:
- Inspection, and
Scrum is – Lightweight, Simple to understand BUT Difficult to master. What makes it Difficult? From my perspective and from what I’ve experienced within organisations; it is holding on to old mindsets, habits and ways of knowing that builds judgement, cynicism and fear in to this simple process – amongst other things.
Something that is so simple, is complicated and made difficult by people, teams and organisations that want to NOT be responsible, NOT be accountable, NOT self-manage and NOT trust ‘them’ – it’s them, not us, that’s why it failed!
The post says that Scrum has 5 Gaps; Clarity, Commitment, Ritual, Progress, and Habit.
Clarity within Scrum is gained by people talking and sharing information through it’s founding principle of Transparency and having a shared common understanding of what ‘Done’ is.
Commitment (an objective set) and this can be a tricky word and value for sprint teams to adopt – we are NOT committing, we are setting the expectation and objective?
So, Commitment and Progress can be measured (if you want to measure, rather than look at business / user value being delivered) by the four formal events for inspection and adaptation, as described in the Guide:
- Sprint Planning
- Daily Scrum
- Sprint Review
- Sprint Retrospective
What gaps are left: Ritual and Habit. These two ‘gaps’ can be associated and embodied by teams (inside and outside of product or software development) who live the Scrum Values of: commitment, courage, focus, openness and respect.
Consistently having action (a ritual) to embody these values and mindsets that hold on to positive, life affirming, appreciative habits will build teams that deliver, trust each other and bring about a sense of collective purpose.
Personally, I don’t see how you can not apply the Scrum framework (and values) to not just the project or team sprint level but across the organisation at the programme and / or portfolio level.
Shared from Lyssa Adkins:
And not just for IT or product work, contextual use and ‘what’s good enough’ flexible, adaptive approaches, with aspects of Lean / Kanban can play substantially to the systemic organisational ‘whole’, without the need for more complicated, process, artefact heavy frameworks and keeping the focus on ‘people‘.
I am a Coach and I work with people, teams and organisations to help them be curious about their potential to self-manage, be whole and share their collective purpose.
I am not technical – I cannot code – I cannot build continuous integration deployment platforms. I will display humility and be humble in this professional, skilled domain and will trust those that know, to know.
However, if they lack the belief or confidence to know that they know or how that might take the first steps, then I can coach them.
If the Product Owner is not sure about telling the user journey – together we can explore that journey through a coaching relationship.
If the team want to explore greater trust and to challenge (management or each other) – then together we can explore what ‘trust & challenge’ would feel like.
I am a Coach – I work with: relationships, identity, ambiguity, confusion, uncertainty, dilemmas, visioning, creativity and innovation.
I explore the curious, and hold the potential for you, to a point when that potential can be held by you to achieve greater performance.
Thank you for reading.
Inspired by many things but for this post – Reinventing Organisations / Theory-U / Lyssa Adkins / The Scrum Guide.