5.1 Project Operational Templates
- How many users are going to use the functionality?
- Describe your current ‘How to’?
- Deadline for the functionality?
- Why do you need that functionality?
- Provide stakeholders for requirement gathering/ user testing
- Languages used
- Describe your pain points?
- Are there any parts of your current processes manual? How many people currently working on them?
- Do they use other systems currently? Any third party? Any tools (Excel …)?
- How many people can access sensitive information/ do we need permission sets?
- Are there any existing documentation they can share
- Who are the beneficiaries/ receivers of the functionality/Target Audience?
- Short/Long term ambition of the company
- International set-up? Currency used?
- Define MOSCOW status of each requirement (Must Have/ Should Have/ Could have/ Can’t Have)
- Do you have a Glossary available?
(Needs an existing scenario)
Process mapping of the ‘as is’ and the ‘to be’ with a proof of concept (Lucidchart/ using a Dev Sandbox for POC) using SwimLane model, or colour coding for Salesforce Actions/ End user action
- Numbering of the user Stories (ColumnA)
- ’As a’ ‘I want to’ ‘So I can’ (Column B)
- Acceptance Criteria (Column C)
- Estimation/Sizing (Column D)
- Status of the ticket (Backlog/ Ready for Dev/ In Dev/ Ready for QA/ In QA/ QA complete/ Deployed)
- Solutions (Column E)
- QA testing steps/results (Column F)
- Stakeholder/ SME (Column G)
- Change set
Demo of the functionality Ask stakeholders for feedback. If all good, you push to production and hand over to training If changes needed, gather new requirements > Update process maps > Create new user stories Understand time savings from deploying new functionality
List of questions to generate, process mapping, user stories, demo what you’ve done– show and tell.