Stories are small and must be completed in a single iteration (see the splitting stories section). It’s a vertical slice of functionality to ensure that every Iteration delivers new value. Most stories emerge from business and enabler features in the Program Backlog, but others come from the team’s local context.Įach story is a small, independent behavior that can be implemented incrementally and provides some value to the user or the Solution. But the detailed implementation work is described through stories, which make up the Team Backlog. Collectively, they describe all the work to create the solution’s intended behavior. SAFe’s Requirements Model describes a four-tier hierarchy of artifacts that outline functional system behavior: Epic, Capability, Feature, and story.
Enabler stories bring visibility to the work items needed to support exploration, architecture, infrastructure, and compliance. User stories deliver functionality directly to the end user. Through acceptance criteria and acceptance tests, stories get more specific, helping to ensure system quality. Details are deferred until the story is ready to be implemented. Stories provide just enough information for both business and technical people to understand the intent. Each one is intended to enable the implementation of a small, vertical slice of system behavior that supports incremental development.
They are short, simple descriptions of functionality usually told from the user’s perspective and written in their language. Stories are the primary artifact used to define system behavior in Agile. Agile Teams implement small, vertical slices of system functionality and are sized so they can be completed in a single Iteration. Stories are short descriptions of a small piece of desired functionality, written in the user’s language. Bill Wake, co-inventor of Extreme Programming Story Stories act as a ‘pidgin language,’ where both sides (users and developers) can agree enough to work together effectively.
0 kommentar(er)
