Related Content
How to Run a Productive and Effective Remote Team With remote work becoming the norm, now is a good time to consider how you can help your team do their best without causing burnout. Fortunately, remote work may actually improve productivity. After all, it's one of the factors that largely contribute to job satisfaction. |
||
Schedule Risk Analysis Building schedules for complex projects is challenging. While the results are never perfect, credible schedules are a useful communication and coordination device. Incredible schedules are a dangerous waste of time and energy that damage a project manager’s credibility and cost an enterprise a fortune. |
||
Evaluating Team Health in Agile and DevOps The importance of the human element in delivering great software is sometimes overlooked, as is the relationship between team health and team performance. Just like physical health checks, team checkups are important. Let's look at some factors that can affect team health and how you can evaluate the important metrics. |
||
3 Ways Leaders Can Change a Blame Culture If your organization has a blame culture, team members get discouraged and mistrust leaders. It focuses on pointing fingers, not coming up with solutions to move forward. To increase trust, inspire creativity, and nurture a generative culture with your team, here are three things leaders can do instead of placing blame. |
||
Making a Game out of Building an Amazing Team Games are a cost-effective and efficient way to evaluate, assess, and thus hire people with the right expertise and aptitude. It is an equally practical and powerful way to continue to develop and improve the team and individual team members. Try using games to improve your efforts to build and maintain an outstanding team. |
||
Why Setting Priorities Is a Core Agile Practice Every aspect of agile includes prioritization. The most important user stories are implemented first. Testing is prioritized to make sure features valued by customers are tested the most. Even everyday tasks are prioritized during daily standups. Here are three reasons setting priorities is essential to success in agile. |
||
Prioritizing Invisible Work There are work items that will give the team an operational boost and perhaps avoid a crisis, but that never make it to the top of the priority list—like build and deployment improvements, or paying down technical debt. For enabling work that is valuable but too invisible to be a priority, consider breaking it down. |
||
Software Features to Avoid in a Production Environment When developing an application, it’s best practice not to use certain software features in a production environment. These include features related to programming language, the OS, the database, a framework, a web or application server, or a tool. You have to consider the production setup to avoid bugs or server crashes. |