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
880
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
300
Jukes - User Manual
jukesie
0
120
my adidas
jukesie
1
370
This is a team sport
jukesie
0
370
Working in the open works
jukesie
1
67
Digital is a team sport
jukesie
0
560
The importance of being open
jukesie
1
85
The Wrong Users?
jukesie
0
550
Other Decks in Technology
See All in Technology
The Rise of LLMOps
asei
9
1.8k
Exadata Database Service on Dedicated Infrastructure(ExaDB-D) UI スクリーン・キャプチャ集
oracle4engineer
PRO
2
3.2k
【Startup CTO of the Year 2024 / Audience Award】アセンド取締役CTO 丹羽健
niwatakeru
0
1.4k
飲食店データの分析事例とそれを支えるデータ基盤
kimujun
0
220
Amazon CloudWatch Network Monitor のススメ
yuki_ink
1
210
強いチームと開発生産性
onk
PRO
36
12k
SDNという名のデータプレーンプログラミングの歴史
ebiken
PRO
2
160
DynamoDB でスロットリングが発生したとき_大盛りver/when_throttling_occurs_in_dynamodb_long
emiki
1
460
B2B SaaSから見た最近のC#/.NETの進化
sansantech
PRO
0
960
SSMRunbook作成の勘所_20241120
koichiotomo
3
180
Terraform Stacks入門 #HashiTalks
msato
0
360
組織成長を加速させるオンボーディングの取り組み
sudoakiy
2
260
Featured
See All Featured
The Illustrated Children's Guide to Kubernetes
chrisshort
48
48k
The World Runs on Bad Software
bkeepers
PRO
65
11k
For a Future-Friendly Web
brad_frost
175
9.4k
Six Lessons from altMBA
skipperchong
27
3.5k
Raft: Consensus for Rubyists
vanstee
136
6.6k
Designing for humans not robots
tammielis
250
25k
Building Better People: How to give real-time feedback that sticks.
wjessup
364
19k
What's new in Ruby 2.0
geeforr
343
31k
It's Worth the Effort
3n
183
27k
Building Your Own Lightsaber
phodgson
103
6.1k
How to train your dragon (web standard)
notwaldorf
88
5.7k
Designing for Performance
lara
604
68k
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