We implemented this on one team late in my career. For example, here's a page covering the information for Kanbanize (this is in no way a recommendation, btw):
But as I said most agile management software seems to be providing it now.
And after 30 years of writing code and 10+ years as a PM and SM, I have a lot of experience to draw on to help the team.Īnd I make sure we have fun. There is a lot I could write here - for example I taught public speaking and conflict resolution at night for ten years so I am always using those skills - but here is what I do with any team I am serving as a leader I listen to understand their strengths and weaknesses and then I work like hell to leverage their strengths and compensate for their weaknesses. For example, since I have been a Release Manager, I think about and prepare the team for what we will need to do going into a major release (this is the post office so do not even think we can release every sprint). I find IT so reactive that team members do not think enough about what is ahead. What keeps me busiest is staying ahead of the team, clearing impediments even before they see them. And when I don't have a trick, I do research by talking to other Scrum Masters, reading and listening to podcasts. Nice list - after 38 years of software development, I use every trick in my book to help the team deliver while creating a safe place to work. Yeah, and along the way I might have facilitated a few planning meetings. Fought with HR over policies that didn't exactly embody trust.Purchased enough doughnuts to sink an aircraft carrier.Organized release parties, or other celebrations.Worked with HR and managers when the team elected to vote someone off the island.Coached the testers to get out front on stories.Demonstrated a skills matrix for the team.Hosted countless Lunch and Learns on various topics useful to the company.Demonstrated continuous integration techniques.
I should really save this post somewhere and reload it every time this question gets asked.