Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Page 1 of 23
Overview of Agile - Scrum
Presentation on Scrum – an Agile methodology
Prepared by : Ratul Paul
Page 2 of 23
Agile -- The Change ⌘
Agile is a time b...
Presentation on Scrum – an Agile methodology
Prepared by : Ratul Paul
Page 3 of 23
Agile Manifesto ⌘
"We are uncovering be...
Presentation on Scrum – an Agile methodology
Prepared by : Ratul Paul
Page 4 of 23
Waterfall ⌘
 Published in 1970 by Wins...
Presentation on Scrum – an Agile methodology
Prepared by : Ratul Paul
Page 5 of 23
Waterfall Model Problems ⌘
 Market Dyn...
Presentation on Scrum – an Agile methodology
Prepared by : Ratul Paul
Page 6 of 23
Successful Project ⌘
 Successful proje...
Presentation on Scrum – an Agile methodology
Prepared by : Ratul Paul
Page 7 of 23
Scrum Process⌘
Scrum Roles ⌘
 Product ...
Presentation on Scrum – an Agile methodology
Prepared by : Ratul Paul
Page 8 of 23
Project Manager can either be:
 Scrum ...
Presentation on Scrum – an Agile methodology
Prepared by : Ratul Paul
Page 9 of 23
Product Owner ⌘
 Responsible for repre...
Presentation on Scrum – an Agile methodology
Prepared by : Ratul Paul
Page 10 of 23
Sprint Backlogs⌘
 A subset of Product...
Presentation on Scrum – an Agile methodology
Prepared by : Ratul Paul
Page 11 of 23
Agile – Scrum Planning ⌘
Agile Estimat...
Presentation on Scrum – an Agile methodology
Prepared by : Ratul Paul
Page 12 of 23
Planning Poker⌘
 Everyone selects com...
Presentation on Scrum – an Agile methodology
Prepared by : Ratul Paul
Page 13 of 23
“Information Radiators” – Scrum Wall ⌘...
Presentation on Scrum – an Agile methodology
Prepared by : Ratul Paul
Page 14 of 23
Sprint Burn-down Chart⌘
Tools⌘
Presentation on Scrum – an Agile methodology
Prepared by : Ratul Paul
Page 15 of 23
Post-it vs tools⌘
 Tools can confine ...
Presentation on Scrum – an Agile methodology
Prepared by : Ratul Paul
Page 16 of 23
 The questions must be asked:
 What ...
Presentation on Scrum – an Agile methodology
Prepared by : Ratul Paul
Page 17 of 23
Agile Risk Management⌘
Risk Adjusted B...
Presentation on Scrum – an Agile methodology
Prepared by : Ratul Paul
Page 18 of 23
Risk Burndown Graph ⌘
Presentation on Scrum – an Agile methodology
Prepared by : Ratul Paul
Page 19 of 23
Scrum and...⌘
 documentation - You st...
Presentation on Scrum – an Agile methodology
Prepared by : Ratul Paul
Page 20 of 23
 What happened to Gantt?
 Time repor...
Presentation on Scrum – an Agile methodology
Prepared by : Ratul Paul
Page 21 of 23
As needed
Agenda:
What has your team d...
Presentation on Scrum – an Agile methodology
Prepared by : Ratul Paul
Page 22 of 23
 Extreme Programming (XP)
 Feature D...
Presentation on Scrum – an Agile methodology
Prepared by : Ratul Paul
Page 23 of 23
Test your understanding (with mock exa...
Upcoming SlideShare
Loading in …5
×

Scrum_Presentation_Ratul

317 views

Published on

  • Be the first to comment

  • Be the first to like this

Scrum_Presentation_Ratul

  1. 1. Page 1 of 23 Overview of Agile - Scrum
  2. 2. Presentation on Scrum – an Agile methodology Prepared by : Ratul Paul Page 2 of 23 Agile -- The Change ⌘ Agile is a time boxed, iterative approach to software delivery that builds software incrementally from the start of the project, instead of trying to deliver it all at once near the end.
  3. 3. Presentation on Scrum – an Agile methodology Prepared by : Ratul Paul Page 3 of 23 Agile Manifesto ⌘ "We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:  Individuals and interactions over processes and tools  Working software over comprehensive documentation  Customer collaboration over contract negotiation  Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more." http://agilemanifesto.org/ Principles behind Agile ⌘  Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.  Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.  Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.  Business people and developers must work together daily throughout the project.  Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.  The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.  Working software is the primary measure of progress.  Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.  Continuous attention to technical excellence and good design enhances agility.  Simplicity--the art of maximizing the amount of work not done--is essential.  The best architectures, requirements, and designs emerge from self-organizing teams.  At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
  4. 4. Presentation on Scrum – an Agile methodology Prepared by : Ratul Paul Page 4 of 23 Waterfall ⌘  Published in 1970 by Winston W. Royce  Ironically, Royce was presenting this model as an example of a flawed, non-working model  Ideal in construction or engineering projects  Usually preceded by prototyping  Requires Central Control System  As complexity increases, central control breaks down Waterfall Stages ⌘
  5. 5. Presentation on Scrum – an Agile methodology Prepared by : Ratul Paul Page 5 of 23 Waterfall Model Problems ⌘  Market Dynamics/Changing Requirements  Blaming other people (Analysts blaming designers, designers developers, etc..)  Lack of understanding business by lower ranks  Long feedback  Hit-by-a-spaceship effect (Abducted by aliens) Waterfall vs Agile ⌘ Requirements for the whole project vs. requirements for the iteration, overview of the bigger picture  Clearly defined roles vs Cross-functional teams  Long time estimation vs short time estimation  Long-time budgeting vs short time budgeting  Abandoning project in the middle leaves useless artifacts vs each iteration delivers business value  Extensive out-of-synch documentation vs lean general and in-line code documentation  Changes are expensive vs changes are expected and cheap  Long feedback loop between customer and developer vs almost immediate feedback Agile Inverted Triangle ⌘
  6. 6. Presentation on Scrum – an Agile methodology Prepared by : Ratul Paul Page 6 of 23 Successful Project ⌘  Successful project is not necessarily a project that goes exactly as expected, yielding results identical to those that were predicted.  Scrum controls the process of software development to guide work toward the most valuable outcome possible. Agile Frameworks -- Methodologies ⌘
  7. 7. Presentation on Scrum – an Agile methodology Prepared by : Ratul Paul Page 7 of 23 Scrum Process⌘ Scrum Roles ⌘  Product Owner: The customer itself or the proxy between the customer and the team  Scrum Master: Typically not a project manager  Development Team All management responsibilities in a project are divided among these three roles!!! Project Manager ⌘ THERE IS NO PROJECT MANAGER ROLE! What does the project manager do in SCRUM? Potential role of "Traditional Project Manager" in SCRUM ⌘ It depends upon!  Organizational Set-up  Size of Project  Competency of Project Manager
  8. 8. Presentation on Scrum – an Agile methodology Prepared by : Ratul Paul Page 8 of 23 Project Manager can either be:  Scrum Master  Product Owner  Project Manager owning multiple Scrum teams  Choosing Teams  Budgeting  Client Interaction  Manage Contract  Interface with PMO Scrum Team ⌘  The Team is responsible for developing functionality  Self-managing and self-organizing  Up to 10 people (7 optimal)  Cross functional (db admin, web designer, tester, etc...)  Bigger project = more Scrum teams  Responsible for managing itself and has full authority to do anything to meet the Sprint goal within the guidelines, standards, and conventions of the organization and of Scrum Scrum Master ⌘  Responsible for the Scrum process  Teaching Scrum to everyone involved in the project  Implementing Scrum so that it fits within an organization’s culture and still delivers the expected benefits  Ensuring that everyone follows Scrum rules and practices  Manager drives the team vs Scrum Master serves the team  Scrum Master is a facilitator
  9. 9. Presentation on Scrum – an Agile methodology Prepared by : Ratul Paul Page 9 of 23 Product Owner ⌘  Responsible for representing the interests of everyone with a stake in the project and its resulting system  Achieves initial and ongoing funding for the project by creating:  project’s initial overall requirements  return on investment (ROI) objectives  release plans  The list of requirements is called the Product Backlog  The most valuable functionality is produced first  Prioritize the Product Backlog to queue up the most valuable requirements for the next iteration Backlogs ⌘ Product backlog Iteration backlog  User stories  Epics  User stories (what)  Tasks (how)  Bugs Product Backlog⌘  The requirements for the system or product  Product Owner is responsible for the contents, prioritization, and availability of the Product Backlog  It is never complete  Is merely an initial estimate of the requirements  Span to foreseeable future  Made of pieces of functionality or wish list  Epics  Stories  Proven business value  Testable  Examples  User can browse on-line catalogue  Client can buy a product using a credit card
  10. 10. Presentation on Scrum – an Agile methodology Prepared by : Ratul Paul Page 10 of 23 Sprint Backlogs⌘  A subset of Product Backlog  Specified and discussed with all the team members especially with the product owner  Estimated by more than one person (ideally, entire team)  If it takes longer than a couple of days, they should be split Definition of 'DONE'⌘  Definition of Done can differ  Clarify what does it mean  Entire Scrum Team contributes to Definition of Done  For example:  functional and unit tested  documented  committed into repository  deployed on staging environment  accepted by the client (thumbs up) Scrum Process ⌘
  11. 11. Presentation on Scrum – an Agile methodology Prepared by : Ratul Paul Page 11 of 23 Agile – Scrum Planning ⌘ Agile Estimation Technique⌘  User stories  Business value  How to test it (acceptance criteria)  Different schools about complexity  Abstract size (0,1,2,3,5,8)  Number of IDEAL days - A day in life of developer where he has everything he needs to complete the job with no disturbance.  Planning poker  Splitting User stories into task  Task duration from 1 hour up to 1 day. If its gets longer, it is advisable to break it further.
  12. 12. Presentation on Scrum – an Agile methodology Prepared by : Ratul Paul Page 12 of 23 Planning Poker⌘  Everyone selects complexity from Planning Poker Card  Two extreme people explain why they thought this way  Discussion  Optional re-vote  You can play poker for estimated time and estimated business value Precision vs Accuracy⌘  Precise but not accurate PI number: 3.12134352343435  Accurate but not precise number PI number: 3.14  Try to be accurate not precise  Precision gives false confidence about estimation Estimation⌘  What is the height of the highest mountain  What is the longitude of Reykjavik  What is the latitude of Reykjavik Iteration – The Sprint ⌘  Estimating and Planning (4+1)  Define clear goals  Everyone (not only the person who are going to develop it) MUST understand the task  Everyone can contribute their way they see is the best  Daily Scrums (15min every day)  Demonstration (1h)  Retrospection – review of the sprint (1h)
  13. 13. Presentation on Scrum – an Agile methodology Prepared by : Ratul Paul Page 13 of 23 “Information Radiators” – Scrum Wall ⌘ SCRUM WALL -- It is a board which will be updated daily & present the current status of the sprint. Product Burn-down Chart⌘
  14. 14. Presentation on Scrum – an Agile methodology Prepared by : Ratul Paul Page 14 of 23 Sprint Burn-down Chart⌘ Tools⌘
  15. 15. Presentation on Scrum – an Agile methodology Prepared by : Ratul Paul Page 15 of 23 Post-it vs tools⌘  Tools can confine your choices  Post-its are simple and always visible  Tools are recommended when you work with an outsourced teams’ members Iteration Duration and Team Velocity⌘  Do not change the duration of an iteration!  What if we discovered new tasks to do in order to complete user story?  Measurement – hours or finished tasks  What does it mean done  Overtime  Adjusting next iteration Team Responsibility⌘  All team members are responsible  Hit-by-the-bus factor  Openness  Support and knowledge exchange  Pair programming (one keyboard)  Master-lamma pair programming Daily Scrums⌘
  16. 16. Presentation on Scrum – an Agile methodology Prepared by : Ratul Paul Page 16 of 23  The questions must be asked:  What have I done since the last Daily Scrum?  What am I going to do between now and the next Daily Scrum?  What is preventing me from doing my work?  People MUST stand  Up to 15 min regardless of the team size  Everyone invited, only pigs are talking Scrum guidelines⌘  Product Backlog Planning (PO, Managers, Application Users)  Sprint Planning Meeting (Team, PO, SM)  Estimation  Iteration (Sprint) from 2 to 4 weeks - Daily Scrum (stand-up meeting)  Demonstration  Iteration review (retrospective meeting) Scrum Pros and Cons⌘ Pros Cons Better communication Faster development Better team relations Better productivity  People must be focused all the time. Some people may leave.  Managers lose some of their powers. Some may leave or obstruct the changes.  Partially introduce can do more harm than good.
  17. 17. Presentation on Scrum – an Agile methodology Prepared by : Ratul Paul Page 17 of 23 Agile Risk Management⌘ Risk Adjusted Backlog ⌘
  18. 18. Presentation on Scrum – an Agile methodology Prepared by : Ratul Paul Page 18 of 23 Risk Burndown Graph ⌘
  19. 19. Presentation on Scrum – an Agile methodology Prepared by : Ratul Paul Page 19 of 23 Scrum and...⌘  documentation - You still need some sort of documentation  budgeting  outsourcing  bigger projects Where not to use SCRUM⌘  If you know requirements upfront and model must be proven - Life critical projects (medical, army, etc...)  Cannot change the way clients or your management thinks  Old ways work fine ; -) Painful Transition⌘
  20. 20. Presentation on Scrum – an Agile methodology Prepared by : Ratul Paul Page 20 of 23  What happened to Gantt?  Time reporting?  Documentation?  Responsibility  Clients involved all the times Beware of these PITFALLS ⌘ TOP 10 REASONS AGILE PROJECTS FAIL 1. Transitioning without proper Training/Coaching 2. Resistance To change 3. Seating Arrangement 4. Poor Communication/Collaboration 5. Lack of Transparency 6. Fear of challenges 7. Process without Principles 8. Not empowering the teams 9. No proper Retrospection 10. Still no cross-functional team Scrum of Scrums ⌘
  21. 21. Presentation on Scrum – an Agile methodology Prepared by : Ratul Paul Page 21 of 23 As needed Agenda: What has your team done since we last met? What will your team do before we meet again? Is anything slowing your team down or getting in their way? Are you about to put something in another team’s way? Tools⌘  JIRA (Greenhopper)  Redmine  Xplanner (deprecated)  Google Calc (be careful)  Agilo  Scrumy  Spreedsheet (deprecated)  Wiki Other Agile Methodologies⌘
  22. 22. Presentation on Scrum – an Agile methodology Prepared by : Ratul Paul Page 22 of 23  Extreme Programming (XP)  Feature Driven Development (FDD)  Dynamic Systems Development Method (DSDM)  Crystal  Lean Software Development  Kanban XP Practices⌘ XP consists of number of powerful core practices which help in succeeding with scrum. They are:  Small Releases  Collective Code Ownership  Coding Standards  Continuous Integration  Test Driven Development (TDD)  Continuous Refactoring  Simple Design  Pair Programming Scrum - Lets Summarize⌘  Accepting uncertainty  Welcome technology changes  Delivering early and often  Constant estimating and planning  Sustainable work pace  Early feedback and learning  Self-managing work environment  Self-determining environment  Delegating the responsibility  Have satisfaction at work Appendix ⌘
  23. 23. Presentation on Scrum – an Agile methodology Prepared by : Ratul Paul Page 23 of 23 Test your understanding (with mock exams): http://mockexam4u.com/certification/certified-scrummaster-csm/ http://www.scrum-institute.org/Example_Scrum_Certification_Test_Questions.php Certification Milestones: https://www.scrumalliance.org/certifications Queries or Contacts : For any query for information, please feel free to contact @ https://ch.linkedin.com/in/ratulpaul https://www.scrumalliance.org/community/profile/rpaul24 ---- XXXXX ----

×