From dd91e92c1aa6bacb0f12d0fd6d114598b0a5d3b0 Mon Sep 17 00:00:00 2001 From: Cleop Date: Wed, 17 Jan 2018 11:57:12 +0000 Subject: [PATCH] #24 Updates issue flow --- readme.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/readme.md b/readme.md index 62ab8e0..8abad81 100644 --- a/readme.md +++ b/readme.md @@ -155,11 +155,13 @@ Further reading: https://en.wikipedia.org/wiki/Brooks%27s_law At dwyl we use github labels to help indicate the type, duration and status of an issue. The following image outlines the lifecycle of an issue using labels. In -this example there are 3 actors, the Product Owner (PO), the Scrum Master -(SM) and the developer (Cleop). +this example there are 3 actors, the Product Owner (PO), the dev team +(Scrum Master and developers) and in this case the developer who has completed +the issue: 'Cleop'. - + +To learn more about our contributing process see: https://github.com/dwyl/contributing. ## When to create a new issue when dealing with bugs 🐛 and enhancements :ribbon: