Test plans are essential for communicating intent and requirements for testing efforts, but excessive documentation creates confusion—or just goes unread. Try the 5W2H method. The name comes from the seven questions you ask: why, what, where, when, who, how, and how much. That's all you need to provide valuable feedback and develop a sufficient plan of action.
We’ve all worked with a talented developer who can be a frustrating challenge to manage. First-time managers may unknowingly encourage bad behavior. There are several innovative ways to resolve the situation.
There is tremendous pressure on software development teams to deliver software faster, better, and cheaper. Quality engineering with a focus on innovation is the answer
- Sowers, Mike. “Software Testing: A Social Responsibility.” TechWell Insights. September 3, 2015. https://www.techwell.com/techwell-insights/2015/09/software-testing-social-responsibility.
- Fowler, Martin. “Self-Testing Code.” MartinFowler.com (blog). May 1, 2014. https://martinfowler.com/bliki/SelfTestingCode.html.
In agile development, a bloated backlog results from teams accumulating huge lists of requirements, usually in the form of user stories. Retaining every possible story for building the product weighs down the backlog while squeezing (or obscuring) the highest-value stories. The best way to help minimize this risk is to optimize the time spent defining and refining the product priorities.
Agile is not a state of doing; it’s a state of being. Adopting business models on value and learning how to make teams autonomous are both necessary steps to reap the benefit of agility.
- Hamel, Gary. “The Why, What, and How of Management Innovation.” Harvard Business Review . February 2006. . https://hbr.org/2006/02/the-why-what-and-how-of-management-innovation.
- Rutgers School of Arts and Sciences. “Thomas A. Edison Papers.” The Edisonian, Volume 9, Fall 2012. http://edison.rutgers.edu/newsletter9.html.
- Critchfield, Sara. “How to Push Your Team to Take Risks and Experiment.” Harvard Business Review . March 9, 2017. https://hbr.org/2017/03/how-to-push-your-team-to-take-risks-and-experiment.
When you're working on a project and are presented with a big story or requirement, resist the urge to treat it as a single piece of work. One of the principles of the Agile Manifesto is to deliver working software frequently. This allows you to learn from what you built and make adjustments. See if you can break down the request and find a small piece of work within the big.
A visual management system is a low-tech tool with a simple mission—to visually represent the work that the team is doing. When used regularly and correctly, it can be a project acceleration tool. However, teams often go wild with visuals, decorating every inch of free wall space with...
When we think of planning, we often think about requirements planning. We get the initial features and functions down, and then see where agile takes us. Lisa Calkins claims that less than a third of software development projects are successful. Regarding this lack of success, process...
The cost of delay for releasing a product can be due to many factors, but that value loss can seem like an abstract concept. Attaching hard numbers to a release timeline in the form of a time-value profile helps the development team and business stakeholders have a conversation about how long they have to build a product and when it would be best to enter a market.
In this interview, Axosoft evangelist Tania Katan, who is also the creative instigator of the international viral campaign #itwasneveradress, reports on being invited to the White House’s United State of Women Summit. She talks about agile project management, activism, and Michelle Obama and Oprah.