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

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Basics of Agile Product Development

No description
by

Anar Joshi

on 28 September 2013

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Basics of Agile Product Development

Product Development
Basics of Agile Development
What is Product Development?
What exactly is Agile Development?
How can I use it?
What is this important?
Questions?
But first... Who am I?
What is Product Development?
Questions?
@anarjoshi
Currently:
Mentoring start-ups @StartUp Chile and @Exosphere

Previously:
Product Manager @ PayPal
Social Media Strategist @BBDO
Consultant @OCC Strategy
Engineer @ University of California, Berkeley
Product development is creation of products with new or different characteristics
Waterfall Development
Phased Development – the model is that the software progresses through a well-defined series of phases
Phase Review – each phase ends with a review of the deliverables from that phase
Pros: Perceived predictability
Cons: Validation comes at the end of the process; Changes are costly and disruptive; High overhead
Agile Development
Validate ideas the fastest and cheapest way possible with a focus on the customer
Build and release product in small batches
Requirements will change and the process allows for that
Intense collaboration across disciplines; Good ideas come from anywhere
Reflect, as a team, on what is working and what's not working
An example from Lean Startup...
What's the most efficient way to stuff and seal letters in an envelope?

Image: "The Lean Startup - Tokyo Edition", Eric Ries, slideshare.net
Image: "The Lean Startup - Tokyo Edition", Eric Ries, slideshare.net
What exactly is Agile Development?
Customer development is a iterative process composed of four main areas:
Customer Development
Customer Discovery
Customer Validation
Customer Creation
Scale Company
Product Development
Product development, when done right, can minimize time through the feedback loop to help validate ideas and launch!
The Goal
How can I use it?
Key things to keep in mind:
Having a clear MVP and prioritized backlog is crucial
Be realistic during sprint planning - take on only what you can accomplish
Have a process to manage and track bugs vs. new features through a sprint
Do a retro at the end of every sprint!
www.linkedin.com/in/anarjoshi/
Example: Facebook Photos
Imagine before Facebook bought Instagram, they were working on a copycat product themselves to amp up their offering by building features like filters into the Facebook photo product...
Planning
Current Sprint
The current sprint is where the product comes to life with the goal of pushing out a working set of code at the end of it

Current sprint board has:
Next up: Prioritized user stories that are ready to be picked up in a sprint
In progress: User stories that dev is currently working on
QA: User stories that dev has completed and need to be tested
Live: User stories that are live (week by week)
User Story
User Story: Document customer's requirement of a product and written from a customer's point of view.

Feature: View picture with selected filter


User Story: As a user I want to be able to view the picture I uploaded with the filter I selected applied to it so I know what it will look like.
Before a team can get ready for a sprint, the team has to groom the backlog and see what is ready for them to work on

Planning board has:
Next - What user stories are in the product backlog
Product - What user stories are being worked through with product for requirements
Design - What user stories the design team is working on
Ready - What user stories are complete for the team to handoff to dev
Why is this important?
Without a product development "process", teams are not able to:
Understand progress and problems with the way they work
Predict how long things will take to complete with current resources
Work through product priorities
Launch product and get feedback


Tools you can use
Trello (used in the example above)
Rally
Asana
Google Drive
Basecamp
Full transcript