Related Content
3 Problem-Solving Techniques for Project Managers Managing software development projects involves a lot of moving parts. You might come across bottlenecks and challenges to goals and objectives, and you need resolute methods for expediently addressing such issues. Here are three proven tools and techniques for managing time, planning resources, and solving problems. |
||
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 Visible Project 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 Management One 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 Way The 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 Requirements When 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. |
||
Top 10 TechWell Insights Stories of 2019 Career development was on many software practitioners' minds in 2019, as some of our top stories were about having a technical lead on a Scrum team and making the switch from quality assurance to quality engineering. Stories about new ideas such as DevOps and continuous testing also ranked high. Check out the roundup. |
||
Stop Fanning the Flames of Constant Firefighting Continually 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. |