|
Five Tips for Retrospective Leaders and Meeting Moderators Before you schedule or moderate another retrospective meeting, read this column by Esther Derby. Esther offers five tips that will help improve the productiveness of retrospective meetings. You'll also learn how letting the meeting participants run the conversation will solicit more feedback and ownership than traditional moderation methods.
|
|
|
Simple Summaries Of Complex Projects How can we meaningfully summarize—in a brief status report without losing important details—the successes and setbacks our projects experience?
|
|
|
Keep Non-developers in the Loop Keeping QA members up to date on changes as they happen–through meetings, wikis, and email–can reduce the number of unnecessary bug reports and save you time and frustration.
|
|
|
Tale of a Yo-Yo Manager There is much more to empowering your team than simply stating "You're empowered." Consider the three Ws of empowerment: "what," "when," and "why" when creating boundaries that define which decisions are the team's and which need management approval.
|
|
|
Reducing Friction Tasks and processes often have hidden costs ("friction") that escape our notice. Learning to recognize and reduce needless friction can make a big difference on project cost and schedule, as well as team morale.
|
|
|
Making Retrospective Changes Stick Retrospectives become a waste of time if the changes and improvements agreed upon in the meeting are never accomplished. Esther Derby believes in the power of retrospectives. And she knows firsthand that it's easy to talk about a change, but not always easy to actually do something differently. Esther shares experiences that illustrate this point and offers advice on how to make changes stick.
|
|
|
How I Stopped Worrying and Learned to Love Prioritization Managing an agile project based on uncensored "Very High," "High," and "Low Priority" user stories or backlog items used to induce stress on Jeff Patton. So he learned to implement a combination of prioritization techniques to get these lists--and the job--under control. In this week's column, find out how Jeff utilizes MoSCoW and business goals to make sense of prioritization.
|
|
|
Keys to Top-Notch Estimates If the construction industry estimated projects as poorly as the IT industry does, we would still be living in mud huts. Yet inaccurate project estimates have become the norm in the software industry. Find out how you can turn your estimates into reasonable predictions of project performance.
|
|
|
Product and Project Software Configuration Management (SCM) In this article, the authors discuss how software configuration fits into products and projects, beyond managing and controlling source code and other developer assets. They look at the differences between internal and external products and where project fit into the equation.
|
|
|
Receptiveness to Change Everyone responds to change differently, whether managers know this or not. A good leader knows this, and doesn't hurt the morale of a team by expecting them to act a way that their incapable of, or that feels unnatural to them. Naomi Karten brings this all to light in this article.
|
|