scrum
Question
|
Should Stories be kept as permanent system documentation or should requirements be maintained to document the system Should stories be kept in place of requirements to provide permanent system documentation or should a functionally organized set of requirements be maintained as this documentation. Either way, I am trying to figure out the best way to maintain a description/model of the system being maintained that is understandable to non technical and technical staff and provides a starting point for analyzing future changes to the system. |
||
 |
Estimating Business Value in the Shark Tank You can use analytical methods to assign business value to a user story, of course, but another way is simple estimation. Allan Kelly describes an estimation exercise that combines the Scrum tool of planning poker with a TV show format to add some fun. You end up with enlightening conversation and revealed requirements. |
|
 |
Who Is the Real Product Owner? Communication is always vital on an agile project to ensure everyone is on the same page, but it's perhaps most important in a relationship between a vendor and a customer. Here, Marcus Blankenship relates a personal story about a project where communication failed, and gives some good tips for how to avoid it happening to you. |
|
 |
Use Lean Thinking to Accelerate DevOps Performance for Agile Teams Leaders in agile organizations should consider adding lean techniques to their DevOps practices. Lean thinking can accelerate DevOps delivery by providing a set of processes and principles to help create more beneficial products, save money, boost productivity, reduce waste, and map to value. |
|
|
Which action comes first? Is it Acceptance criteria of user story or tasks of user story in Sprint planning session? When product owner express the userstories, scrum team asks for clarification for better understanding.What is the order of actions in sprint planning, is it that tasks of particular user story should be entered in in scrum board or acceptance criteria of the user should be defined first and then entering the details of develeopment tasks with the estimates derived? can you help me with this? |
||
 |
Become a Great ScrumMaster Performing all the functions required to facilitate project teams as ScrumMaster can be a task. Zuzi Sochova describes creative ways to become a master of Scrum by adopting a ScrumMaster state of mind. |
|
 |
Scaling Agile: A Guide for the Perplexed: An Interview with Sanjiv Augustine
Podcast
In this interview, Sanjiv Augustine, the president of LitheSpeed, sheds light on a handful of scaling frameworks, including the Scaled Agile Framework (SAFe), Large-Scale Scrum (LeSS), and the simple scrum of scrums meeting. |
|
 |
The Fundamentals of Agile: An Interview with Jeff Payne
Podcast
In this interview, Coveros CEO and agile instructor Jeff Payne discusses why you should make the move to agile, its many benefits, and how to transition. He also explains his SQE Training course, Fundamentals of Agile Certification. |
|
 |
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. |
|
 |
STAREAST 2015 Interview with Matt Heusser on Lean Software Testing
Video
In this interview, Matt Heusser covers how most organizations test now, presents ways you can improve your company's approach to lean, and demonstrates lean tools that can help you understand software development and test flow in a different way. |
Pages
Recommended Web Seminars
Featured Resources
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.