Storyotypes and Scaling
Storyotypes are re-useful repeatable patterns that help teams get to done for their work (definition of Done). Teams develop their own repeatable patterns. Storyotype patterns are usually either examples or templates of Stories (and Epics) that contain common, reusable, information for work. Repeatable work patterns are often shared, as a definition, across teams and strongly support the dynamics necessary for scaling scrum.
Storyotypes and Definition of Done
A storyotype is a means for capturing common information within a team’s work and reusing it. The facilitator/coach is the person who is responsible for helping the team. The facilitator/coach helps the team capture, document and use it’s recurring patterns of work. Storyotyping helps a team figure out how they can get to done. When a team is ‘done’ we say it has met or found a suitable definition of Done. You don’t know you are done until you are ‘done’ which often includes a clear acceptance test.
Storyotypes and Domains
There is no definitive list of common storyotypes. Although, some domain patterns are so closely mirrored that we begin to build systems that contain similar captured patterns of work. For example, CMS systems, standardized sales process calls, setting up web servers in ‘our environment’, write code, etc. are all examples of work items that have a recurring nature.
Storyotypes and Analysis
Before we start our work, it is not really what are the storyotypes; it’s about the storyotyping, in other words the analysis. Hence, storyotyping is an ongoing activity that finds (and documents) reusable patterns in a Team’s Stories and Epics. Storyotyping helps a team decompose the work before they start. In my experience, there are many kinds of Stories (and storyotypes), including but not limited to: Coding Stories, Analysis Stories, Environmental Stories, Support Stories, and so on.
Storyotypes and Fundamentals
Storyotyping is a fundamental way to manage work. Storyotyping is a fundamental because it supports both analysis (before we start) and done (how we finish). Good teams know and use their appropriate storotypes.
Storyotype is a just a play on the word story. Story in Scrum and in Get To Done is a request for something of value from the team. Stakeholders clearly request different types of work from a team. Well-formed Teams, analyze the work type upfront in order to help themselves plan. Teams that approach similar jobs do so with a standard of care. Standards are what any professional understands about doing a good job in his or her work. Teams know and use their standard of care. In conclusion, storyotyping helps us capture the standard and use it from start to finish.
Share this Post