SCRUM version X

Published Jan 12, 2018
SCRUM version X

I would like to share my views and observations on different versions of an Agile process that's currently being practiced. I would also like to suggest some ideas from a developer perspective.

To begin with, Agile is something that every development team talks about. To be honest, everyone has their own version of SCRUM. Some popular versions are:

Forced SCRUM

A management decision that we follow SCRUM — you have no choice. Just follow.

I know (Bossy) SCRUM

Boss thinks he knows everything about SCRUM after two days of training and preaches it to others.

We don't care SCRUM

Team doesn't care what methodology is being followed — just follow my own methodology.

Waterfall SCRUM

Wrap waterfall way of working with SCRUM. Nothing changes - just a fancy term.

Custom SCRUM

A mix of multiple process and policies into SCRUM — use it as a tool.

Have you seen any other versions? If yes, comment below.

So what is a SCRUM really for for a developer/team? It's a slow evolving process of working collboratively and sharing knowledge to deliver a common goal.

These simple questions will make you rethink your SCRUM version.

Are you:
Developing incrementally?
Ready to share knowledge?
Ready to discuss what you are going to build and how?
Ready to discuss your problems?
Ready to self manage from all perspectives?
Comfortable to say NO to your PO, SM, and peers?
Ready to learn and improve?

If your answer is No to any of the above questions, you are following one of the X versions of SCRUM.

What is a terrible combination of roles/designation in SCRUM teams?

An individual is a: PO, SM, BA, TL, and sometimes QA - team quits.

An individual is a: SM, BA, TL - team members are worker bees and you have a dictator.

Ideal combination:

1 Business Analyst (Analysis of all stories, interacts with PO, certifies QA report)
1 Technical Consultant / SM (Provides technical guidance for the team, hands-on development)
2 Senior Developers (Proper code, unit and integration test, dev-ops)
1 Junior Developer (Continuous improvement with guidance from others)
1 Quality Analyst (Scans through the deliverables and generates quality report)

Ideal SCRUM roles:

From the above ideal team:
BA - Planner, functionality, voice of the team.
SM - Facilitator, arranges all SCRUM ceremonies.
Developers - Active participants, occasionally play other member's role.
QA - Documentor, documents all ceremonial outcome.

Ideal SCRUM rules:

No monitoring individuals, evaluate as a team.
No individual uses their designation as a tool to override the teams protocol.
Dare to fail, but learn to succeed.

Having said all of the above about SCRUM versions, I do acknowledge some wonderful companies, teams, and individuals out there who follow SCRUM at its best and are reaping the benefits of it.

Why don't we do the same with our team?

Discover and read more posts from Murali Murugesan
get started