1 / 11

Enhancing Collaboration Through User Stories in Agile Development

Collaboration is essential for successful Agile practices. This guide explores how user stories can facilitate teamwork by fostering a common goal, commitment, trust, and respect among team members. By breaking down story components—such as acceptance criteria, development tasks, and story ownership—teams can improve communication and accountability, ultimately leading to better outcomes. Discover how to create clear, measurable success criteria and leverage diverse skills to enhance efficiency, quality, and team morale.

twila
Télécharger la présentation

Enhancing Collaboration Through User Stories in Agile Development

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Steve Fastabend Agile Coach RedpointTechnilogies sfastabend@redpointtech.com Using User Stories for Collaboration

  2. What is Collaboration Definition of COLLABORATE 1: to work jointly with others or together especially in an intellectual endeavor 2: to cooperate with or willingly assist an enemy of one's country and especially an occupying force 3: to cooperate with an agency or instrumentality with which one is not immediately connected

  3. Why Collaborate • Improve efficiency • Improve quality • Improve morale • Improve success rate

  4. What does it take to collaborate • Common Goal • Measureable Success Criteria • Commitment • Trust • Respect

  5. What is a Story • As a presenter I want to describe a story so that my audience understands how the parts interact. • Mike Cohn says that software requirements are a communication problem. Those what want software must communicate with those who built it. • A story is also a document that can be used for commitment.

  6. Investigating Story Parts • Story statement • Clear understandable story that is “shovel ready” • Acceptance Criteria • Describes what the expectations are. • Used to embellish the story • Test cases • Guarantee that function is useful to the user. • Include expected and unexpected scenarios • Development Tasks • Steps to completely deliver functionality • Cross discipline as needed

  7. Story Grooming • This is the process of reviewing the stories as they develop. • Everyone has the opportunity to clarify story intent. • Allows every to develop an common understanding.

  8. Story Part Ownership • Story statement / Acceptance Criteria- Business Analyst • Should be treated as a developer treats source code. • Represents a contract with the user, and should not substantially change. • Acceptance criteria - Quality Assurance • Add and test cases • Development Tasks – Developer • Steps to completely deliver functionality • Estimate

  9. Orchestrating Collaboration Statement Owner Business Analyst Trust Respect Commitment Trust Respect Commitment Test Cases Owner Quality Assurance Tasks Owner Developer Trust Respect Commitment

  10. Summary • A complete user story is a trust agreement between the user and the development team • Clear goals are key to collaboration • Trust and respect are built with measurement and account • The team can work together to leverage each others skills • Successful teams hold each other accountable for the commitments

  11. Questions ?

More Related