process improvement

[article]

Endgame Testing: Exploring Your Agile Product End to End

Summary:
The main goal of endgame testing is to test the system end to end from the user's perspective. This should ensure continuity between components developed by different teams, continuity in user experience, and successful integration of new features. Endgame testing will often identify gaps that are difficult to discover inside agile teams, including flows across the product.

The main goal of endgame testing is to test the system end to end from the user's perspective. This should ensure continuity between components developed by different teams, continuity in user experience, and successful integration of new features. Endgame testing will often identify gaps that are difficult to discover inside agile teams, including flows across the product.

About the author

[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

[article]

Fixing a Broken Deployment Process

Summary:
When you have hundreds of applications performing various functions across several environments, it's tough to push all the code when it needs to be. Here are some steps to help your own team develop the internal tooling it requires to deploy thousands of applications if needed, all in a reliable, efficient manner.

When you have hundreds of applications performing various functions across several environments, it's tough to push all the code when it needs to be. Here are some steps to help your own team develop the internal tooling it requires to deploy thousands of applications if needed, all in a reliable, efficient manner.

About the author

[article]

How Businesses Stay Agile: The Art of Being Retrospective

Summary:
The greatest use for agile in business is in changing how you tackle problems and projects. Rather than defining the whole project and setting a “way forward,” an agile approach takes things much more iteratively. That means meeting as a team on a frequent and regular basis to share problems and successes, then making improvements as needed—being retrospective.

The greatest use for agile in business is in changing how you tackle problems and projects. Rather than defining the whole project and setting a “way forward,” an agile approach takes things much more iteratively. That means meeting as a team on a frequent and regular basis to share problems and successes, then making improvements as needed—being retrospective.

About the author

[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

[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

[article]

7 Lessons Agile Can Teach Us about Leadership

Summary:
The Agile Manifesto contains values to guide teams toward developing better software. But its directives are also about leadership—influencing culture and creating an organization where people can collaborate to meet the needs of their customers. Here are seven lessons the Agile Manifesto can teach us about leadership.

The Agile Manifesto contains values to guide teams toward developing better software. But its directives are also about leadership—influencing culture and creating an organization where people can collaborate to meet the needs of their customers. Here are seven lessons the Agile Manifesto can teach us about leadership.

About the author

[article]

The Transparency Experiment: Improving Accuracy and Predictability in Scrum

Summary:
Using the iterative and incremental agile development framework Scrum should help manage product development, but some teams still have difficulty delivering features in a predictable manner. This organization decided to address the mismatch between what was being committed and what was accomplished by doing an experiment in work transparency.

Using the iterative and incremental agile development framework Scrum should help manage product development, but some teams still have difficulty delivering features in a predictable manner. This organization decided to address the mismatch between what was being committed and what was accomplished by doing an experiment in work transparency.

About the author

About the author

About the author

[article]

Reduce Uncertainty in Agile Projects with #NoEstimates Thinking

Summary:
Estimation uncertainty in software projects is often not driven by the difficulty of the problem we are trying to solve, but rather by the health of our codebase, the quality of process, and how much discipline we have in our management practices. If you want to improve your estimates, then agile and #NoEstimates thinking can have the biggest impact on your team’s success.

Estimation uncertainty in software projects is often not driven by the difficulty of the problem we are trying to solve, but rather by the health of our codebase, the quality of process, and how much discipline we have in our management practices. If you want to improve your estimates, then agile and #NoEstimates thinking can have the biggest impact on your team’s success.

About the author

Pages

AgileConnection is a TechWell community.

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