Scrum   feb 3rd  - manoj vadakan -  cosncires agile practices
Upcoming SlideShare
Loading in...5
×
 

Scrum feb 3rd - manoj vadakan - cosncires agile practices

on

  • 821 views

Agile , What is in it for me Webinar by Manoj and Conscires Agile Practices . An Introduction to Scrum and Agile.

Agile , What is in it for me Webinar by Manoj and Conscires Agile Practices . An Introduction to Scrum and Agile.

Statistics

Views

Total Views
821
Views on SlideShare
818
Embed Views
3

Actions

Likes
0
Downloads
9
Comments
0

1 Embed 3

http://agile.conscires.com 3

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Over following a plan
  • Over comprehensive documentation

Scrum   feb 3rd  - manoj vadakan -  cosncires agile practices Scrum feb 3rd - manoj vadakan - cosncires agile practices Presentation Transcript

  • Going Agile? What is in it for me?
    Hosted By
    Manoj Vadakkan
    Bachan Anand
    Conscires Agile Practices
    agile@conscires.com
    Manoj Vadakkan
    manoj@vadakkan.org
  • Conscires Agile Practices
    Who we are ::
    • Enabler of Agile & Scrum adoption for your organization
    • Agile Adoption Assessment, Training & Coaching
    What we do ::
    • Agile & Scrum Coaching – http://agile.conscires.com/services/
    • Agile & Scrum Trainings - http://bit.ly/allTrainings
    • Boston,MA
    • Irvine,CA
    • San Diego,CA
    • Phoenix, AZ
  • Your experience with Agile
    I don’t know what Agile is
    Understand the values of Agile
    Started using Agile but have Challenges
    I am sailing smooth on my Agile boat
    3
  • Agenda
    Why Agile?
    What is In In It For Me?
    What is Scrum?
    4
  • About your facilitator
    5
  • Certifications
    6
  • Organizations consulted with
    7
  • Currently with
    8
  • Previous Speaking Engagements
    9
  • Iterative Vs. Agile
    10
  • Homework Problem
    11
    http://alistair.cockburn.us/Are+iterations+hazardous+to+your+project%3F
  • The Homework ProblemIterative vs. Agile
    A School homework assignment
    Read 10 books answer 20 questions
    Submit answers by Following Monday (1 week to complete the assignment)
    12
    http://alistair.cockburn.us/Are+iterations+hazardous+to+your+project%3F
    http://www.scrumalliance.org/articles/134-iterative-vs-agile
  • Homework Problem
    13
  • Homework Problem
    14
  • Homework ProblemThe plan
    Read two book every day (M-F)
    Spend Saturday to answer questions
    Submit answers on Monday
    15
  • Homework ProblemWhat Really Happened
    Student read books as per plan.
    Status on Friday - Green
    Started looking at questions on Saturday to realize that books need to be read again for the most part
    Status on Saturday - Red
    16
  • What is the point?
    How the student should have measured his progress?
    Number of Books read?
    Number of Questions answered?
    How do you measure progress in your projects?
    17
  • 18
    Agile
  • Agile Manifestowww.agilemanifesto.org
    19
  • Agile Manifestowww.agilemanifesto.org
    20
    That is, while there is value in the items on the right,
    we value the items on the left more.
  • Responding to Change
    21
  • Working Software
    22
  • Working Software
    Track Record
    23
  • The Plan Driven development: The Plan
    24
  • The Plan Driven developmentThe Plan
    25
  • The Plan Driven development: The Plan
    26
    Analysis
  • The Plan Driven development: The Plan
    27
    Analysis
    Design
  • The Plan Driven development: The Plan
    28
    Analysis
    Design
    Code
  • The Plan Driven development: The Plan
    29
    Analysis
    Design
    Code
    Test
  • The Plan Driven developmentOct Target date
    30
  • Reality?
    31
  • The Plan Driven development: Reality
    32
    Analysis
    Design
    Code
    Test
  • The Plan Driven development: Reality
    33
    Analysis
    Design
    Code
    Test
  • The Plan Driven development: Reality
    34
    Analysis
    Design
    Code
    Test
  • The Plan Driven development: Reality
    35
  • The Plan Driven developmentNew Date
    36
  • The Plan Driven developmentsystem testing
    37
  • bugs
    38
  • The Plan Driven developmentProduction Release
    39
  • The Plan Driven developmentProduction Release
    delivered in March
    40
  • The Plan Driven developmentProduction Release
    5 Months late
    41
  • The Plan Driven development: Prod. Release
    no new business value for 15 months
    42
  • Trust?
    43
  • How do we build the Trust?
    44
  • What if we deliver
    working Software
    with business value from the first week/month
    45
  • What if we deliver
    working Software
    Frequently
    46
  • Agile Manifestowww.agilemanifesto.org
    47
    That is, while there is value in the items on the right,
    we value the items on the left more.
  • Agile is not an Excuse for
    We don’t need to plan anything
    We don’t need to document anything
    48
  • Lazy Agile
    49
  • 50
    Why Agile?
  • What Challenge do you have?
    What challenges do you have in your environment?
    51
  • Why Agile?
    We may have better process efficiency than we ever had before.
    How do we improve now?
    Is the budget/schedule getting shorter?
    How about value delivered & Time to Market?
  • Business Value
    Is prioritization an afterthought?
    When/who prioritize features?
    Late? may be when we are really sure we can not do it all within the time?
  • Applying the Pareto Principle
  • Reasons for Project Failure
    55
    Extracted from CHAOS Report : The Standish Group 1995
  • 56
    Reasons for Project Success
    Extracted from CHAOS Report : The Standish Group 1995
  • What is in it for me?
    As a customer , I want to be able to
    Go to market faster
    Faster return on investment
    Opportunity to provide feedback early
    As a Project Manager/Leadership, I want
    To measure progress in terms of real progress made on product .
    Better engaged and accountable   team 
    As a team member, I want
    A sustainable pace
    Satisfaction of quality product delivered
    Clear Priority and less interruption during development
    57
  • 58
    Scrum A quick Introduction Scrum
  • Scrum
    A process framework for managing product development
    Not a methodology
    59
  • Agile Product Development
    Product Owner with Stakeholders/PMO
    Multiple sprints usually build up a release
    Product Backlog
    Production Release
    Feedback from Sprint
    Reviews
    Discovery Period
    Feedback from Releases
    Sprint = Iteration
    Product Owner with Stakeholders/PMO
    During the Discovery Period, the product team identify the features, prioritize the features, and identify a roadmap for the product. The roadmap will identify the release milestones into production and the features contained in each releases at a high-level.
    Each Sprint deliver (for a subset of Product Backlog) running tested features potentially shippable that the team can demonstrate to the customer to get feedback
  • Agile Product Development: Sprints
    Initial Analysis for
    the sprint backlog
    The team creates working software for the features selected for the Sprint including all the necessary Documentation
    Acceptance Criteria
    Defined for Sprint
    Sprint Backlog
    Product Backlog
    Sprint Demo
    Potentially shippable product
    Sprint Task List
    Sprint
    Product Owner with Stakeholders/PMO
    Sprints are of the consistent, fixed length for a project, usually 1 week to 4 weeks.
    With the help of the Product Owner, the team selects a set of features from the top of the prioritized product backlog.
    Team Spends 2 to 4 hours on the first day of the sprint to break down the features to detail tasks (technical, testing, documentation, etc) and estimate hours needed to complete them.
    Within the sprint the team deliver Running Tested Features along with all the documentation for the selected features.
    The product from the sprint is demonstrated to the customer to get feedback.
  • Scrum
    62
    • Roles
    • Product owner
    • Scrum Master
    • Team
    • Ceremonies
    • Daily Scrum
    • Sprint Planning
    • Sprint Review-Demo
    • Retrospective
    • Artifacts
    • Product Backlog
    • Sprint Backlog
    • Planning
    • Release plan
    • Progress Tracking
    • Velocity
    • Burn down Chart
  • What is in it for me?
    As a customer , I want to be able to
    Go to market faster
    Faster return on investment
    Opportunity to provide feedback early
    As a Project Manager/Leadership, I want
    To measure progress in terms of real progress made on product .
    Better engaged and accountable   team 
    As a team member, I want
    A sustainable pace
    Satisfaction of quality product delivered
    Clear Priority and less interruption during development
    63
  • What is your action item?
    What are you going to differently?
    What two action items do you have?
    64
  • Upcoming Trainings in Boston,MA
    • “What is Scrum” by Manoj Vadakan on Feb 19th 2011
    • Certified ScrumMaster Training by Alan Cyment on April 7th – 8th 2011
    20% discount with code Webinar0122
    • Contact
    • Bachan Anand
    • W : http://agile.conscires.com
    • E : bachan.anand@conscires.com
    • P : 949-232-8900
  • Thank you !
    Work is GOOD !
    http://work-is-good.com