Introduction to agile scrum
Download as PPT, PDF0 likes512 views
The document provides an overview of Scrum, an Agile framework for project management. It describes Scrum's core roles, events, artifacts, and values. The Product Owner prioritizes features, the Scrum Master facilitates the process, and self-organizing Teams work in sprints to deliver working software. Sprints involve planning, daily stand-ups, taskboards to track work, a sprint review to demonstrate work to stakeholders, and a retrospective to improve the process. Customers benefit from early feedback and faster delivery of working products, while teams enjoy sustainable pacing and satisfaction from delivering quality work.
Introduction to agile scrum
- 1. Scrum Intro What’s in it for me? Prepared by Bachan Anand
- 2. Agenda Overview of Agile and Scrum Scrum: Vision and Product Scrum: Sprint What’s in it for me 2
- 3. Overview of Agile and Scrum
- 4. Overview of Agile and Scrum Agile Manifesto Agile is a set of values: Individuals and interactions over processes and tools Working software (Products) over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan 4
- 5. Overview of Agile and Scrum Agile Principles Highest priority is to satisfy the customer through early and continuous delivery of valuable software/products Welcome changing requirements Deliver working software (product) frequently Business people and developers must work together daily throughout the project 5
- 6. Overview of Agile and Scrum Agile Principles Build projects around motivated individuals Most efficient and effective method of conveying information is face-to-face conversation Working software (product) is the primary measure of progress Agile processes promote sustainable development (maintain a constant pace indefinitely) 6
- 7. Overview of Agile and Scrum Agile Principles …cont’d Continuous attention to technical excellence and good design enhances agility Simplicity (art of maximizing amount of work not done) is essential Best architectures, requirements, and designs emerge from self-organizing teams At regular intervals, team reflects on how to become more effective, then tunes and adjusts http://agilemanifesto.org/principles.html 7
- 8. Overview of Agile and Scrum What is Scrum Scrum is an Agile framework that supports lightweight processes that emphasize: Continuous improvement Quality of Product Incremental deliveries Discovery of people’s potential Scrum is simple to understand, requires discipline in order to be successful Scrum is not a methodology 8
- 9. Overview of Agile and Scrum Foundations of Scrum Empiricism Self-Organization Do the next right thing Rhythm Small teams manage their own workload and organize themselves around clear goals and constraints Prioritization Detailed up-front planning and defined processes are replaced by just-in-time Inspect and Adapt cycles Allows teams to avoid daily noise and focus on delivery Collaboration Leaders and customers work with the Team, rather than directing them 9
- 10. Overview of Agile and Scrum Core Values Transparency Everything about a project is visible to everyone Commitment Making realistic commitments Courage Have the courage to commit, to act, to be open and to expect respect Focus Focus all of your efforts and skills on doing the work that you have committed to doing Respect Respect and trust the different people who comprise a team 10
- 11. Scrum: Vision and Product
- 12. Scrum: Vision and Product Vision A goal to aspire to Can be summarized in a short statement of intent Communicate it to the team 12
- 13. Scrum: Vision and Product Role: Product Owner Thought Leader and Visionary Drives the Product Vision (for example, with Story Mapping) Prioritizes the Goals - User Stories Maintains the Product Backlog with the team Accepts the Working Product (on behalf of the customer) 13
- 14. Scrum: Sprint
- 15. Scrum: Sprint Role: ScrumMaster Servant Leader Facilitates the Process Supports the Team Removes Organizational Impediments Socializes Scrum to Management Enable close collaboration across all roles and functions 15
- 16. Scrum: Sprint Role: Team Cross-Functional 4-8 Members Self-Organizing Focused on meeting Commitments 16
- 18. Scrum Diagram Diagram from theagilemindset.com 18
- 19. Scrum: Sprint Flow & Artifacts: Planning Sprint Planning meeting held at beginning of each Sprint Duration and time-effort are fixed in any given Sprint Goal is to have prioritized Sprint Backlog, broken down into tasks, that the Team can commit to During planning, Team commits to scope that can be completed in the Sprint, taking into account the definition of Done 19
- 20. Scrum: Sprint Flow & Artifacts: Daily Standup Meetings held in same location, same time, every day Timeboxed at 15 minutes Encourages self-organization, rhythm, and collaboration Not a status meeting Each Team member speaks to: What did I accomplish in the last 24 hours What do I plan to accomplish in the next 24 hours Any impediments getting in the way of my work 20
- 21. Scrum: Sprint Flow & Artifacts: Taskboard Active visual indicator of flow of work Should be visible to team members at all times Should be kept current Encourages selforganization, and collaboration 21
- 22. Scrum: Sprint Flow & Artifacts: Sprint Review Occurs at the end of each Sprint Inspect and Adapt the product (Empiricism) The team meets with the Product Owner (and Stakeholders) to demonstrate the working software from the Sprint This is a hands-on software demo (not a PowerPoint) that usually requires some prep beforehand 22
- 23. Scrum: Sprint Flow & Artifacts: Retrospective Occurs at the end of each Sprint Inspect and Adapt the process (Empiricism) Team and ScrumMaster meet to reflect on what went well and what can be improved Tone of the meeting is that everyone did their best and now look to how can we improve Retrospectives must conclude with team commitments to action 23
- 24. What is in it for me? (Customer) As a customer , I want to be able to Have Opportunity to provide feedback early Go to market faster with Quality Faster return on investment 24
- 25. What is in it for me? (Leadership) As a Leader , I want To 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 want A sustainable pace Satisfaction of quality product delivered Clear Priority and less interruption during development 26
- 27. How do you learn Scrum – By Doing? Apply few practices at a time Understand the values and foundations Inspect and Adapt Experience the Joy of Doing Scrum 27
- 28. How do you learn Scrum ? Experiential Training 28
- 29. User groups /Communities ALN – Agile Leadership Network Scrum Alliance – Scrum User Groups Online User Groups Scrum Alliance 29
- 31. Q&A 31
- 32. Scrum is a lightweight framework with a simple set of rules, built on foundations and values Scrum enables teams to discover their true potential and deliver quality software that adds business value 32
- 33. Agile & Scrum Trainings in US Albuquerque Charlotte Little Rock Raleigh Atlanta Chicago Minneapolis Richmond Austin Dallas Los Angeles San Diego Baltimore Denver New York San Francisco / San Jo Bentonville Hartford Oklahoma Seattle Boston Houston Orlando St. Louis Boulder Irvine Philadelphia Tampa Charleston Las Vegas Phoenix Washington D.C. 33
- 34. FREE Kindle Fire HD With Certified ScrumMaster Trainings in December 2013! 34
- 35. Thank you ! More Resources at http://agile.conscires.com/suggested-reading-listand-resources/ Contact Info Bachan Anand Bachan.anand@conscires.com +91-9972992288 (India), +1-949-981-0998 (US) http://www.linkedin.com/in/bachan 35
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
- #20: done in two meetings. Requirements Workshop and Design Workshop Can also have Pre-Planning (Estimation) and Product Backlog Grooming meeting If 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: Story Tasks (Things to Do) Work in Progress (WIP) Blocked/Impeded Done