sprint planning
|
How to Train Agile Product Owners Using Financial Terms Prioritizing stories for an upcoming sprint can lead to confusion and miscommunication between the product owner and agile teams. But putting that exercise into financial terms, such as purchase, budget, cost, and investment—a set of words that everyone understands, no matter what their area of expertise is—gets everyone thinking about value.
|
|
|
5 Ways Testers Can Mitigate Practical Risks in an Agile Team Testers who analyze quality in every aspect of the team’s deliverables also have a responsibility to mitigate risks and practical issues that are bound to come up, and help the team succeed in their product as well as at being agile. Here are five such issues that testers can help the team alleviate or avoid.
|
|
|
Stories, Epics, and Tasks: Organizing Agile Requirements Some teams only work with stories, but it can be difficult for a team new to agile to write stories that are easy to understand and provide value every time. An alternative is to add epics and tasks. Understanding the differences between each level and knowing what size story to use for each situation will improve the accuracy of your sprint planning.
|
|
|
Help Your Team Understand Its Velocity Teams should be working toward a target velocity that is based on historical evidence. There may be times when this figure needs to be adjusted, but teams that understand their velocity know that it is a good indicator of what they are capable of achieving in a sustainable way, and this will increase confidence for the teams and stakeholders.
|
|
Visit Our Other Communities
AgileConnection is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.