Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Super Lean Agile Project Startup for Students

Presentation to NUVention Web course, February 2012
by

Chris Riesbeck

on 13 January 2012

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Super Lean Agile Project Startup for Students

Maximum progress,
minimum waste

Continuous delivery of
maximum value

Crystal clear
product vision

Very small
highly focused
MVP
Features cost. More features in product
harder to use
harder to see value proposition
harder to maintain (5x features = 25x maintenance)
Delivery = tested and deployed
Tested = passes all automated tests
The best way to test code is with other code
Types of test
Acceptance tests
System tests
Functional tests
Integration tests
Unit tests
Value = a new user story

a user can now do something a user wants to do
No story, no value

Things with no value to the user
meetings
design sketches
development platforms
test code (!)
iteration = a fixed length timebox
Minimize the time through the build-measure-learn loop
Anything not done goes back to the release backlog
Iterations help
planning
tracking progress
measuring velocity
periodic reflection
rescoping
Velocity = story points done per iteration
Assume there's no tomorrow
If this was your last iteration, if this is all the user is going to get, what would you be sorry never got built?

Build that.
Deployed = code is running in a version of the app available on a server accessible to the entire team and pilot users.
Developer's laptop
Source control repository
Beta site
Public site
Continuous integration (CI) server
watches for changes to source
re-builds app
re-runs all tests
if failure, emails developers
else installs new version on Beta site
User scenario:
A complete narrative
From initiating circumstances to final success
Including context of use
If you have a working scenario, you have a demo.
If you have enough working scenarios, you have a product.
A [type of user] can [do something with product] in order to [achieve a user goal].
Backlog = a collection of user stories
Iteration backlog: stories for this iteration
Release backlog: stories for the next product release
Scenario backlog: stories needed to have a working scenario
Continuous = value delivered every few days
Points = relative estimate of story size and complexity


Done = tested and deployed
huh?
why?
huh?
how?
huh?
how?
huh?
huh?
how?
huh?
huh?
why?
huh?
why?
huh?
how?
huh?
how?
why?
how?
huh?
huh?
huh?
huh?
Full transcript