30 likes | 239 Vues
User Request. BAU Prioritisation process. Investment Prioritisation process. Stakeholders. Workshops To form a BRD. BA. PM. BRD. Stakeholders. BRD. Product Backlog. Workshops To signoff subset of items. Ranked list of requirements from BRD. Prioritised Ordered Sized.
E N D
User Request BAU Prioritisation process Investment Prioritisation process Stakeholders Workshops To form a BRD BA PM BRD Stakeholders BRD Product Backlog Workshops To signoff subset of items • Ranked list of requirements from BRD. • Prioritised • Ordered • Sized Bi Weekly Sprints Dev Team BA Signed off items Backlog Iterative delivery Dev & testing Sprint Backlog • Process: • BA: To run workshops with the business to expand upon and signoff subset of requirements from the BRD which are to be picked in the next sprint. • Meetings: • Regular Workshops with stakeholders specific to the subset of requirements picked up from the backlog. • Process: • BA + Dev + PO: to work out the priority and ordering of items in the Product Backlog. • Devto provide high level estimates on the requirements. • Meetings:
Requirement Initiation Technology Team User Request Production Support KSOR/BAU - BA JIRA – BAU Unscheduled • Process: • KSOR / BAU requirements from the below stakeholders are registered by the BAU BA: • User Requests • Bugs / Issues • Enhancement to existing functionalities • Small size new functionalities • Production Support • Automation requests for manual tasks • User requests directed to production support • Technology team • Performance improvements • Infrastructure/system upgrades (ARM, DMS, etc.) • Technical enhancements to improve the system (stability etc.) Process: For each of these requests the BA adds / modifies a JIRA in the “BAU Unscheduled” release. This may require some workshops with the stake holders to understand and clarify the requirements. All details must be entered in JIRA, which is the only true version of the exact requirement. JIRA (BAU Unscheduled)