Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to ANI - Agility Alignment in Team @ Vadodara | Agility in Teams | Hiren Pandya
Similar to ANI - Agility Alignment in Team @ Vadodara | Agility in Teams | Hiren Pandya (20)
More from AgileNetwork
More from AgileNetwork (20)
Recently uploaded
Recently uploaded (20)
ANI - Agility Alignment in Team @ Vadodara | Agility in Teams | Hiren Pandya
- 9. Program Wall âScaled Up Plansâ Inception Planning Story Mapping Sprint Planning Sprint Execution
- 10. Visualizing MVP (Minimum Viable Product) WHATâS OUR SCOPE? Review Requisition Create Standing Order Add Standing Order Close Standing Order Approve Requisition Approve or Reject Return for amendment Bulk Approval Auto Approve Issue Purchase Order Create Purchase Order Email / Print Purchase Order Reprint Receipt Goods Enter Goods Receipt Reverse Goods Receipt Complete / cancel outstanding order Action Variances Explain Price Variances Quantity Variance Request Credit Return to AP Process Exempt Invoices Enter Line Items Return to AP Provide Details Enter Credit Notes Enter Credit Note Apply Credit Note to Invoice Approve Invoice Approve Invoice Reject Invoice Request Credit Return to AP Process Payment Extract Payment Run Select / deselect Suppliers Review Payment Listing Submit for Approval Payment Approval Approve / Reject Invoices Approve / Reject Supplier Review Bank Account Changes Submit Payment Generate EFT File Print Cheques Remittance Update Send Remittance Advice Generate BPay File Procuring Goods & Services (Online Reqs) Invoice Processing (AP Workflow) Payment Managing Creditors Managing Suppliers Process Invoice Enter Invoice Attach Image Reverse Invoice Maintain Invoice Import Invoices Parameters & SettingsBulk Processing End of Period / Year Processing Enter Requisition Validate Requisition Credentials Select Requisition and type Select Supplier Enter items to buy Enter attach quotes Enter Delivery details Submit Enter Supplier Request Quotes Login Registered User Login Access to forms by permissions MVP Release Scope Epics in Future Releases Key Existing web enabled, no new UX for Release 1 Epic Feature MVP1 User Story Future Release User Story Dropped Story (TBC) Standing Invoice Posting Reports ATO Payment Reporting Reports Enquiry Forms Purchase Card Process Invoice / Order Reallocation Submit Payment At risk for June delivery
Editor's Notes
- Salient points Each stage completed and signed off before the next starts Big up front analysis and design Different people involved in each stage Communication through documentation Consider walking them through this with a real example: Manager somewhere comes up with a list of requirements Over the next 3-4 months a technical writer will flesh these out into detailed technical software requirements (ie. 1.1.1 Table must contain 4 headings etc) Business analyst then will do some analysis over the requirements â back and fore for another 2-3 months Design (UML diagrams, architecture mapping, etc) â another 2-3 months (already about a year since requirement was first thought of) Plan developed Development (developers remotely somewhere working through list of requirements against a plan) â probably about a year Testing (probably some issues to go back and fore between development) Then acceptance testing happens but maybe the team has long gone â or no longer need the software Millions of pounds wasted with potentially nothing to show for it
- Salient points Each stage completed and signed off before the next starts Big up front analysis and design Different people involved in each stage Communication through documentation Consider walking them through this with a real example: Manager somewhere comes up with a list of requirements Over the next 3-4 months a technical writer will flesh these out into detailed technical software requirements (ie. 1.1.1 Table must contain 4 headings etc) Business analyst then will do some analysis over the requirements â back and fore for another 2-3 months Design (UML diagrams, architecture mapping, etc) â another 2-3 months (already about a year since requirement was first thought of) Plan developed Development (developers remotely somewhere working through list of requirements against a plan) â probably about a year Testing (probably some issues to go back and fore between development) Then acceptance testing happens but maybe the team has long gone â or no longer need the software Millions of pounds wasted with potentially nothing to show for it