In this episode of SoundNotes, Dave Prior and Derek Huether respond to a couple questions from students who have taken a LeadingAgile CSM and/or CSPO class over the past couple months. Here are the questions they will address in this short video podcast:
My team seems to have a problem with estimating and understanding the estimating concepts. The team members are accustomed to traditional waterfall projects and estimating everything in units of time. How can I help them understand estimating, but continue to complete the sprints with no PBIs (Product Backlog Items) rolling over to the next sprint?
I have a team lead who is skeptical of scrum, especially metrics related to the process. He doesn’t think carryover matters from sprint to sprint as long as we’re “creating value” and getting the program priorities completed. Any advice on how to convince him that metrics can be a tool for good, and that the sanctity of the sprint commitment matters?
Today I saw a link on Twitter that intrigued me. It was a video of WikiSpeed's Joe Justice at TEDxRainier. Sure, the video is 10 minutes long. But, I guarantee it will leave you inspired. I get challenged all the time by people saying Agile is only good for Software Development. Well, watch this video and see if you don't agree that the horizon has expanded. If you don't want to click the link above, I'm adding an embedded video below.
This post concludes my 3 part series about when PMI Introduced the Elephant in the Room. It's the basis of my talk at AgileDC on October 26. The elephant I am referring to is the mainstream adoption of Agile. In part one of my series, I introduced the idea that Agile was about to cross the chasm. The chasm I'm referring to is based on the "Technology Life Cycle Adoption Curve" concept from Geoffrey Moore's 1992 book Crossing the Chasm. I see parallels between a technology life cycle adoption curve and a methodology life cycle adoption curve. Though waterfall may be at the far right, with the laggards and skeptics, I see Agile as being embraced by the innovators and visionaries for the last 10 years. But within the last view years, the earliest adopters and visionaries started to get traction. It took real leadership to follow a few "lone nuts" and brave ridicule.
There comes a time within the adoption curve that the tipping point occurs. If the original Agile leaders were the flint, the first followers were the spark that made the fire. With PMI creating the PMI-ACP certification, there is going to be a lot of fuel on the fire. After teaching my first PMI-ACP class over the last few days, I asked my students why they were pursuing this certification. What made it different? Their answers were both enlightening and similar. The common answer was that their organizations see the PMI endorsement of Agile methods as the legitimizing of Agile. Until PMI got involved, Agile practices were "undisciplined ideas from those on the fringe". Even with the certification being in the pilot stage, it has rapidly become a viable alternative to other processes that just aren't working. Though Agile isn't for everyone, I find it amazing that so many have not adopted it, merely because it wasn't supported by the status quo.
I'm actually not sure where we are on the adoption curve. But, from listening to my students, the fear of ridicule is being stripped away. I do believe we are crossing the chasm.
Watch this 3 minute video. If you are a version of the shirtless (Agile) dancing guy at your organization, all alone, remember the importance of nurturing your first few followers as equals, making everything clearly about the movement, not you.
It's all in how you say it. Or, in the case of this video, how you write it. In less than 2 minutes, this video will send a powerful message. It's about writing from perspective.
After watching it, I immediately thought of how a user story can communicate a message differently, compared to a standard "shall statement" requirement.
Here are as few formats for you to compare. Which would you use?
As a <role>, I want <goal>
As a <role>, I want <goal> so <reason>
Given <dependency/constraint>, as a <role>, I want <goal> so <reason>
Do you have a preferred user story format that you use? Please include it as a comment and have a beautiful day.
You should be looking for ways to motivate your team every single day. You could bring them donuts or bagels. You could give out monthly awards or public recognition. You could also give them a pep talk. All it takes is one minute of encouragement to change their day for the better. So, here is your pep talk for today. Take 55 seconds, watch the video, and I challenge you not to have an awesome day. This kids could be the next Tony Robbins!