Provide vision for, and coaching toward achievement of below stated enterprise goals ( among others ):
– Input/output needs of parties involved in communication and other interaction/handoff points are well understood, and thus are always adequately met for said parties.
– Planning ( including daily ), goal/task follow-through and prioritization, customer validation and direct/gatekeepered channels for creating a shared team/customer understanding of the problem and proposed solution the software is addressing are all adequately enabled and well managed by the whole team. Continuous learning is employed in order to achieve continued evolution on all aspects of team-working.
– Functionality that the software implements is fully self-testing, fully self-documenting and perfectly annotated, and thus ultimatelly fully malleable as part of each delivery ( the software remains soft ).
– Motivation is actively managed and provided by the servant leaders of the team through enabling autonomy, mastery and full responsibility and empowerment for defining, and following through on, our worthy cause(tm). People are leaving at 5 every day to enable sustainable pace.
Recently I had the opportunity to consider what questions I need the sprint planning meeting to answer, and I will share it here so I can refer to it later, and in case it would be useful to you.
1. In what way can we adjust the current software so that our users would start using it after the sprint? ( adjust last part if your software is already in use )
2. What seems like the best way we can come up with right now for actually completing the suggested adjustment to the software by the end of the current sprint?
3. Who could we get to actually start use our adjustments to the software at the end of the sprint? ( all users of the software? Beta users? Alpha users? )
Seems it is valuable to keep those questions in mind for the sprint planning meeting. What questions do you try to answer during your sprint planning meeting?
Another inspiring and fun meeting and conversation with Jeff tonight under the excuse of The Winnipeg Scrum Experience, Scrum Learning Series pt. 2 – The Backlog.
Caught up on the end of his internship, and what he has been up to with Rails, then chatted about people we’ve looked up to over the years, and then watched the second video of the ScrumTrainingSeries.com – The Product Refinement Meeting. I would mention that it was another opportunity for me to try to listen more than I talk in a conversation, but I am still far from being good at it! 🙂
We left excited about intention of picking an app/product to build, then creating a backlog for it. I came home to a cool suggestion from Jeff for the suggested app.
The first presentation about Scrum, as part of The Winnipeg Scrum Experience project is tonight!
Only one person RSVP-ed ‘Yes’. Perhaps I should apologize to those who would really like to come out but can not because they are going to the Secret Handshake + NMM Christmas Party, if there is anyone like that 🙂 I chose the date before the Christmas Party date was announced, and I just stuck with it, so sorry about that!
I look forward to hanging out with Jeff again, and practising the Intro to Scrum presentation!