communitiesuk / mhclg-epc-alpha

MHCLG EPC Alpha
Mozilla Public License 2.0
2 stars 4 forks source link

[Service Standard] Use agile methods #26

Open jukesie opened 5 years ago

jukesie commented 5 years ago

To pass the alpha, beta and live assessments, you usually need to:

explain how you’re working in an agile way, using agile tools and techniques, and how you’ll continue to do so when the service is live

explain how you and your team have reviewed and iterated the ways you work to fix problems

explain how your team is using agile tools and techniques to communicate with each other

give an example of how the team has responded to user research and usability testing

show that your governance is agile, based on clear and measurable goals, and has a clear focus on managing change and risk in real time

You also need to discuss:

the design options you explored for your prototype and the reasons you discarded some

how the design of the service has changed over time because of what you found in user research the design options you’re considering for your assisted digital support

any problems that you found in research which you’ll have to solve to design the service, and how you plan to solve them

davidtoldmeto commented 5 years ago

Team of engagement -https://github.com/notbinary/mhclg-epc-alpha/wiki

davidtoldmeto commented 5 years ago

Facilitating daily stand ups using slack to collate and publish feedback in epc-alpha group channel

davidtoldmeto commented 5 years ago

drafting alpha roadmap into sprints/whiteboard

davidtoldmeto commented 5 years ago

Realtimeboard tool that we are using enables the team to collaborate and plan in real time throughout the process.

Also allows for real time and open sharing with stakeholders outside squad