Agile Project Management: QuickStart Guide - The Simplified Beginners Guide To Agile Project Management (Agile Project Management, Agile Software Development, Agile Development, Scrum) by ClydeBank Business

Author:ClydeBank Business
Language: eng
Format: azw3
Publisher: ClydeBank Media LLC
Published: 2014-09-08T04:00:00+00:00

A Culture of Continuous Feedback

To nurture successful and perpetually fruitful Adapt phases, an Agile project manager must know how to elicit useful feedback. Successful project managers will ask pertinent questions and facilitate meaningful dialogs between team members. The acquisition of useful feedback should be continuous and should not be relegated only to the Adapt phases. Building a culture of continuous feedback is actually easier than you might think. Much of the Agile structure inadvertently limits room for continuous feedback. Daily stand-up meetings are designed to be quick and to the point, unencumbered by protracted theoretical discussions or general complaints. Sprints are designed to be fast-paced and focused, not contemplative. Therefore, if you provide an ongoing forum for your team members to provide general feedback, then they’ll likely take advantage of it. A physical feedback box can work well in this respect. You may also be able to leverage your online collaboration tools (see Chapter 4) to solicit feedback. Employees may candidly record and deposit their thoughts on various matters without having to offer immediate solutions. Complaints and suggestions are reviewed during the Adapt phase, and are hopefully paired with viable remedies. Using a feedback box or a similar setup allows your Agile team to concurrently generate continuous feedback while also capitalizing on the rigorous focus inherent in the Agile Project Management method. The content of the feedback box will also inspire new and innovative ideas from the team. In many cases, it won’t be feasible to immediately implement all of the ideas generated. The team will have to prioritize the importance of the ideas in the Adapt phase and decide which ones to incorporate into the next sprint, which ones to add to the product backlog, and which ones to disregard. The Scrum team as a whole should be involved in the prioritization process, either through voting or by some other means.

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.