I’ve invited a fellow Agilist in as a guest blogger, something I think I’m going to be doing more of. Raymond is a newly minted CSM, and he’s a voracious reader of Agile books. He’s off on the right foot–using his CSM as the foundation for Agile and always looking for ways to expand his knowledge. Writing about Agile is one of the best things a scrum master can do to develop at an individual level, and when I asked Raymond if he was interested, true-to-form, he snatched up the chance to write his first blog about the topic:
As a “waterfall” project manager of 8 years, I can honestly say I was pretty stoked when introduced to the Scrum Agile framework. The major aspects of Scrum that excited me were the continuous flow and providing increments of working software. This was great news because as a project manager, I can honestly say that it was extremely rare to see the fruits of the team’s labor. What I was used to (and most project managers will agree) is the following:
- Get a project with inadequate detail around the scope
- Spend tons of time on documentation
- Assemble a team
- Large amounts meetings to go back and forth about requirements
- Get to a point where we can have something produced (that will be tangible)
- Finally, go to production with a half baked product or service, and move on to the next project
|“everything taught was in the “perfect world” scenario.”|
adopted the framework, there is a huge intangible piece that needs to be in place and that’s BUY-IN. With Scrum framework not being as widely adopted as Waterfall, one of the most difficult aspects that you run into is trying to get buy-in from upper management and team members. The major thing to consider is people usually do not respond well to change and Scrum will change EVERYTHING in regards to how to go about completing a project. To get the most benefit you must first convince people that this practice works, and you have to actually do it. So before you get to implement all this knowledge that you gained in you Certified Scrum Training class, you have to convince the powers that be that it’s worth doing –> Imagine how fun that’s going to be!
Sooooooooooooooooo, I said all of that to say, while Scrum is the best thing since sliced bread when it comes to providing tangibility in projects, what they don’t elaborate on is how difficult it is to evangelize and get buy-in. Something you definitely need to think about if you’re going to be implementing Scrum into your world, is how you’ll convey it so that people will be on-board and willing to give it a shot! The one thing I can suggest is to convince everyone to try it. If you can get a scrum team and a project, take requirements and break it down into user stories, hold ceremonies and use artifacts, I am certain that this will have a positive outcome with peers (and upper management). Another suggestion is to read Mike Cohn’s Succeeding With Agile: Software Development Using Scrum. This book gives great suggestions on implementing scrum into a new environment.
3 thoughts on “Guest Post: Raymond, A New Scrum Master”
Excellent post by an excellent scrum master. Well done, Raymond!
Great post.Thanks for sharing this post.I have article regarding Agile and Scrum.Are you currently accepting guest blog?
Thanks for showing interest, but I usually only invite guests to blog if I have been working with them.
Comments are closed.