project management

[article]

Slim Down Your Test Plan Documentation

Summary:
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.

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.

About the author

Achieving Continuous Improvement and Innovation in Software

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

Better Software Magazine
[article]

Streamline Your Agile Requirements by Avoiding Bloated Backlogs

Summary:
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.

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.

About the author

10 Things You Must Do to Become Truly Agile

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.

Better Software Magazine

References

  1. 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.
  2. Rutgers School of Arts and Sciences. “Thomas A. Edison Papers.” The Edisonian, Volume 9, Fall 2012. http://edison.rutgers.edu/newsletter9.html.
  3. 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.
[article]

Build One before Building Many: Learning from Agile Feedback

Summary:
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.

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.

About the author

Visual Management Gone Wild

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...

[article]

Estimating Cost of Delay in Agile Projects with Time-Value Profiles

Summary:
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.

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.

About the author

[interview]

The United State of Women Summit: An Interview with Tania Katan

Summary:
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.

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.

About the author

Pages

StickyMinds is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.