• Save
Agile Coaching By Manish Manekar - Introduction to Agile/Scrum.
Upcoming SlideShare
Loading in...5

Agile Coaching By Manish Manekar - Introduction to Agile/Scrum.



Agile Coaching By Manish Manekar - Introduction to Agile/Scrum.

Agile Coaching By Manish Manekar - Introduction to Agile/Scrum.



Total Views
Views on SlideShare
Embed Views



2 Embeds 4

http://www.linkedin.com 2
https://www.linkedin.com 2



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.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

Agile Coaching By Manish Manekar - Introduction to Agile/Scrum. Agile Coaching By Manish Manekar - Introduction to Agile/Scrum. Presentation Transcript

  • An Introduction to Agile/Scrum
  •  No rules – we will abide by rule of self discipline  Interrupt – with a caution not to disrupt the flow  Breaks – we will take frequent regular breaks  Discuss – your experience, doubts, suggestion  Review – we will review our progress regularlyTitle… …Agenda
  • Session I Session II Session III Session IV The Starter Agile Adoption Sprint Lifecycle Discussion Introduction Scrum Brief Sprint Planning Next Steps Methodology Discussion Sprint Progress Key Takeaway Recap/Review Recap/Review Recap/Review Recap/Review As you know, please note that Geometric requires an assessment be conducted at the end of the course.Set the Stage… …Session I
  •  The Starter  The Methodology  Trainee-Trainer Intro  Agile Development  Objective  Agile Project Management  Expectations  Agile Methods & Practices  Introduction to Agile  Session Recap/Review  About Agile  What have we completed?  Agile Manifesto  How are we doing?  Agile Principles  What needs to change?Agenda… …The Starter
  • TRAINER OBJECTIVE EXPECTATIONSManish Manekar First step in Scrum adoption  Formal orientation of Agile BE (Computer), Executive MBA  Understand Scrum 17 yrs in Software Development  Know your Role & Responsibility Agile Practitioner – 5 yrs  ___________________________ Certified Scrum Master  ___________________________ ITIL Certified  ___________________________ Certified Support Professional Software is my profession and Coaching my passion Please introduce yourself.Session I… …The Waterfall
  • How does it look like? (video)The Starter… …Introduction to Agile
  • Any comments?The Starter… …Introduction to Agile
  • DICTIONARY CONTEXT WIKIPEDIA  agile  a quick & well coordinated Agile software development refers movement to a group of software  Able to move quickly and with development methodologies suppleness, skill, and control  adaptive to change based on iterative development, where  Lively, Alert, & Responsive  people oriented not process requirements and solutions oriented evolve through collaboration between self-organizing cross-  simple and flexible functional teams. The term “Agile” was coined in the year 2001 when the Agile Manifesto was formulated.The Waterfall… …About Agile
  • Agile methodology is based on Iteration refers to short A group of agilist and independent iterative development, where cycle, typically between 1 and 4 thinkers, naming themselves as requirements and solutions weeks, and also referred to as a “The Agile Alliance”, representing evolve through collaboration sprint. different lightweight between self-organizing cross- methodologies (now known as functional teams. Self-organizing team is a close agile methodologies) agreed on group of motivated individuals the Manifesto for Agile Software committed to Agile values & Development. principles who have been empowered to take initiatives & decisions Agile manifesto is a set of values the alliance acknowledges and states as their emphasis.Introduction to Agile… …Agile Manifesto
  • About Agile… …Agile Principles
  • #1 #2 #3Our highest priority is to satisfy Welcome changing Deliver working software the customer through early and requirements, even late in frequently, from a couple of continuous delivery of valuable development. Agile processes weeks to a couple of software. harness change for the months, with a preference to the customers competitive shorter timescale. advantage.Agile Manifesto… …Agile Principles
  • #4 #5 #6Business people and developers Build projects around motivated The most efficient and effective must work together daily individuals. Give them the method of conveying throughout the project. environment and support they information to and within a need, and trust them to get the development team is face-to- job done. face conversation.Agile Principles … … Agile Principles
  • #7 #8 #9Working software is the primary Agile processes promote Continuous attention to technical measure of progress. sustainable development. The excellence and good design sponsors, developers, and users enhances agility. should be able to maintain a constant pace indefinitely.Agile Principles … … Agile Principles
  • #10 #11 #12Simplicity--the art of maximizing The best At regular intervals, the team the amount of work not done--is architectures, requirements, and reflects on how to become more essential. designs emerge from self- effective, then tunes and adjusts organizing teams. its behavior accordingly.Agile Principles … …The Methodology
  • METHODOLOGY METHOD PRACTICEMethodology is a set or system of Method is a Practice is repeated performance methods, principles, and rules for procedure, technique, or way of or systematic exercise for the regulating a given discipline, as doing something, esp. in purpose of acquiring skill or in the arts or sciences. accordance with a definite plan. proficiency.Agile Principles… …The Methodology
  • DEVELOPMENT MANAGEMENT METHOD/PRACTICEAgile Development is generally Agile Management is offered by Methods referred to software certain but not all Agile methods. Extreme Programming development that follows Agile Feature Driven Development values and principles. Scrum is one such framework that Scrum allows teams to deliver a Lean Software Development potentially shippable set of functionality per iteration in a Practices team based incremental Test Driven Development manner. Behavior Driven Development Pair Programming Planning PokerThe Methodology… …Q&A
  • Questions!The Methodology… …The Agile
  • How does it look like? (video)Q&A… …Recap/Review
  • Any comments?Q&A… …Recap/Review
  • RECAP WHAT HAVE WE COMPLETED? REVIEW HOW ARE WE DOING? WHAT NEEDS TO CHANGE?  Training kick-off  How are we doing?  Introduction to Agile  ___________ is working well  Agile Manifesto  ___________ is not going well  ___________ need to improve  Agile Principles  The Methodology  What needs to change?  Agile Development  ________________________  Agile Project Management  ________________________  Agile Methods & Practices  ________________________Title… …Agenda
  • Break Time!Recap/Review… …Session II
  •  Agile Adoption  Q&A and Discussion  Culture, Mindset and Change  Commitment  Tools  Scrum Brief  Session Recap/Review  Scrum Flow and Roles  What have we completed?  Product Backlog  How are we doing?  Scrum Meetings and Metrics  What is required to change?Title… …Agenda
  • CULTURE… COMMITMENT TOOLS Culture  Management  Do not bogged down by tools Mindset  Team  Agile is not about using tools ChangeSession II… …Scrum Brief
  • Questions!Agile Adoption… …Scrum Brief
  • Are you ready for Agile? (video)Q&A… …Recap/Review
  • • impediments • burndown • done daily scrum series of sprints • plan product vision • review drives • retrospect releases • roadmap • planningAgile Adoption… • backlog …Scrum
  • ROLES BACKLOG MEETINGS Product Owner  Product Backlog  Release Planning Scrum Master  Sprint Backlog  Sprint Planning Team  Impediments Backlog  Daily Scrum Stakeholders  Review  RetrospectiveAgile Adoption… …Q&A
  • Questions!Scrum Brief… …Recap/Review
  • Scrum in under 10 minutes. (video)Q&A… …Recap/Review
  • RECAP WHAT HAVE WE COMPLETED? REVIEW HOW ARE WE DOING? WHAT NEEDS TO CHANGE?  Agile Adoption  How are we doing?  Culture, Mindset and Change  ___________ is working well  Commitment  ___________ is not going well  Tools  ___________ need to improve  Scrum Brief  What needs to change?  Scrum Flow and Roles  ________________________  Product Backlog  ________________________  Scrum Meetings and Metrics  ________________________Scrum… …Break
  • Break Time!Recap/Review… …Session III
  •  Sprint Lifecycle  Sprint Progress  Planning Meeting  Storyboard  Daily Scrum  Burndown Chart  Review and Retrospect  Impediment Backlog  Sprint Planning  Session Recap/Review  Prioritized Backlog  What have we completed?  Team Velocity  How are we doing?  Estimates  What is required to change?Break… …Sprint
  • Daily Scrum Retrospect • Velocity • Accepted • Sprint Backlog • I did... • Bad • or Rejected • Estimate • Im doing... • Good • My Problem... • Great Sprint Review PlanningSession III… …Sprint
  • PRIOR DURING AFTERSprint… …Sprint
  • StoryboardSprint… …Sprint
  • BurndownSprint… …Sprint
  • Questions!Sprint … …Recap/Review
  • A day in life of Scrum team. (video)Q&A… …Recap/Review
  • RECAP WHAT HAVE WE COMPLETED? REVIEW HOW ARE WE DOING? WHAT NEEDS TO CHANGE?  Sprint Lifecycle  How are we doing?  Plan - Scrum - Review - Retro  ___________ is working well  ___________ is not going well  Sprint Planning  ___________ need to improve  Backlog - Velocity - Estimates  What needs to change?  ________________________  Sprint Progress  ________________________  Storyboard and Burndown  ________________________Sprint… …Break
  • Break Time!Recap/Review… …Session IV
  •  Open House  Key Takeaway  Next Steps  Training Recap/Review  What have we completed?  How are we doing?  What is required to change?Break… …Open House
  • Scrum!Session IV… …Next Steps
  •  Learn & Assimilate Agile Values & Principles  Learn the Basics of Agile/Scrum  Learn & Identify Challenges in Agile Adoption  Pilot Agile Development  Coach the Team and Go AgileOpen House… …Key Takeaway
  • Session IV… …Next Steps
  • RECAP WHAT HAVE WE COMPLETED? REVIEW HOW ARE WE DOING? WHAT NEEDS TO CHANGE?  Introduction to Agile  How are we doing?  Agile Adoption  ___________ is working well  Introduction to Scrum  ___________ is not going well  Sprint Lifecycle  ___________ need to improve  Sprint Progress  What needs to change?  Next Steps  ________________________  ________________________  ________________________Title… …Agenda
  • Oops!Sprint Progress… …Recap/Review
  • Happy Scrum!
  • An Introduction to Agile/Scrum