Webinar - Into to Scrum by Bachan Anand
Download as PPTX, PDF1 like963 views
This document provides an overview of Scrum, which is an Agile framework that emphasizes incremental deliveries, quality of product, and continuous improvement. It discusses Scrum roles like Product Owner, ScrumMaster, and Team. The Scrum process involves sprint planning, daily standups, taskboards, sprint reviews, and retrospectives. Benefits are outlined for customers, leadership, and team members. Experiential training and certifications are recommended ways to learn Scrum.
Webinar - Into to Scrum by Bachan Anand
- 1. Scrum IntroWhat’s in it for me? Prepared by Bachan Anand Please dial into (218) 895-4640 PIN: 3289145
- 2. AgendaOverview of Agile and ScrumScrum: Vision and ProductScrum: SprintWhat’s in it for me2
- 3. Overview of Agile and Scrum
- 4. Overview of Agile and ScrumAgile ManifestoAgile is a set of values:Individuals and interactions over processes and toolsWorking software (Products) over comprehensive documentationCustomer collaboration over contract negotiationResponding to change over following a plan4
- 5. Overview of Agile and ScrumAgile PrinciplesHighest priority is to satisfy the customerthrough early and continuous deliveryof valuable software/productsWelcome changing requirementsDeliver working software (product) frequentlyBusiness people and developers must work together daily throughout the project5
- 6. Overview of Agile and ScrumAgile PrinciplesBuild projects around motivated individualsMost efficient and effective method of conveying information is face-to-face conversationWorking software (product) is the primary measure of progressAgile processes promote sustainable development (maintain a constant pace indefinitely)6
- 7. Overview of Agile and ScrumAgile Principles …cont’dContinuous attention to technical excellence and good design enhances agilitySimplicity (art of maximizing amount of work not done) is essentialBest architectures, requirements, and designs emerge from self-organizing teamsAt regular intervals, team reflects on how to become more effective, then tunes and adjustshttp://agilemanifesto.org/principles.html7
- 8. Overview of Agile and ScrumWhat is ScrumScrum is an Agile framework that supports lightweight processes that emphasize:Incremental deliveriesQuality of ProductContinuous improvementDiscovery of people’s potentialScrum is simple to understand, but requires discipline in order to be successfulScrum is not a methodology8
- 9. Overview of Agile and ScrumFoundations of ScrumEmpiricism Detailed up-front planning and defined processes are replaced by just-in-time Inspect and Adapt cyclesSelf-OrganizationSmall teams manage their own workload and organize themselves around clear goals and constraintsPrioritizationDo the next right thingRhythmAllows teams to avoid daily noise and focus on deliveryCollaborationLeaders and customers work with the Team, rather than directing them9
- 10. Overview of Agile and ScrumCore ValuesTransparencyEverything about a project is visible to everyoneCommitmentBe willing to commit to a goalCourageHave the courage to commit, to act, to be open and to expect respectFocusFocus all of your efforts and skills on doing the work that you have committed to doingRespectRespect and trust the different people who comprise a team10
- 11. Scrum: Vision and Product
- 12. Scrum: Vision and ProductVisionA goal to aspire toCan be summarized in a short statement of intentCommunicate it to the team12
- 13. Scrum: Vision and ProductRole: Product OwnerThought Leader and VisionaryDrives the Product Vision (for example, with Story Mapping)Prioritizes the Goals - User Stories Maintains the Product Backlog with the teamAccepts the Working Product (on behalf of the customer)13
- 14. Scrum: Sprint
- 15. Scrum: SprintRole: ScrumMasterServant LeaderFacilitates the ProcessSupports the TeamRemoves Organizational ImpedimentsSocializes Scrum to ManagementEnable close collaboration across all roles and functions15
- 16. Scrum: SprintRole: TeamCross-Functional 4-8 MembersSelf-OrganizingFocused on meeting Commitments16
- 19. Scrum: SprintFlow & Artifacts: PlanningSprint Planning meeting held at beginning of each SprintTime and Resources are fixed in any given Sprint Goal is to have prioritized Sprint Backlog, broken down into tasks, that the Team can commit toDuring planning, Team commits to scope that can be completed in the Sprint, taking into account the definition of DoneStory points may be refined19
- 20. Scrum: SprintFlow & Artifacts: Daily StandupMeetings held in same location, same time, every dayTimeboxed at 15 minutesEncourages self-organization, rhythm, and collaborationNot a status meetingEach Team member speaks to:What did I accomplish in the last 24 hoursWhat do I plan to accomplish in the next 24 hoursAny impediments getting in the way of my work20
- 21. Scrum: SprintFlow & Artifacts: TaskboardActive visual indicator of flow of workShould be visible to team members at all timesShould be kept currentEncourages self-organization, and collaboration21
- 22. Scrum: SprintFlow & Artifacts: Sprint ReviewOccurs at the end of each SprintInspect and Adapt the product (Empiricism)The team meets with the Product Owner (and Stakeholders) to demonstrate the working software from the SprintThis is a hands-on software demo (not a PowerPoint) that usually requires some prep beforehand22
- 23. Scrum: SprintFlow & Artifacts: RetrospectiveOccurs at the end of each SprintInspect and Adapt the process (Empiricism)Team and ScrumMaster meet to reflect on what went well and what can be improvedTone of the meeting is that everyone did their best and now look to how can we improveRetrospectives must conclude with team commitments to action23
- 24. What is in it for me? (Customer)As a customer , I want to be able toHave Opportunity to provide feedback earlyGo to market faster with QualityFaster return on investment24
- 25. What is in it for me? (Leadership)As a Leader , I wantTo understand progress in terms of real progress made on product . Better engaged & accountable team 25
- 26. What is in it for me? ( Team Member)Who is a typical team member?As a team member, I wantA sustainable paceSatisfaction of quality product deliveredClear Priority and less interruption during development26
- 27. How do you learn Scrum – By Doing?Apply few practices at a timeUnderstand the values and foundationsInspect and AdaptExperience the Joy of Doing Scrum27
- 28. How do you learn Scrum ? Experiential Training 28
- 29. User groups /CommunitiesAPLN – Agile Project Leadership NetworkScrum Alliance – Scrum User GroupsOnline User GroupsScrum Alliance29
- 31. Q & A31
- 32. 32Scrum is a lightweight framework with a simple set of rules, built on foundations and valuesScrum enables teams to discover their true potential and deliver quality software that adds business value
- 33. Donation only 1 day TrainingsDenver – May 14thhttp://agile.conscires.com/scrum-1-day-training-denver/Seattle – May 15thhttp://agile.conscires.com/agile-scrum-training-seattle-01/Boston – May 20thhttp://agile.conscires.com/1-day-agile-scrum-training-boston-02/Irvine – June 4thhttp://agile.conscires.com/1-day-agile-scrum-training-irvine-04/33
- 34. Thank you !More Resources athttp://agile.conscires.com/suggested-reading-list-and-resources/Contact InfoBachan AnandBachan.anand@conscires.com949-232-8900http://www.linkedin.com/in/bachan34
Editor's Notes
- #2: Test
- #11: Doing Scrum mechanics without these values misses the point. These values are not unique to Scrum, but the Scrum Framework is built on top of these values.
- #17: Cross-Functional = Dev, QA, Bus Analyst, UI Designer, Architect
- #19: Sprints are TimeBoxed 1 to 2 weeksTypical duration is 2–4 weeks or a calendar month at mostA constant duration leads to a better rhythm
- #20: done in two meetings. Requirements Workshop and Design WorkshopCan also have Pre-Planning (Estimation) and Product Backlog Grooming meetingIf commitment is inaccurate (either under-commit or over-commit), then stories are to be added or removed. Team would then reflect in the Retrospective and accordingly adjust their upcoming commitments
- #22: StoryTasks (Things to Do)Work in Progress (WIP)Blocked/ImpededDone