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

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Scrum feb 3rd - manoj vadakan - cosncires agile practices

544

Published on

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.

Published in: Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
544
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
9
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Over following a plan
  • Over comprehensive documentation
  • Transcript

    • 1. 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
    • 2. Conscires Agile Practices
      Who we are ::
      • Enabler of Agile & Scrum adoption for your organization
      • 3. Agile Adoption Assessment, Training & Coaching
      What we do ::
      • Agile & Scrum Coaching – http://agile.conscires.com/services/
      • 4. Agile & Scrum Trainings - http://bit.ly/allTrainings
      • 5. Boston,MA
      • 6. Irvine,CA
      • 7. San Diego,CA
      • 8. 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
    • 9. Agenda
      Why Agile?
      What is In In It For Me?
      What is Scrum?
      4
    • 10. About your facilitator
      5
    • 11. Certifications
      6
    • 12. Organizations consulted with
      7
    • 13. Currently with
      8
    • 14. Previous Speaking Engagements
      9
    • 15. Iterative Vs. Agile
      10
    • 16. Homework Problem
      11
      http://alistair.cockburn.us/Are+iterations+hazardous+to+your+project%3F
    • 17. 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
    • 18. Homework Problem
      13
    • 19. Homework Problem
      14
    • 20. Homework ProblemThe plan
      Read two book every day (M-F)
      Spend Saturday to answer questions
      Submit answers on Monday
      15
    • 21. 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
    • 22. 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
    • 23. 18
      Agile
    • 24. Agile Manifestowww.agilemanifesto.org
      19
    • 25. 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.
    • 26. Responding to Change
      21
    • 27. Working Software
      22
    • 28. Working Software
      Track Record
      23
    • 29. The Plan Driven development: The Plan
      24
    • 30. The Plan Driven developmentThe Plan
      25
    • 31. The Plan Driven development: The Plan
      26
      Analysis
    • 32. The Plan Driven development: The Plan
      27
      Analysis
      Design
    • 33. The Plan Driven development: The Plan
      28
      Analysis
      Design
      Code
    • 34. The Plan Driven development: The Plan
      29
      Analysis
      Design
      Code
      Test
    • 35. The Plan Driven developmentOct Target date
      30
    • 36. Reality?
      31
    • 37. The Plan Driven development: Reality
      32
      Analysis
      Design
      Code
      Test
    • 38. The Plan Driven development: Reality
      33
      Analysis
      Design
      Code
      Test
    • 39. The Plan Driven development: Reality
      34
      Analysis
      Design
      Code
      Test
    • 40. The Plan Driven development: Reality
      35
    • 41. The Plan Driven developmentNew Date
      36
    • 42. The Plan Driven developmentsystem testing
      37
    • 43. bugs
      38
    • 44. The Plan Driven developmentProduction Release
      39
    • 45. The Plan Driven developmentProduction Release
      delivered in March
      40
    • 46. The Plan Driven developmentProduction Release
      5 Months late
      41
    • 47. The Plan Driven development: Prod. Release
      no new business value for 15 months
      42
    • 48. Trust?
      43
    • 49. How do we build the Trust?
      44
    • 50. What if we deliver
      working Software
      with business value from the first week/month
      45
    • 51. What if we deliver
      working Software
      Frequently
      46
    • 52. 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.
    • 53. Agile is not an Excuse for
      We don’t need to plan anything
      We don’t need to document anything
      48
    • 54. Lazy Agile
      49
    • 55. 50
      Why Agile?
    • 56. What Challenge do you have?
      What challenges do you have in your environment?
      51
    • 57. 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?
    • 58. 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?
    • 59. Applying the Pareto Principle
    • 60. Reasons for Project Failure
      55
      Extracted from CHAOS Report : The Standish Group 1995
    • 61. 56
      Reasons for Project Success
      Extracted from CHAOS Report : The Standish Group 1995
    • 62. 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
    • 63. 58
      Scrum A quick Introduction Scrum
    • 64. Scrum
      A process framework for managing product development
      Not a methodology
      59
    • 65. 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
    • 66. 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.
    • 67. Scrum
      62
    • 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
    • 84. What is your action item?
      What are you going to differently?
      What two action items do you have?
      64
    • 85. Upcoming Trainings in Boston,MA
      • “What is Scrum” by Manoj Vadakan on Feb 19th 2011
      • 86. Certified ScrumMaster Training by Alan Cyment on April 7th – 8th 2011
      20% discount with code Webinar0122
      • Contact
      • 87. Bachan Anand
      • 88. W : http://agile.conscires.com
      • 89. E : bachan.anand@conscires.com
      • 90. P : 949-232-8900
    • Thank you !
      Work is GOOD !
      http://work-is-good.com

    ×