Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
ProductONSers
Search
Matt Jukes
May 24, 2016
Technology
0
920
ProductONSers
Notes for ONS product owners
Matt Jukes
May 24, 2016
Tweet
Share
More Decks by Matt Jukes
See All by Matt Jukes
Roadmaps and Missions for the Scottish Digital Academy
jukesie
0
1.2k
A ChatGTP Christmas Quiz
jukesie
0
350
Jukes - User Manual
jukesie
0
140
my adidas
jukesie
1
400
This is a team sport
jukesie
0
450
Working in the open works
jukesie
1
70
Digital is a team sport
jukesie
0
600
The importance of being open
jukesie
1
86
The Wrong Users?
jukesie
0
590
Other Decks in Technology
See All in Technology
ガチな登山用デバイスからこんにちは
halka
1
240
allow_retry と Arel.sql / allow_retry and Arel.sql
euglena1215
1
160
フィンテック養成勉強会#56
finengine
0
140
CDK CLIで使ってたあの機能、CDK Toolkit Libraryではどうやるの?
smt7174
4
120
サンドボックス技術でAI利活用を促進する
koh_naga
0
200
AWSで始める実践Dagster入門
kitagawaz
1
590
COVESA VSSによる車両データモデルの標準化とAWS IoT FleetWiseの活用
osawa
1
260
Agile PBL at New Grads Trainings
kawaguti
PRO
1
390
下手な強制、ダメ!絶対! 「ガードレール」を「檻」にさせない"ガバナンス"の取り方とは?
tsukaman
2
420
Language Update: Java
skrb
2
290
DDD集約とサービスコンテキスト境界との関係性
pandayumi
3
280
なぜSaaSがMCPサーバーをサービス提供するのか?
sansantech
PRO
8
2.7k
Featured
See All Featured
The Invisible Side of Design
smashingmag
301
51k
Designing Experiences People Love
moore
142
24k
ピンチをチャンスに:未来をつくるプロダクトロードマップ #pmconf2020
aki_iinuma
126
53k
個人開発の失敗を避けるイケてる考え方 / tips for indie hackers
panda_program
111
20k
Dealing with People You Can't Stand - Big Design 2015
cassininazir
367
27k
It's Worth the Effort
3n
187
28k
Rails Girls Zürich Keynote
gr2m
95
14k
CSS Pre-Processors: Stylus, Less & Sass
bermonpainter
358
30k
How To Stay Up To Date on Web Technology
chriscoyier
790
250k
Art, The Web, and Tiny UX
lynnandtonic
302
21k
The World Runs on Bad Software
bkeepers
PRO
70
11k
Building an army of robots
kneath
306
46k
Transcript
Being a Product Owner at the ONS. Beyond the job
description.
None
1.User Experience (UX) 2.Business 3.Technology 4.Team
1.User Experience (UX)
1.User Experience (UX) Learn how to undertake user research and
how to integrate it in to your decision making and prioritisation.
1.User Experience (UX) You are the voice of the user
in the product team so you will need to steer the priorities for the user researchers.
1.User Experience (UX) Observe as much user research as possible.
Ensure your team does this as well. Two hours every six weeks is target.
1.User Experience (UX) Read: https://userresearch.blog.gov.uk/2015/03/18/so-youre-going-to- be-a-user-researcher-top-tips-to-get-you-going/ https://www.gov.uk/service-manual/the-team/user-researcher http://www.disambiguity.com/guerrilla-empathy/
https://www.nngroup.com/articles/usability-101-introduction- to-usability/
1.User Experience (UX) Learn how to sketch ideas and use
basic prototyping tools to help the team visualise concepts.
1.User Experience (UX) Read: https://library.gv.com/the-product-design-sprint-diverge-day-2- c7a5df8e7cd0#.wneifj8h5 http://www.almostexact.com/ux-comics/ http://chrismcgrath.com/blog/keynote-is-best-app-prototyping-
tool https://library.gv.com/the-product-design-sprint-prototype- day-4-ebab764ac69f#.swf2wrufy
1.User Experience (UX) Be aware of the ‘visual language’ of
the ONS. You aren’t a designer but you will make design decisions.
1.User Experience (UX) Read: http://onsdigital.github.io/ons-pattern-library-starter/ http://www.bbc.co.uk/gel/articles/what-is-gel https://boagworld.com/design/pattern-library/
2.Business
2. Business Bring an understanding of the business process to
the team and a first hand knowledge of the user journey.
2. Business Bring a first hand understanding of the business
process to the team and knowledge of the user journey.
2. Business Understand the organisational environment. Who are the decision
makers, the stakeholders & the related teams.
2. Business Be the voice/face of the team internally. Make
sure there is sufficient communications activity. Too much is better than not enough.
2. Business Read: https://fitzdigital.wordpress.com/2015/09/21/showing-telling- plus-listening-collaborating-to-deliver/ https://gdsengagement.blog.gov.uk/2016/05/18/blog-like- there-arent-any-rules/ http://russelldavies.typepad.com/planning/2015/11/doing-
presentations.html https://medium.com/@jukesie/words-and- slides-2b2a8584e0f4#.ff5ucgif8
3.Technology
3. Technology Learn enough about the technology used in your
product that you can understand the high-level choices & trade-offs at a high level.
3. Technology Learn about version control (Git), collaborative programming (GitHub)
and at a high level how and when code gets deployed to users in your product.
3. Technology Read: http://mcfunley.com/choose-boring-technology https://blog.ons.digital/2016/01/20/technicalities-of-the-eq- alpha-outcomes-part-3/ https://guides.github.com/activities/hello-world/ https://18f.gsa.gov/2015/03/03/how-to-use-github-and-the- terminal-a-guide/ http://continuousdelivery.com/
4.Team
4. Team The Delivery Manager will make sure things get
done but you must decide what gets done and when.
4. Team You are responsible for articulating the product vision
and making certain your team works towards that goal.
4. Team Work collaboratively but the backlog is your
responsibility. Always prioritise with the user and the vision in mind.
4. Team Work with the Service Manager (or equivalent) to
produce a product roadmap. This is part planning artefact, part communication. Own it.
4. Team Make sure retrospectives happen regularly. If possible
invite Product Owners from other teams to facilitate.
4. Team Read: http://www.jamiearnold.com/blog/2014/07/07/everyone-loves- a-roadmap http://www.jamiearnold.com/blog/2015/02/17/how-to-scale- agile-service-delivery http://digital.nhs.uk/how-the-nhs-uk-team-does-agile https://www.gov.uk/service-manual/agile-delivery/agile-tools- techniques
http://www.scrumguides.org/scrum-guide.html#artifacts- productbacklog
You
Thanks. @jukesie