1. Use post-its to map your process on your current project out, thinking about the stages you go through
2. If time, add in any tools, techniques and practices against each stage BRIEF: OUTCOME: You will have mapped out your current process, plus ways of working
CUSTOMER FIRST Prioritise the customer and the outcomes they will value Value getting working designs, prototypes or software to the customer over defining requirements upfront Feedback and iterate
Key to making your project work and building a better product Don’t rely on documentation to define requirements and share knowledge Face to face communication and shared decisions The team is your client too! TEAM COLLABORATION
REQUIRE- MENTS DEFINE UX DESIGN LAUNCH WIRE FRAMES KICK OFF MEETING DEV DAILY STAND UPS QA BUSINESS NEEDS USER NEEDS BACKLOG STATIC DESIGNS CLIENT DEMOS SPRINTS TDD RETRO- SPECTIVES LACK OF DESIGN TIME NO USER TESTING NOT WHOLE TEAM NO SPRINT RELEASES
“We have come to realise that bespoke software delivery is far more akin to product design and development than it is to project delivery.” John Yorke, 2017
E X I S T I N G D A T A & R E S E A R C H I N S I G H T S A S S U M P T I O N S F U R T H E R R E S E A R C H H Y P O T H E S E S STAGE 1 I D E N T I F Y P A I N P O I N T S I D E N T I F Y O P P O R T U N I T I E S
Gather requirements Review data & research Think in terms of deliverables Identify customer pain points Develop features Develop assumptions & hypotheses Build & launch Design & prototype Test after dev Test & learn before dev Product Project
1. Thinking about product over project process, where are the opportunities to improve in your projects?
2. Fill in the second column of the canvas with a couple of hypotheses BRIEF: OUTCOME: You will identify what the opportunities in your project process are
Pain points (Principles) Opportunities (Processes) Actions (Practices) Customer first: • No user testing until we’ve launched the product
• Lack of design time means we’re focusing on tech defining the product
Frequent delivery: • Despite working in Sprints, we aren’t releasing frequently
Team collaboration: • We don’t have the entire team involved from the start of the project Customer first: • I believe that testing designs on customers
• For my whole team
• Will help us define the correct solution before we start build and help eliminate waste
Frequent delivery: • I believe that reviewing the release process and uncovering blockers
• For my developers
• Will help us to release more frequently #AdaptingAgile @suzehaworth
suzehaworth
1000ch
hmatsu47
soudai
konifar
ewolff
torounit
lapis2411
tatsuru
_kensh
shinnosuke_kishida
irotoris
autifyhq
pauljervisheath
mza
colly
addyosmani
edds
sonatard
jennybc
tanoku
aarron
shpigford
lara
mclloyd