際際滷

際際滷Share a Scribd company logo

Agile @ Siteimprove - presentation at Scrum Day Denmark 2018

Mikkel Toudal Kristiansen
Mikkel Toudal Kristiansen

Presentation from Scrum Day Denmark 2018, about how Siteimprove used agile practices to build their SaaS product

1 of 17
Download to read offline
Agile @ Siteimprove Mikkel Toudal Kristiansen, Agile Coach at Siteimprove Scrum Day Denmark 2018
About me 1995 First job as a developer 2005 Agile, Scrum, Kanban and Lean evangelist 2013 Professional Scrum Trainer with Scrum.org 2018 Agile Coach at Siteimprove Mikkel Toudal Kristiansen @otwtbs mikkel.kristiansen@gmail.com
Danish SaaS company founded in 2003 100 employees in 2014 530 today! Offices in 9 countries HQ is still in the heart of Copenhagen All development happens at HQ Began as a broken links checker Now also checks accessibility, GDPR compliance, SEO, and much more
Our product And much more
Organization The product is split into several functional areas, so We are organized into 4 Product Units and a Core Unit A Unit is split into 2-3 Teams
Collaboration in Teams Teams at Siteimprove are permanent are co-located at HQ are cross-functional use Scrum, Kanban, or a mix of the two
How do we work?
UX and Agile? Every Product Unit has one or more UX specialists Product Owners and UXers ideate and design prototypes We run Alpha and Beta tests with FirstImprovers We want to include customers more in our design process Design Sprints Co-creation Early and frequent validation of assumptions
6 months lets evaluate!
6 months later Product Units and Teams are major improvements! Cross-functional Teams work! Lots of new features and functional areas released! The good However, coordination, alignment and collaboration are challenged Across Teams in a Unit Across Units With the rest of the organization We have become too siloed The bad
The traditional solution More management More meetings More documentation Stricter processes for handovers Less productivity
The available levers
Options architecture Establish a loosely coupled architecture One core platform A number of plugins, each depending only on the core Benefits include: Plugins can be owned by single Units or Teams Less coordination is necessary More autonomy for Units and Teams
Options people Make the Product Units and Teams even more cross- functional Introduce scaling practices from the Nexus framework
Options work Release management Marketing materials and campaigns Training of Sales and Support Organize work to happen in parallel instead of sequence Between people, Teams, Units and beyond Between items on the Product Backlog On software components and technology Manage dependencies explicitly and deliberately
As we grow, we may need multiple Nexuses But what about the future? Currently, one single Nexus-like structure is sufficient The architecture (core + plugins) will enable several paths Each Product Unit could become a Nexus Or we could group 2 or more Product Units into a Nexus
Thank you!

More Related Content

Agile @ Siteimprove - presentation at Scrum Day Denmark 2018

  • 1. Agile @ Siteimprove Mikkel Toudal Kristiansen, Agile Coach at Siteimprove Scrum Day Denmark 2018
  • 2. About me 1995 First job as a developer 2005 Agile, Scrum, Kanban and Lean evangelist 2013 Professional Scrum Trainer with Scrum.org 2018 Agile Coach at Siteimprove Mikkel Toudal Kristiansen @otwtbs mikkel.kristiansen@gmail.com
  • 3. Danish SaaS company founded in 2003 100 employees in 2014 530 today! Offices in 9 countries HQ is still in the heart of Copenhagen All development happens at HQ Began as a broken links checker Now also checks accessibility, GDPR compliance, SEO, and much more
  • 5. Organization The product is split into several functional areas, so We are organized into 4 Product Units and a Core Unit A Unit is split into 2-3 Teams
  • 6. Collaboration in Teams Teams at Siteimprove are permanent are co-located at HQ are cross-functional use Scrum, Kanban, or a mix of the two
  • 7. How do we work?
  • 8. UX and Agile? Every Product Unit has one or more UX specialists Product Owners and UXers ideate and design prototypes We run Alpha and Beta tests with FirstImprovers We want to include customers more in our design process Design Sprints Co-creation Early and frequent validation of assumptions
  • 9. 6 months lets evaluate!
  • 10. 6 months later Product Units and Teams are major improvements! Cross-functional Teams work! Lots of new features and functional areas released! The good However, coordination, alignment and collaboration are challenged Across Teams in a Unit Across Units With the rest of the organization We have become too siloed The bad
  • 11. The traditional solution More management More meetings More documentation Stricter processes for handovers Less productivity
  • 13. Options architecture Establish a loosely coupled architecture One core platform A number of plugins, each depending only on the core Benefits include: Plugins can be owned by single Units or Teams Less coordination is necessary More autonomy for Units and Teams
  • 14. Options people Make the Product Units and Teams even more cross- functional Introduce scaling practices from the Nexus framework
  • 15. Options work Release management Marketing materials and campaigns Training of Sales and Support Organize work to happen in parallel instead of sequence Between people, Teams, Units and beyond Between items on the Product Backlog On software components and technology Manage dependencies explicitly and deliberately
  • 16. As we grow, we may need multiple Nexuses But what about the future? Currently, one single Nexus-like structure is sufficient The architecture (core + plugins) will enable several paths Each Product Unit could become a Nexus Or we could group 2 or more Product Units into a Nexus