practicalli / practicalli/engineering-playbook
Establishing process
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 12
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
A process is using the tools and techniques that are effective for your team and organisation
Process is a way to communicate and share practices and workflows across the organisation
Process should not be ridged and inflexible
Case studies
Reinventing the process Brittas insurance experience
- no understanding of what a process is
- process workshop biased toward product management
- no understanding of value proposition of company
Result
Reinvented the same process (Prince2) with a company name
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named in the issue. Read the existing engineering-playbook structure and related process guidance first, then determine where this material belongs and what gaps it should address. Done means the process explanation and Brittas insurance case study are clear, accurate, and integrated into the playbook.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100