![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj18xFwDd_e-feHhY6XeEv5uieWrTOyv-fGkSABjxrTCzDkxNa67q67IwjIXPvjC5xm5qzyXuZx8CAtLV-RNZboft89DxT6cefojC1xmFJ0uj2U_WOC5APM1aveHszx7Xvsa1kPTZuqeBZE/s1600/2015-02-26+19.45.13.jpg)
In the beginning:
Teacher sees a need to have teams become better at- organizing their work
- working better as a team
- determining if/when teams will be done by the deadline
It continues with:
An Agile Transformation Coach who loves to work with kids (and used to teach her stuffed animals…oh yeah, that's me)It continues with:
The Teacher and Coach come together to determine if teaching Agile techniques will provide value by assessing the- current situation and needs
- willingness of the students
- support of the principal
Let's Start:
We have teams!
There are 2 classes with each class broken into 4 teams of 2-3.We have a Product Owner!
The Teacher becomes responsible for the backlog: writing user stories, prioritizing, ordering, accepting stories, etc.![]() |
Students reviewing the stories the Product Owner created |
We'll use a mixture of Agile Techniques!
- Scrum Activities (Product backlog refinement, Sprint planning, Daily Scrum, Sprint review, Sprint retrospective)
- Scrum Artifacts (Product increment, Product backlog, Sprint backlog)
- Scrum Roles (Development Team, Product Owner, ScrumMaster)
- Kanban Principles (Visualize work with cards, Limit Work in Process, Continuous Improvement)
- XP Rules (User Stories, Pair Programming, Spikes usage, XP Values: Simplicity, Communication, Feedback, Respect, Courage)