Keppel Ltd. 1Q 2024 Business Update Presentation Slides
Rijksoverheid.nl and scrum JBoy Aarhus 2010
1. SCRUM and Rijksoverheid.nl | november 3, 2010
From 16 websites to 1:
www.rijksoverheid.nl
Using SCRUM, good
people and web standards
Gerrit C. Berkouwer
J.Boye10 - Aarhus
3. SCRUM and Rijksoverheid.nl | november 3, 2010
From 16 websites to 1:3
From 16 to 1 websites
New CMS/hosting
New UI-design
New content-strategy
Migration of 16 websites
13 clients/stakeholders
And more…
4. SCRUM and Rijksoverheid.nl | november 3, 2010
From 16 websites to 1:4
2008 2009 2010 2011
preparation……………………….realisation
5. SCRUM and Rijksoverheid.nl | november 3, 2010
From 16 websites to 1:5
More than 40 servers HA/HP
± 80.000 documents
± 20 theme’s and 700 subjects
± 35.000 unique visitors per day
± 235.000 pageviews per day
Facts and figures
Rijksoverheid.nl
6. SCRUM and Rijksoverheid.nl | november 3, 2010
From 16 websites to 1:6
3 years…that’s
26280 hours or
94.608.000 seconds…
new cms, information architecture, new hosting-platform,
usability, webstandards, headaches, metadata, user centered
design, persona’s, java, content management, findability,
migration, frontend-performance, spring, high availability, high
performance, clustering, content-strategy, government, css, xhtml,
jquery, javascript, importer, pizza ,UI-design, editorial staff,
governance, estimations, security, coffee, URL-redirects, organisation
8. SCRUM and Rijksoverheid.nl | november 3, 2010
From 16 websites to 1:8
How to organize this?
Go see: ‘We've killed their darlings
- daring to go from 16 websites to one’
By my colleague Gemma Sweeren, tomorrow
at 16.00 in the ‘Web Governance’ track!
9. SCRUM and Rijksoverheid.nl | november 3, 2010
From 16 websites to 1:9
let’s talk
SCRUM
How to implement this?
10. SCRUM and Rijksoverheid.nl | november 3, 2010
From 16 websites to 1:10
• human interaction over technology and huge
projectplans
• not imposing techniques
• webstandards and website-speed a must!
• stability and flexibility
• include Usability testing
Starting points
11. SCRUM and Rijksoverheid.nl | november 3, 2010
From 16 websites to 1:11
Working
software
Product
backlog
Sprint
backlog
every
24 hours
3 weeks
12. SCRUM and Rijksoverheid.nl | november 3, 2010
From 16 websites to 1:12
Reasons
• big project
• changing requirements
• for 13 clients...
• flexibility needed
• speed needed
• multiple disciplines
• internal and external
projectmembers
What we did
Focus your tasks…
NO 100% functional
design
NO 100% technical design
Change is welcome!
Short iterations
DAILY communication and
mini-planning
13. SCRUM and Rijksoverheid.nl | november 3, 2010
From 16 websites to 1:13
Goals
• deliver high quality
• deliver often
• deliver quick
• deliver on time
• direct results for clients
• learn and adapt!
What we did
Focussed teams:
• development-teams
• design-team
• infrastructure-team
• migration-team
• editorial team
Demo and live every 3
weeks…
Dedicated ‘Productowner’
17. SCRUM and Rijksoverheid.nl | november 3, 2010
From 16 websites to 1:17
Soft Goals
• communication
• human interaction
• collaboration
• increase morale
• increase motivation
• increase trust
• increase creativity
• building trust...
What we did
Good people…
Multidisciplinary teams
Daily team stand-ups
Scrum-of-scrums stand-
up
Story-finding
Estimation sessions
Retrospective sessions
21. SCRUM and Rijksoverheid.nl | november 3, 2010
From 16 websites to 1:21
• transparency, we know what we are doing
• planning is (almost) fun now !
• working in pairs among almost all disciplines
• no walls between teams
• good demo’s, on time and in KNOWN scope
• quality is very high
building trust...proud teammembers
Results
23. SCRUM and Rijksoverheid.nl | november 3, 2010
From 16 websites to 1:23
• good people to do the magic
• lots of stakeholders: how to keep them into
SCRUM and how to communicate?
• (usability) testing
• www.rijksoverheid.nl: visitors, stability, security
Challenges/discussion
Our project
government
projectmanager
Big
- after 15 years of 16 websites….
webstandards, quality, simpel!
political driver: cutbacks on civil servants and money…
‘establish a shared service’
16 instead of 1 website must be cheaper
CAN IT BE BETTER?
- love it!
- timeframe…
- we had to come up with something good
how to organize this
how to implement this
all disciplines involved!
human interaction over technology and huge projectplans
not impose techniques but coaching teams and facilitating
include User Centred Design
include (usability) testing
include automatic testing
include continuous integration
Productowner: quality assurance, keeping the quality on a certain level: webstandards, accessibility, website-speed, stability, durability, focus!
Teams, working together and daily communication. No big plans, but ITERATION.
Learn and adapt!
bulletproof
Scope negotiation
Bulletproof, fence off all outside stuff…
Productowner: quality assurance, keeping the quality on a certain level: webstandards, accessibility, website-speed, stability, durability, focus!
Teams, working together and daily communication. No big plans, but ITERATION.
Learn and adapt!
communication, (human) interaction, collaboration and flexibility
increase morale of the teams
increase motivation of the teams
increase trust between client and project
increase creativity
building trust...
Productowner: quality assurance, keeping the quality on a certain level: webstandards, accessibility, website-speed, stability, durability, focus!
Teams, working together and daily communication. No big plans, but ITERATION.
Learn and adapt!
Productowner: quality assurance, keeping the quality on a certain level: webstandards, accessibility, website-speed, stability, durability, focus!
Teams, working together and daily communication. No big plans, but ITERATION.
Learn and adapt!
Productowner: quality assurance, keeping the quality on a certain level: webstandards, accessibility, website-speed, stability, durability, focus!
Teams, working together and daily communication. No big plans, but ITERATION.
Learn and adapt!
all disciplines involved!
human interaction over technology and huge projectplans
not impose techniques but coaching teams and facilitating
include User Centred Design
include (usability) testing
include automatic testing
include continuous integration
Productowner: quality assurance, keeping the quality on a certain level: webstandards, accessibility, website-speed, stability, durability, focus!
Teams, working together and daily communication. No big plans, but ITERATION.
Learn and adapt!
all disciplines involved!
human interaction over technology and huge projectplans
not impose techniques but coaching teams and facilitating
include User Centred Design
include (usability) testing
include automatic testing
include continuous integration