Please enable JavaScript.
Coggle requires JavaScript to display documents.
Coding for non Dev AKA Coding for C-Suite (Sense and respond (continuous…
Coding for non Dev AKA Coding for C-Suite
From Lean to Agile
From Waterfall to Lean
1994: the CHAOS report by The Standish Group
84% of IT projects
or are impaired by cost and schedule overruns
failed to delivery any result
Decision-making contexts
Cynefin framework
Complex vs. Complicated
Agile Manifesto
Time Management
Scrum
Scrum LEGO City :game_die:
Sprint planning
Sprint Review & Retrospective
Daily Scrum
User Stories
Estimates, story points
Artifacts
PO's product backlog
Team sprint backlog
Burndown chart
Kanban
Dot game :game_die:
Kanban board
WIP limit
:game_die:
name/numbers game
Bruno Munari: design as "progettazione" step by step
Nassim Taleb
Antifragile
The Black Swan
Sense and respond
create two-way conversations with our markets and customers
markets = people
focus on the outcomes
it is difficult/impossible to predict which product features are need
try approaches
experiment
learn
discover
embrace continuous change and continuous processes
create collaboration
create a learning culture
continuous uncertainty
the end of assembly line management
ford assembly line
first softwares: Lotus 1-2-3 in box
escape the manifacturing mindset: the process of copying software onto floppy or CD/DVD is no longer part of the software distribution process
removing this ONE step, we enabled a lot of new models
benefits
delivering services
reducing risks
optimizing for value
recognizing emergent value
adapting to a complex context
Harward Business Review: David Snowden and Mary E. Boone: complex adaptive systems
self directed teams
run e.t. an auto company like a software company
Tesla auto updates cars
building hardware products as they're software
Xiaomi releases small batches of products to collect feedback and improve
continuous learning
priorityzing learning over delivery
questions instead of plans
the unit of progress is moving from question to question
allow the team to make mistakes
provide freedom to the team to make their own decisions
placed value on customer behavior is the measure of progress
the value is defined by
users
customers
market
the new definition of "DONE"
could not be the "launch" of a product
your goal is not creating an output, but an outcome
cool vs valuable: Amazon's 2014 Fire Phone
testing assumptions
forming hypotheses
the usage of big data reduces risk
What is value?
:film_frames: Start with why
Waste in processes is not customer value
Value is subjective
Lean User Research
:blue_book: Tomer Sharon: Lean User Research
Customer needs for a specific product
Emphaty Map
Customer Journey Map
User Centered Design
Value metrics
Value stream map
Validated knowledge
:blue_book: Jeff Gothelf: Lean UX
IDEAS-BUILD-PRODUCT-MEASURE-DATA-LEARN
Value added
The customer is willing to pay for this activity
It must be done right the first time
The action must somehow change the product or service in some manner
No value added
No value added but necessary