Related Content
How to Manage Project Delays We often attribute project delays to internal reasons, such as poor management, lack of collaboration, resource issues, and software quality, but there are often reasons that fall outside of the norm. Rajini Padmanaban provides some examples of these types of project delays and how to manage them. |
||
The Word “Automation” Has Led Us Astray The misunderstanding that automation for software quality is just doing what humans do (i.e., manual testing), but faster and more often, causes business risk. Unless you’re very clear, the quality measure is incomplete. The word automation distracts from the real value: measuring quality. |
||
Testing Nonfunctional Requirements in an Agile Lifecycle As organizations embrace agile, requirements become a challenge because they must be considered and validated in each (short) sprint. Ideally, nonfunctional requirements should be a continuous focus throughout the project. Here are some ways to better address NFRs in an agile development lifecycle. |
||
Five Techniques for Creating Testable Requirements Documenting user requirements is always a challenging phase in software development, as there are no standard processes or notations. However, communication and facilitation skills can make this activity easier. Here are five techniques for converting user stories into testable requirements. |
||
Become an Estimation Leader Single-point estimates, whether they are for a budget or a schedule, are never correct. Things happen. Demanding that your team provide you an exact number and then treating that as a guarantee is not being a good manager—or being agile. What if you could provide a different estimation leadership? |
||
Book Review: More Fearless Change It is not always easy to encourage people or organizations to adopt new ideas. More Fearless Change: Strategies for Making Your Ideas Happen can give you the tools to help you spread new ideas. This book has actionable advice you can apply as a change agent, regardless of your role or organization. |
||
Performing Accessibility Testing on a Live Site: A Case Study Because accessibility is just starting to really gain awareness in the product development world, organizations are often not fully informed on what it takes to build accessible software—they just want to get there. Here’s a case study from a project that involved making a live product accessible. |
||
Figuring Out What to Measure: Metrics for Agile Teams For agile to work, it's important to evaluate how your team and your project are doing. Qualitative feedback, such as from reviews and retrospectives, can be valuable. But at some point you may need more quantitative information to improve your project. How do you decide what metrics to gather? |