Scrum Intro What’s in it for me? Please dial into  +1 (646) 558-2123  ACCESS CODE:  479-408-170   Prepared by  Bachan Anand
Agenda Overview of Agile and Scrum Scrum: Vision and Product Scrum: Sprint What’s in it for me Please dial into  +1 (646) 558-2123  ACCESS CODE:  479-408-170
Overview of Agile and Scrum Please dial into  +1 (646) 558-2123  ACCESS CODE:  479-408-170
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 Please dial into  +1 (646) 558-2123  ACCESS CODE:  479-408-170
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 Please dial into  +1 (646) 558-2123  ACCESS CODE:  479-408-170
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)
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
Overview of Agile and Scrum What is Scrum Scrum is an Agile framework that supports lightweight processes that emphasize: Incremental deliveries Quality of Product Continuous improvement Discovery of people’s potential Scrum is simple to understand, but requires discipline in order to be successful Scrum is  not  a methodology
Overview of Agile and Scrum   Foundations of Scrum Empiricism  Detailed up-front planning and defined processes are replaced by just-in-time Inspect and Adapt cycles Self-Organization Small teams manage their own workload and organize themselves around  clear goals and constraints Prioritization Do the next right thing Rhythm Allows teams to avoid daily noise and focus on delivery Collaboration Leaders and customers work with the Team, rather than directing them
Overview of Agile and Scrum   Core Values Transparency Everything about a project is visible to everyone Commitment Be willing to commit to a goal 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
Scrum: Vision and Product Please dial into  +1 (646) 558-2123  ACCESS CODE:  479-408-170
Scrum: Vision and Product Vision A goal to aspire to Can be summarized in a short statement of intent Communicate it to the team Please dial into  +1 (646) 558-2123  ACCESS CODE:  479-408-170
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) Please dial into  +1 (646) 558-2123  ACCESS CODE:  479-408-170
Scrum: Sprint
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
Scrum: Sprint Role: Team Cross-Functional  4-8 Members Self-Organizing Focused on meeting Commitments
Scrum: Sprint Role: Relationships
Scrum Diagram
Scrum: Sprint Flow & Artifacts: Planning Sprint Planning meeting held at beginning of each Sprint Time and Resources 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 Story points may be refined
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
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  self-organization,  and  collaboration
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
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
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
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 
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
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
How do you  learn Scrum ? Experiential Training
User groups /Communities APLN – Agile Project Leadership Network Scrum Alliance – Scrum User Groups Online User Groups Scrum Alliance
Scrum Certifications
Q & A
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
1-Day Trainings in March 2012 - India March 2– 1-Day training on Agile & Scrum in Bangalore http://agile.conscires.com/1-day-agile-scrum-training-bangalore-02/ March 9– 1-Day training on Agile & Scrum in Hyderabad http://agile.conscires.com/1-day-agile-scrum-training-hyderabad-01/ March 23– 1-Day training on Agile & Scrum in Chennai http://agile.conscires.com/1-day-agile-scrum-training-chennai-02/ March 28– 1-Day training on Agile & Scrum in Mumbai http://agile.conscires.com/1-day-agile-scrum-training-mumbai-01/ March 30– 1-Day training on Agile & Scrum in Delhi http://agile.conscires.com/1-day-agile-scrum-training-delhi-01/
Upcoming Certified Trainings - India April 2-3– Certified ScrumMaster Training in Bangalore http://agile.conscires.com/csm-training-bangalore-01/ April 5-6– Certified ScrumMaster Training in Chennai http://agile.conscires.com/csm-training-chennai-01/ April 9-10– Certified ScrumMaster Training in Hyderabad http://agile.conscires.com/csm-training-hyderabad-01/ May 14-15– Certified ScrumMaster Training in Delhi http://agile.conscires.com/csm-training-delhi-01/ May 17-18– Certified ScrumMaster Training in Mumabi http://agile.conscires.com/csm-training-mumbai-01/
Thank you ! More Resources at http://agile.conscires.com/suggested-reading-list-and-resources/ Contact Info Bachan Anand [email_address] 949-232-8900 http://www.linkedin.com/in/bachan

Introduction to agile scrum

  • 1.
    Scrum Intro What’sin it for me? Please dial into +1 (646) 558-2123 ACCESS CODE: 479-408-170 Prepared by Bachan Anand
  • 2.
    Agenda Overview ofAgile and Scrum Scrum: Vision and Product Scrum: Sprint What’s in it for me Please dial into +1 (646) 558-2123 ACCESS CODE: 479-408-170
  • 3.
    Overview of Agileand Scrum Please dial into +1 (646) 558-2123 ACCESS CODE: 479-408-170
  • 4.
    Overview of Agileand 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 Please dial into +1 (646) 558-2123 ACCESS CODE: 479-408-170
  • 5.
    Overview of Agileand 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 Please dial into +1 (646) 558-2123 ACCESS CODE: 479-408-170
  • 6.
    Overview of Agileand 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)
  • 7.
    Overview of Agileand 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
  • 8.
    Overview of Agileand Scrum What is Scrum Scrum is an Agile framework that supports lightweight processes that emphasize: Incremental deliveries Quality of Product Continuous improvement Discovery of people’s potential Scrum is simple to understand, but requires discipline in order to be successful Scrum is not a methodology
  • 9.
    Overview of Agileand Scrum Foundations of Scrum Empiricism Detailed up-front planning and defined processes are replaced by just-in-time Inspect and Adapt cycles Self-Organization Small teams manage their own workload and organize themselves around clear goals and constraints Prioritization Do the next right thing Rhythm Allows teams to avoid daily noise and focus on delivery Collaboration Leaders and customers work with the Team, rather than directing them
  • 10.
    Overview of Agileand Scrum Core Values Transparency Everything about a project is visible to everyone Commitment Be willing to commit to a goal 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
  • 11.
    Scrum: Vision andProduct Please dial into +1 (646) 558-2123 ACCESS CODE: 479-408-170
  • 12.
    Scrum: Vision andProduct Vision A goal to aspire to Can be summarized in a short statement of intent Communicate it to the team Please dial into +1 (646) 558-2123 ACCESS CODE: 479-408-170
  • 13.
    Scrum: Vision andProduct 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) Please dial into +1 (646) 558-2123 ACCESS CODE: 479-408-170
  • 14.
  • 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
  • 16.
    Scrum: Sprint Role:Team Cross-Functional 4-8 Members Self-Organizing Focused on meeting Commitments
  • 17.
    Scrum: Sprint Role:Relationships
  • 18.
  • 19.
    Scrum: Sprint Flow& Artifacts: Planning Sprint Planning meeting held at beginning of each Sprint Time and Resources 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 Story points may be refined
  • 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
  • 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 self-organization, and collaboration
  • 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
  • 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
  • 24.
    What is init 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
  • 25.
    What is init for me? (Leadership) As a Leader , I want To understand progress in terms of real progress made on product . Better engaged & accountable team 
  • 26.
    What is init 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
  • 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
  • 28.
    How do you learn Scrum ? Experiential Training
  • 29.
    User groups /CommunitiesAPLN – Agile Project Leadership Network Scrum Alliance – Scrum User Groups Online User Groups Scrum Alliance
  • 30.
  • 31.
  • 32.
    Scrum is alightweight 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
  • 33.
    1-Day Trainings inMarch 2012 - India March 2– 1-Day training on Agile & Scrum in Bangalore http://agile.conscires.com/1-day-agile-scrum-training-bangalore-02/ March 9– 1-Day training on Agile & Scrum in Hyderabad http://agile.conscires.com/1-day-agile-scrum-training-hyderabad-01/ March 23– 1-Day training on Agile & Scrum in Chennai http://agile.conscires.com/1-day-agile-scrum-training-chennai-02/ March 28– 1-Day training on Agile & Scrum in Mumbai http://agile.conscires.com/1-day-agile-scrum-training-mumbai-01/ March 30– 1-Day training on Agile & Scrum in Delhi http://agile.conscires.com/1-day-agile-scrum-training-delhi-01/
  • 34.
    Upcoming Certified Trainings- India April 2-3– Certified ScrumMaster Training in Bangalore http://agile.conscires.com/csm-training-bangalore-01/ April 5-6– Certified ScrumMaster Training in Chennai http://agile.conscires.com/csm-training-chennai-01/ April 9-10– Certified ScrumMaster Training in Hyderabad http://agile.conscires.com/csm-training-hyderabad-01/ May 14-15– Certified ScrumMaster Training in Delhi http://agile.conscires.com/csm-training-delhi-01/ May 17-18– Certified ScrumMaster Training in Mumabi http://agile.conscires.com/csm-training-mumbai-01/
  • 35.
    Thank you !More Resources at http://agile.conscires.com/suggested-reading-list-and-resources/ Contact Info Bachan Anand [email_address] 949-232-8900 http://www.linkedin.com/in/bachan

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