Related Content
 |
6 Signs Your Agile Project Isn’t Really Agile There's a trend of organizations declaring they are agile without actually changing how they develop software. Declaring that an apple is an orange doesn’t make it so. These six key indicators can help you determine whether your agile project isn’t really agile after all—and give you some solutions to help. |
|
 |
The Premortem: Planning for Failure While a postmortem, or retrospective, is done after a project is completed, a premortem is done before the project starts as a way to imagine that the project failed and to explore what went wrong. You list every possible thing that can go wrong, then devise solutions to the most probable risks—before you need them. |
|
 |
4 Ways to Increase Software Quality and Decrease Test Time Software testers are continually under pressure to test faster without sacrificing quality. By taking the perspective that quality is the responsibility of the entire team, not just the testers, shorter test cycles with higher quality software are possible. Here are four ways the whole team can improve releases. |
|
 |
Can Your Project Succeed without Your Sponsor On Board? Project managers are tasked by sponsoring executives to complete projects successfully and provide timely communication if barriers arise. But what should a project manager do if the sponsors are the biggest barrier? If you can’t get the answers you need, is it a good idea to make your best guess and proceed? |
|
 |
3 Steps to Transformational Leadership for Business Agility Building your agile organization only starts with developing software in an agile way. The next step is transforming your business with a customer-focused embrace of agile across the entire enterprise. Managers who want a truly agile organization must lead with focus, steer from the edges, and change the system. |
|
 |
How to Prioritize Tasks and Do Only the Work That Matters When you’re working on multiple projects at a time and everyone is breathing down your neck for results, it’s difficult to separate wants from needs. You have to be smart about task prioritization. Here are four ways to break through the noise and make sure you’re focusing on the work that really matters. |
|
 |
A Tester’s Role in Requirements Exploration Agile is supposed to get people to talk to each other in real time. However, many teams still lack a shared understanding of what they are going to build, even as they start coding. As testers, we can explore feature specifications early, contributing to successful and timely delivery through defined requirements. |
|
 |
Wisdom from Consulting: Getting and Vetting Advice When you hire a consultant, they may appear to have a wealth of experience and knowledge—and may actually have it. But accepting their advice without question is dangerous. Here are some good practices to keep in mind when you're receiving advice, including asking questions, exploring alternatives, and analyzing risks. |
