Agile
Methodology from Digital Micro-Learning Sprint: Agile 2
Section titled “Methodology from Digital Micro-Learning Sprint: Agile 2”Session led by David Tallan, Anna Boyden
How do you do it?
- Fail quickly / plan for it
- To do lists / Kanban (backlog, in progress, in review, done), moved away from sprints
- Issues could take between 1 day to years depending on the issue. All bugs, issues, features are all in the backlog
“Be a Learner” - How did you / your team balance time to learn vs. development. Due to the speed of agile, teams encounter new things often and the learning backlog for individuals can be as large as the development things to work on :-)
- Make a regular time in your day/week to do the learning
- Prioritize items in backlog that will give you the most learning rather than just value
Important skills?
- Communication and effective interaction, consensus building
Tool to use?
- JIRA
- GitHub
- Asana
- Microsoft Teams, Office 365
- Groups by project
- Wiki
Important relationships?
- Development and business team - if they are together, need a good dev-product manager
Co-design with Ontario citizens?
- Get feedback with consultation regularly with users or representative stakeholders and decision makers, Plan Do Check Act. Build trust with stakeholders