know how: digital thinking
TRANSCRIPT
DIGITAL THINKING
#knowhow15@nearnow | @broadwaycinema
AGILE
#knowhow15@nearnow | @broadwaycinema
#knowhow15@nearnow | @broadwaycinema
#knowhow15@nearnow | @broadwaycinema
#knowhow15@nearnow | @broadwaycinema
#knowhow15@nearnow | @broadwaycinema
#knowhow15@nearnow | @broadwaycinema
#knowhow15@nearnow | @broadwaycinema
#knowhow15@nearnow | @broadwaycinema
ROLES
Product Owner
Responsible for the overall vision of the product / project. They
work with the development team & scrum manager to define the
vision & the core features.
Scrum Master
Think of this person as a process facilitator, they do not have
any authority within the team. Responsible for translating the
vision between the product owner & team. Their core role is
removing any barriers to the development team working.
Development Team
The development team is comprised of a mixture of skills and
work through features of the vision, delivering them
incrementally.
#knowhow15@nearnow | @broadwaycinema
WHAT DOES A DEVELOPMENT TEAM LOOK LIKE?
#knowhow15
Developers Designers
Backend
DeveloperEngineer
UI
DesignerService Layer &
Clear Signage
Frontend
DeveloperArchitect
UX
Designer
Interior Design,
what is the quality
of the space?
Fullstack
DeveloperEngineer &
Architect
Digital
Designer
Like the full stack
developer, Mix of
Experience
Mobile
DeveloperTransport Designer
Interaction
Designer
Improve
engagement with
the space
Hackers & Creative Technologists
@nearnow | @broadwaycinema
#knowhow15
USER STORY CARDS
@nearnow | @broadwaycinema
#knowhow15
USER STORY CARDS
A method for defining features & user needs:
> the person using the service (actor)
> what the user needs the service for (narrative)
this describes the person’s main interaction
> why the user needs it (goal)
@nearnow | @broadwaycinema
#knowhow15
TITLE
As an / a [the actor] I want to
[what is their narrative] so
that I can [what is the goal].
@nearnow | @broadwaycinema
#knowhow15@nearnow | @broadwaycinema
MoSCoW
#knowhow15@nearnow | @broadwaycinema
M MUST
Describes a requirement that must be
satisfied in the final solution for the
solution to be considered a success.
S SHOULD
Represents a high-priority item that
should be included in the solution if it is
possible. This is often a critical
requirement but one which can be
satisfied in other ways if strictly
necessary.
C COULD
Describes a requirement which is
considered desirable but not necessary.
This will be included if time and
resources permit.
W WOULD
Represents a requirement that
stakeholders have agreed will not be
implemented in a given release, but may
be considered for the future.
#knowhow15@nearnow | @broadwaycinema
Show me the Money Mobile
Banking App - Features Spec
MUST have a secure login system.
MUST allow customers to check their balance.
SHOULD allow customer to move money between their
accounts.
SHOULD allow them to pay bills or edit direct debits in
app.
COULD allow them to set savings targets and track their
progress.
WOULD allow them to attach photos to transactions with
their friends to say thanks for buying me that coffee.
#knowhow15@nearnow | @broadwaycinema
KANBAN
#knowhow15@nearnow | @broadwaycinema
High
Priority
Low
Priority
TO DO DOING DONETEST / REVIEW
/ SHIP
Your list of to do
items for the
sprint or working
block.
As you work
through the things
you take one item
from the to do list
and put it in the
Doing Bin, limiting
the work you are
doing at any one
time.
Once it’s done, it
goes in the Done
Bin.
This is an optional
Bin. Think of it as
a holding bay for
review before you
put out your work
in front of its
audience. If it is
not complete, To
Do items are
added back into
the first bin until it
is complete
#knowhow15@nearnow | @broadwaycinema
#knowhow15
WHAT DOES THIS ALL LOOK LIKE IN
PRACTICE?
@nearnow | @broadwaycinema
#knowhow15
+
@nearnow | @broadwaycinema
#knowhow15
THIS IS BORING SHOW US SOME
COOL TECH STUFF!
@nearnow | @broadwaycinema
# k n o w h o w 1 4#knowhow15
Mathew Trivett
Producer, Near Now
Broadway
@mathewtrivett