Related Content
The Difference between Plans and Planning As former president Dwight Eisenhower said, "In preparing for battle I have always found that plans are useless, but planning is indispensable." The fact that plans may have to change does not mean planning is a waste of time. In projects, it's always valuable to consider budgeting, resources, and timelines. |
||
Shorten Your Feedback Loops to Build Better Software, Faster When we have short feedback loops, we are still in the moment for that feature. We still have the context. The longer the feedback loop, the less likely we are to still have all the context for the feature because we are on to the next piece of work. How long are your feedback loops? Can you shorten them? |
||
Why Process Standardization Is a Terrible Idea Having a standard process everyone uses makes sense in theory. You could compare metrics and progress across teams and projects. But it practice, it becomes like comparing apples and oranges. Teams aren't all the same, and neither are projects. Each team need its own optimized way to deliver value. |
||
The Art of People Facilitation: Servant Leadership and Team Dynamics Some senior level staff in various organizations struggle to embrace certain modern concepts of leadership and facilitation. Emotional intelligence, observation, and skilled listening all play into modern servant leadership. It is a new art among agile managers, but it's an art we can all learn. |
||
Should You Cancel Your Next Meeting? Of course meetings are often necessary, but sometimes they are just rituals without meaning. At your job, would anyone recognize if a meeting weren't efficient or essential? When was the last time a meeting you were scheduled to attend was canceled because it wasn’t a good use of anyone’s time? |
||
Expanded Schedules Pose Project Management Risks, Too We're all aware of the risks from projects that have overly aggressive schedules. But projects with leisurely schedules have risks, too. Extending a timeframe is supposed to give you more time to create quality products, but it can also lead to procrastination, changing teams and expectations, and more. |
||
Scaling Agile: Reasonable Practices for Program Management In a big push to scale agile, it can help to think of scaling agile as program management, or coordinating projects where the value is in the overall deliverable. Consider how you can deliver your product one small, finished bit at a time. If you deliver value as often as possible, you see real results. |
||
The Best Way to Communicate Project Quality Concerns When you encounter quality concerns in a project, it's important to let management know. But building an overly detailed list of faults and shortcomings undermines the impact of the important points and muddles communication. To effectively convey the crucial issues, you have to prioritize. |