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
900
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.1k
A ChatGTP Christmas Quiz
jukesie
0
330
Jukes - User Manual
jukesie
0
120
my adidas
jukesie
1
380
This is a team sport
jukesie
0
400
Working in the open works
jukesie
1
67
Digital is a team sport
jukesie
0
570
The importance of being open
jukesie
1
86
The Wrong Users?
jukesie
0
570
Other Decks in Technology
See All in Technology
関東Kaggler会LT: 人狼コンペとLLM量子化について
nejumi
3
460
日経電子版 x AIエージェントの可能性とAgentic RAGによって提案書生成を行う技術
masahiro_nishimi
1
290
「海外登壇」という 選択肢を与えるために 〜Gophers EX
logica0419
0
500
スタートアップ1人目QAエンジニアが QAチームを立ち上げ、“個”からチーム、 そして“組織”に成長するまで / How to set up QA team at reiwatravel
mii3king
1
1.1k
MC906491 を見据えた Microsoft Entra Connect アップグレード対応
tamaiyutaro
1
480
データの品質が低いと何が困るのか
kzykmyzw
6
1k
事業継続を支える自動テストの考え方
tsuemura
0
300
RSNA2024振り返り
nanachi
0
500
Ask! NIKKEI RAG検索技術の深層
hotchpotch
13
2.8k
プロセス改善による品質向上事例
tomasagi
1
1.6k
ハッキングの世界に迫る~攻撃者の思考で考えるセキュリティ~
nomizone
12
4.5k
株式会社EventHub・エンジニア採用資料
eventhub
0
4.2k
Featured
See All Featured
Why Our Code Smells
bkeepers
PRO
335
57k
The Myth of the Modular Monolith - Day 2 Keynote - Rails World 2024
eileencodes
20
2.4k
Let's Do A Bunch of Simple Stuff to Make Websites Faster
chriscoyier
507
140k
Become a Pro
speakerdeck
PRO
26
5.1k
Principles of Awesome APIs and How to Build Them.
keavy
126
17k
Side Projects
sachag
452
42k
Building Flexible Design Systems
yeseniaperezcruz
328
38k
Building a Scalable Design System with Sketch
lauravandoore
460
33k
Testing 201, or: Great Expectations
jmmastey
41
7.2k
10 Git Anti Patterns You Should be Aware of
lemiorhan
PRO
656
59k
ピンチをチャンスに:未来をつくるプロダクトロードマップ #pmconf2020
aki_iinuma
114
50k
Templates, Plugins, & Blocks: Oh My! Creating the theme that thinks of everything
marktimemedia
29
2.2k
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