I already created a branch for this. Testing the ease of use of the Issue Tracker flow from my phone.
The pattern is still relevant and should.be added.
DCO agreement
By submitting this pull request, I comply with the license in the Developer Certificate of Origin.
Specifically, I acknowledge that the owner of this repository has the right to use my contribution as he/she sees fit.
I will not take legal action against the owner or maintainer of this repository on the basis of copyright infringement.
How to make a Suggestion
Remove verbatim content, and fill out the sections below.
These fit the structure of the existing patterns.
You can submit this template as an easier way to add to the collection, as an alternative
to creating your own github fork.
OPERAS
This is a general purpose pattern to frame progress towards a specific goal by using the ’divide and conquer’ technique and a clear checklist-style plan of attack. The goal is to give users a mental map of the different actions that are required to complete a 'milestone'.
TODO: add 'milestone' and 'divide and conquer' to the Glossary or as seperate micro-patterns.
Applicable Context
This pattern can be helpful to:
keep tabs on the status of various goals and objectives, by using the step names as status indicators
have a clear idea of progress made, when combined with the KPI pattern
split big goals into bite-sized chunks
stay committed to your goals without feeling like you are drowning in a never ending cycle of irrelevant 'sidequests'
Compatible with:
most agile frameworks (increments, reflection and adaption)
The OPERAS mental model is a description of the flow you go through when advancing a task from "TODO" status to "DONE". A task can be any size to start with. Possivle sizes of actionable items range from 'build a house' to 'do the dishes'. How hard this seems to you, is called the 'perceived required effort'. For the same task, this perceived effort can vary a lot from person to person. But the explanation of that is not in scope of this pattern description.
{width=50%}
Key Performance Metrics
How do we know if we applied the pattern succesfully? What are our 'red flags' that should
trigger a adaption of the style of application?
KPI's give us a way of measuring succesful application of the pattern.
These can also be used to validate certain assumptions about the context before
applying the pattern.
example of a precondition KPI: 'The team turnover is higher than 1/month'
example of a postcondition KPI: 'The team turnover is lower than 1/year'
Related Patterns and Resources
Add links to other patterns in the collection (or external ones), please add
references to the source material if you were inspired by someone else's work.
Feel free to add your own previous work as a reference.
Item
Description
Action
Some thingy
Why it is here
What to do with it?
Pattern meta information
Credit should go where it is due. If you are so kind to donate your knowledge to
the open source / self-improvement community, we believe you've earned the (bragging) right to
let people know it was your work or experience that helped them.
PATTERN SUGGESTION: OPERAS
DCO agreement
By submitting this pull request, I comply with the license in the Developer Certificate of Origin. Specifically, I acknowledge that the owner of this repository has the right to use my contribution as he/she sees fit. I will not take legal action against the owner or maintainer of this repository on the basis of copyright infringement.
How to make a Suggestion
Remove verbatim content, and fill out the sections below. These fit the structure of the existing patterns. You can submit this template as an easier way to add to the collection, as an alternative to creating your own github fork.
OPERAS
This is a general purpose pattern to frame progress towards a specific goal by using the ’divide and conquer’ technique and a clear checklist-style plan of attack. The goal is to give users a mental map of the different actions that are required to complete a 'milestone'.
Applicable Context
This pattern can be helpful to:
Compatible with:
Description of Pattern
The OPERAS mental model is a description of the flow you go through when advancing a task from "TODO" status to "DONE". A task can be any size to start with. Possivle sizes of actionable items range from 'build a house' to 'do the dishes'. How hard this seems to you, is called the 'perceived required effort'. For the same task, this perceived effort can vary a lot from person to person. But the explanation of that is not in scope of this pattern description.
Key Performance Metrics
Related Patterns and Resources
Pattern meta information