SlideShare utilise les cookies pour améliorer les fonctionnalités et les performances, et également pour vous montrer des publicités pertinentes. Si vous continuez à naviguer sur ce site, vous acceptez l’utilisation de cookies. Consultez nos Conditions d’utilisation et notre Politique de confidentialité.
SlideShare utilise les cookies pour améliorer les fonctionnalités et les performances, et également pour vous montrer des publicités pertinentes. Si vous continuez à naviguer sur ce site, vous acceptez l’utilisation de cookies. Consultez notre Politique de confidentialité et nos Conditions d’utilisation pour en savoir plus.
As an industry based lobby group we were faced with Legislation to reduce government funding by $1.9B. We needed to respond quickly and adopted an Agile approach to our digital campaign strategy in order to have a skinny version of the website up and running as soon as possible. We used a mix of Scrum and Kanban methods to prioritize widgets we required on the website and ensure our campaign remained responsive to stakeholders and built iterative changes to the site in order to respond to stakeholders and the political debate.
The session will be a short 10min talk focusing on how a mix of Agile approaches, namely Kanban and Scrum were used as a management tool to coordinate the development of a new website for the campaign. The presenter will explain how the adoption of Scrum allowed the team to iteratively build features based on weekly sprint cycles and ensured weekly collaboration and communication between product owner, designers and developers of the website.
The presenter will demnonstrate how the introduction of a Kanban board to the Scrum process helped to manage the backlog of work packages and help focus the team on the ranked priorities for the current sprint. This provided a process to manage Workflow and allowed the team to remain flexible and responsive to the changing environment and stakeholder needs when changes were required mid sprint
• The blend of Scrum and Kanban helped to focus the team on the priorities and remain flexible and responsive to the changing environment and stakeholder needs
These Agile methods are an effective management tool and can aid coordination of work effort to deliver a campaign strategy
How to Save Your Industry $1.9B Using Agile Methods<br />Mia Horrigan<br />Chief Information Officer AHIA<br />August 2011<br />
Legislation to reduce govt funding by $1.9B<br />Previous mass media channels not measurable, responsive or targeted <br />Take debate to consumers: digital campaign<br /> ADKAR<br />Get users engaged or loose $1.9B<br /><ul><li>Awareness
Reinforcement</li></ul>continuous integration<br />value stream<br />+<br />release 1.0<br />+...+<br />UX Design <br />release n<br />embed in<br />User stories<br />Elements of User Experience<br />Prioritise delivery of value in backlog<br />SCRUM<br />skinny <br />solution<br />What we did<br />Kanban<br />build knowledge<br />from retrospectives about ‘value’<br />More value = act to save the Industry<br />
Sprint zero – Planning <br />Scrum<br />Elements of User Experience<br />Framework Elements<br />Strategy, Scope, Structure, Skeleton and Surface <br />Things to Produce<br />Things to Do<br />Things to Consider<br />(e.g. requirements)<br />
Weekly Sprint cycles<br />Continuous integration to build upon skinny solution to respond to evolving needs Collaboration between product owner, scrum master and team <br />Needs changing so estimation of what could be done and definition of done important <br />Cost ($$$ vs Time vsOpportunity)<br />Scrum<br />
Needed to prioritize widgets to ensure campaign remained responsive to stakeholder needs<br />Visual tool to manage the backlog, focus team on the ranked priorities<br />Process to manage workflow and remain flexible<br />Kanban<br />
Pilot of Kanban on one project<br />Project Kanban Board <br />Sprint backlog in ranked priority<br />Features being produced<br />What has been produced<br />
If one Board is great, why not two?<br />Project interdependencies<br />Shared resources<br />
Viewed all 3 projects within the campaign<br />Multidisciplinary teams across the projects<br />Applied learnings from one to the next<br />“Scrum of Scrums” Kanban Board<br />Three projects on the board<br />Three different sprints in progress<br />Project interdependencies<br />Streams of work with shared resources<br />
Team identified BAU activities and these became a BAU backlog <br />Identified lessons learnt and suggested improvements to business processes <br />Learnings for BAU<br />
What we learned<br />Multidisciplinary approach and blend of Agile and UX tools:<br />Remain flexible and responsive <br />Prioritise features and manage the backlog of work<br />Aided focus and coordination<br />Kanban Board was an effective visual communication tool (team & org)<br />Scrum effective way to continuously integrate features and keep the team on track<br />Value of Scrum master <br />
Thank you<br />Mia Horrigan <br />Chief Information Officer - AHIA<br />Vice President - Women in Information and Communication (WIC ) <br />Agile CSM, MBA, Post grad Dip Mgmt, B Comm<br />Mia.email@example.com<br />Maria.firstname.lastname@example.org<br />@miahorri<br />www.zenagile.wordpress.com<br />www.miahorri.wordpress.com<br />Mia (murphy) horrigan<br />