...
Comparison with current processes
Bug
Use case example - adams report
Adam sent email
John raises issue + attaches the document + adds a comment - need more clarity
Adam should be alerted
Step | Current process step |
---|
Outcome ok
Outcome not ok
Possible next steps | proposed process | ||
---|---|---|---|
Customer identifies problem and sets priority |
|
|
|
Support alerted | unread item alert |
Clarify
Support responds to gain clarity if required
| Support alerted to unread item | ||
Support reviews | Review issue | Support Determines
| Read and review
|
Not supported functionality / new functionality required | Explain to customer not supported and new function required - Close issue | Alert customer not supported and issue closed
| Customer alerted all of above outcomes |
Training issue | Explain to customer not supported and training required with link to training document - Close issue | Alert customer training required and issue closed
| |
Not Clear | Customer asked to clarify | Alert customer clarity required | |
Clear but cannot reproduce | Customer asked to reproduce | Alert customer clarity required | |
Customer Alerted clarity required | unread item alert |
|
|
| ||
Support Alerted clarity provided | unread item alert | Support |
Reviews | |||
Clear and Reproducible | Steps to reproduce documented |
| |
Can Reproduce and is Bug |
Steps to reproduce defined
Assign developer
developer is assigned / works with support
Test
Testing of changes
Test
Dev fixes problems found
Support define priority | Await start | ||
Developer Review | Developer estimates effort required | Await start | |
Developer start | Make system changes | Test | |
Test | Test based on steps to reproduce |
| |
Test ok | Testing ok | Done |
New Feature
Step | Current process | proposed process |
---|---|---|
Customer report |
| |
Clarify | Support identifies new feature required | |
Clarify | High level design options considered | |
Clarify | Discuss with customer to clarify requirements | |
Design | Define changes required to system and resulting test plan | |
Design | Review with customer to get sign off on design and $ | |
Build | developer is assigned | |
Clarify | Clarification questions if required from poor design | |
Test | Testing of changes | |
Build | Dev fixes problems found in testing | |
Test | Testing ok | |
Done | Released into production and issue closed | |
Invoice | Invoice sent and paid |
...