Is the Problem with Your Agile Tool, or How You’re Using It?While using index cards and a wall can function just fine as a kanban or Scrum board, issue-tracking tools such as Jira can make it easier to manage a backlog, especially with a distributed team. But these tools are more complex to use and can add their own overhead to the process. You need to keep things simple.
Making (and Keeping) Project Risk VisibleProject managers recommend how much should be invested to address various risks based on their understanding of project context, but the final decision about what to do and when those efforts are sufficient belongs to the sponsor. Risk management requires executive input, so sponsors need to see all risk data you have.
Planning Strategies for Successful Project ManagementOne of the central responsibilities of a project manager is to establish the most suitable strategy for project delivery. That means creating a plan for success and predicting potential issues that could affect the project. These strategies can help assess the amount of time and effort for each facet of the project.
Plan for the Year the Agile WayThe start of a new year always comes with new resolutions, goals, and a set of plans to grow in the future. The excitement and energy that a new start brings can rejuvenate a team. However, if you’re not careful, that same ambition can lead to failure. This year, adjust your strategy and plan in a more agile manner.
The Curse of Rushed RequirementsWhen development is outsourced, a documented baseline of expected functionality sets expectations for both the client and developer. Acknowledging that agile practices are flexible, beware the trap of rushing requirements just because you know they are going to change. It's still essential to be as accurate as you can.
Stop Fanning the Flames of Constant FirefightingContinually having to address unexpected problems interrupts your original sprint activities, causing stress on the team members and fanning the flames for future firefights. But with due diligence, you can lessen the need to constantly put out fires. Here are some steps that can break the cycle of work and rework.
Beware of Success StoriesThe tendency to look back and think you know what contributed to a success is called survivorship bias. It occurs when you make a decision or take some action based on past successes while ignoring past failures. That's why it's important to approach reports of successful projects with a healthy dose of skepticism.
Are You Forgetting a Stakeholder?Technology allows amazing innovations to optimize business and deliver new and better services, but if you don’t carefully consider your entire user community, innovations may cost you business. When designing for stakeholders, don't stop at the obvious cases—or else you may find that you forgot an important customer.
