tag:blogger.com,1999:blog-31808663.post6366263231477507942..comments2023-04-16T23:58:29.247+12:00Comments on On Agile Leadership: Introducing new toolsManfred Langehttp://www.blogger.com/profile/01100831606055102208noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-31808663.post-72671732297148794802009-03-04T04:13:00.000+13:002009-03-04T04:13:00.000+13:00This seems like a common problem, and I think your...This seems like a common problem, and I think your solution points to its root. Given the frantic pace of many projects, it has been my experience that each team member will often just 'do' what they think is best, perhaps without consulting the rest of the team. Sometimes, this works well. Other times, you run into the problems you have described, especially if that new tool is likely to have an impact on how the rest of the team will work.<BR/><BR/>When encountering a problem, perhaps during a retrospective, I believe it is more effective to communicate how a new tool would alleviate some of the team's pain and get buy-in before introducing the tool. If there is skepticism, it can be addressed. If someone else comes up with an even better suggestion that the team gets behind, great. Either way, you will save time and waste by aligning the team before you roll-out something new.Jeremy Kriegelhttps://www.blogger.com/profile/03493294017711607695noreply@blogger.com