Scrum Master Services

Scrum is simple but not easy. It is very easy to deviate from the practices that make Scrum a powerful and productive software delivery process.

I am a Certified Scrum Master (CSM) and have the experience necessary to understand why it is important to stay on track and understand the consequences of not doing so.

Using the diagram below, I want to take a minute and explore some of these points so you can get an idea of the type of Scrum Master I will be if you hire me at your firm.


Point 1 – People will have many new ideas. It is up to the Product Owner to manage the requests that come in and ensure that only appropriate stories get added to the backlog. She needs to get comfortable with the word no, and reject stories that do not make sense. For this to be successful, she must have a passion for the product and understand the marketplace.  

Point 2 – The Product Owner owns the backlog. She ensures that stories are sized properly and keeps the backlog prioritized. If there is a Business Analyst on the team, she works closely with him to ensure the stories have a proper level of detail and Acceptance Criterion. The Product Owner schedules Grooming Meetings when necessary to ensure the backlog is maintained and estimated.

Point 3 – The Scrum Master guides the team in the activity of Sprint Planning. He ensures that the stories added to a sprint have enough detail and the team has what they need to commit to the stories in the sprint.

As the sprint unfolds he keeps a watchful eye on things and acts as a flashlight, shining light on things he feels need attention. 

A well understood Definition of Done is critical. When a story is Done, it is ready for deployment at the end of the sprint if the Product Owner decides it is appropriate. If it is not Done, it returns to the backlog and is completed in a future sprint. The team only gets credit for stories that are Done. There is no partial credit for stories not Done.

Point 4 – The team must be cross functional and willing to work on anything they have the skills to do. One of the most powerful benefits in Scrum is the whole team works to get the stories in a sprint to a Done state. 

For example, toward the end of a sprint, development is mostly complete. Developers are now available to help test the stories in the current sprint.

Point 5 – As the team gets stories Done and into production confidence in the team grows and quality increases. This builds upon itself. The team feels good about themselves and the firm is happy with the work the team produces.

Part 6 – It needs to be easy to deploy into production. Dev Ops practices help in the regard. We also need to continuously improve. Scrum uses Retrospectives for this purpose.

I understand the tenants of Scrum and why they are important. I also understand the consequences of deviating from them. I use Standups, Retrospectives and daily interaction with team members to point out when agile and scrum principles are not being followed.

I also align with senior management on the degree the firm wishes to adhere to scrum principles. When necessary, I ask senior management to step in and re-direct team members who need it.

Scrum is more than packaging work into buckets of time and calling them sprints. If you do not consistently have user stories that can be deployed to production at the end of a sprint. your scrum process can be improved.

Contact Me today to discuss your Scrum Master needs. 

Learn More