It is absolutely true that a correctly set up team of professionals does not need a dedicated Scrum Master.
Problem statement: However, sooner or later, they will fall in the trap of the everyday ordeal. You can easily recognize it by retrospective action items not done, or a messy Jira, or continuous overcommitment. There might be other signs, specific for your team.
As to why it happens: The answer can be found in team dynamics. Sooner or later, the team reaches the stage after "form-storm-norm-perform". This stage still does not have a name. It is characterized by the old "common sense" taking rule.
Solution: This is the right time to reintroduce the role of the Scrum Master. It must be someone with knowledge of the project history, as well as with a lot of trust from the team. The only missing ingredient from the recipe is human interaction and dedicated discussions on how to overcome the good old common sense. For inspiration how to continue, refer to Beware of Common Sense
Showing posts with label scrum. Show all posts
Showing posts with label scrum. Show all posts
Tuesday, October 30, 2012
Wednesday, March 14, 2012
About Trust and Agile as Behaviors
Something that amazes me is how easy we forget basic postulates. In this case, our believes determine our behaviors. Thus the connection between trust in the new ideas and our behavior towards implementing them.
If you want to read an interesting post on the connection between trust an becoming agile, head straight on to LeadingAgile and read Agile at the speed of Trust - an Overview (Written by Peter Callies).
Thursday, September 30, 2010
A Scrum Certification Summer End
It has been an interesting summer. More interestingly, I am now a certified Scrum Master and Scrum Product Owner.
It feels good to know that an effort has been crowned properly.
Saturday, May 15, 2010
Inertia and its anti-Scrum effect
Working routinely in a changing environment leads to waste, both in the professional and the personal life.
The same happens when at work we do not actively choose what and when to do. This is one of the reasons why we should not skip the retrospectives at the end of each iteration, either sprint or change between workdays and weekdays schedule.
Do you have some special mantras that help you keep on track?
Monday, November 2, 2009
Scrum @ BPM
This morning, while waiting for the Office 2007 update, I was reading an article on the future of BPM - BPM in Ten Years? My Best Shot.
The combination of Scrum being implemented at work and BPM as my future professional target resulted in the idea that BPM's next incarnation will be a mixture of Scrum principles and BPM methodology.
To put it in a few more words, using Scrum, the team members are given freedom to choose their own paths to the target presented by the product owner. They act as rational personas and the result is a much more motivated and capable team.
On the other hand, currently there is little flexibility in the implementation of the BPM modelled processes. Very often the improvements are done like little "waterfall" development stages. There is little flexibility and continuation of the improvements.
This is exactly where the Scrum principles can help. They can empower the team members to provide feedback, influence the workflow and continuously improve, improve, improve... But then comes the question of the most proper management style to allow this to happen.
The combination of Scrum being implemented at work and BPM as my future professional target resulted in the idea that BPM's next incarnation will be a mixture of Scrum principles and BPM methodology.
To put it in a few more words, using Scrum, the team members are given freedom to choose their own paths to the target presented by the product owner. They act as rational personas and the result is a much more motivated and capable team.
On the other hand, currently there is little flexibility in the implementation of the BPM modelled processes. Very often the improvements are done like little "waterfall" development stages. There is little flexibility and continuation of the improvements.
This is exactly where the Scrum principles can help. They can empower the team members to provide feedback, influence the workflow and continuously improve, improve, improve... But then comes the question of the most proper management style to allow this to happen.
Sunday, August 23, 2009
Scrum @ home
A few months ago, the department I work in started implementing the Scrum methodology. Then came Lean. We still try to fight our way through the terminology and ideas. However, thanks to our great Scrum mentor, Monika Kovachka-Dimitrova, I am pretty sure that we have a great chance become winners.
In the meanwhile, I've decided to start applying some of the Scrum principles in my personal life. Probably it is due to the smaller scale, but the positive results started flowing right after the first weekend sprint. Even when I involved my family in the planning, the results made me jump for joy.
The morale of the story is the following:
Maybe, after reading Ken Schwaber scrum books, you are still not completely persuaded that scrum works in a strenuous environment. If that is the case, I recommend to give it a try and experiment with your own tasks. I am sure the results will surprise you ;- )))
In the meanwhile, I've decided to start applying some of the Scrum principles in my personal life. Probably it is due to the smaller scale, but the positive results started flowing right after the first weekend sprint. Even when I involved my family in the planning, the results made me jump for joy.
The morale of the story is the following:
Maybe, after reading Ken Schwaber scrum books, you are still not completely persuaded that scrum works in a strenuous environment. If that is the case, I recommend to give it a try and experiment with your own tasks. I am sure the results will surprise you ;- )))
Subscribe to:
Posts (Atom)