agile scrum training process

Download Agile Scrum Training Process

Post on 18-Jan-2017

365 views

Category:

Technology

0 download

Embed Size (px)

TRANSCRIPT

  • Agile Scrum Process2016

  • Introduction

    Traditional Methodologies

    Agile Methodology

    Scrum

    Scrum Framework: Roles

    Scrum Framework: Ceremonies

    Scrum Framework: Artifacts

    Clarion Scrum Process-Review

  • Traditional Methodologies: Waterfall Model

    You complete one phase (e.g. design) before moving on to the next phase(e.g. development)

    You rarely aim to re-visit a phase once its completed. That means, you better get whatever youre doing right the first time!

  • Traditional Methodologies: Waterfall Model

    You dont realize any value until the end of the project

    You leave the testing until the end

    You dont seek approval from the stakeholders until late in the day

    Takes too long

    **This approach is highly risky, often more costly and generally less efficient than Agile approaches

    Takes too long

    Changes

    Skipped

  • Agile Meaning (Literally)Ability to move quickly and easily.

  • Agile Methodology

    Not a process, it's a philosophy or set of values

    Rapid Adaptive Agile Quality-Driven Cooperative Iterative

  • Process and tools

    Comprehensive documentation

    Following a plan

    Contract negotiation

    Agile Manifesto

    Individuals and interactions

    Working software

    Customer collaboration

    Responding to change

    OVER

  • 12 Agile Principles

    Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.

    1 ROI

  • 12 Agile Principles

    Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.

    2 CHANGEABILITY

  • 12 Agile Principles

    Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.

    3 GETTING REAL

  • 12 Agile Principles

    Business people and developers must work together daily throughout the project.

    4 ALIGNMENT

  • 12 Agile Principles

    Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.

    5 SELF ORGANIZATION

  • 12 Agile Principles

    The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

    6 BANDWIDTH

  • 12 Agile Principles

    Working software is the primary measure of progress.

    7 DONE

  • 12 Agile Principles

    Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

    8 SUSTAINABILITY

  • 12 Agile Principles

    Continuous attention to technical excellence and good design enhances agility.

    9 IMPROVEMENT

  • 12 Agile Principles

    Simplicity the art of maximizing the amount of work not done is essential.

    10 KEEP IT SIMPLE, STUPID (KISS)

  • 12 Agile Principles

    The best architectures, requirements, and designs emerge from self-organizing teams.

    11 EMERGE

  • 12 Agile Principles

    At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

    12 INSPECT & ADOPT

  • Various Agile Methodologies

  • Meaning Of Scrum (Literally)

  • What Is Scrum?

    Scrum is an agile framework that allows us to focus on delivering the highest business value in the shortest time.

    It allows us to rapidly and repeatedly inspect actual working software (every two weeks to one month).

    The business sets the priorities. Teams self-organize to determine the best way to deliver the highest priority features.

    Every two weeks to a month anyone can see real working software and decide to release it as is or continue to enhance it for another sprint.

  • Scrum Origins

    Controversies

    Some professionals believe that Jeff Sutherland, John

    Scumniotales and Jeff McKenna invented Scrum

    in 1993.

    Others, who vouch for HirotakaTakeuchi and

    IkujiroNonakaas inventing Scrum in 1986.

  • Who Is Using Scrum?

    Electronic Arts

    Lockheed Martin

    Microsoft

    Google

    Siemens Capital

    One

    Ipswitching Sabre BBC

    High Moon Studios

    Turner Broadcasting

    First American Real Estate

    Nielsen Media

    Lexis Nexis

    Salesforce.comAmazon

    Yahoo

    BMC Software

    John Deere Time Warner

    Clarion Technologies

  • Where To Use Scrum?

    Commercial software

    In-house development

    Contract development

    Fixed-price projects

    Financial applications

    ISO 9001-certified applications

    Embedded systems

    24x7 systems with 99.999% uptime requirements

    The Joint Strike Fighter

    Video game development

    FDA-approved, life-critical systems

    Satellite-control software

    Websites

    Handheld software

    Mobile phones

    Network switching applications

    ISV applications

    Some of the largest applications in use

  • Scrum Framework

    Product owner

    Scrum Master

    Team

    Roles

    Sprint planning

    Sprint review

    Sprint retrospective

    Daily scrum meeting

    Ceremonies

    Product backlog

    Sprint backlog

    Burndown charts

    Artifacts

  • Scrum Framework

    Product owner

    Scrum Master

    Team

    Roles

    Sprint planning

    Sprint review

    Sprint retrospective

    Daily scrum meeting

    Ceremonies

    Product backlog

    Sprint backlog

    Burndown charts

    Artifacts

  • Role: Product Owner

    Define the features of the product

    Decide on release date and content

    Be responsible for the profitability of the product (ROI)

    Prioritize features according to market value

    Adjust features and priority every iteration, as needed

    Accept or reject work results

  • Role: Scrum Master

    Represents management to the project

    Responsible for enacting Scrum values and practices

    Removes impediments

    Ensure that the team is fully functional and productive

    Enable close cooperation across all roles and functions

    Shield the team from external interferences

  • Role: The Team

    Typically 5-9 people

    Cross-functional Programmers, testers, user experience designers, etc.

    Members should be full-time May be exceptions (e.g., database administrator)

    Teams are self-organizing Ideally, no titles but rarely a possibility

    Membership should change only between sprints.

  • Clarion Role Mapping

    Product owner/Shadow product owner

    Scrum master

    Cross functional scrum team

    Product owner is generally from client side and shadow product owner would be from BA/SA offshore side. In some cases product owner could be from offshore, who has gained detailed product/system knowledge, this scenario does not require Shadow PO.

    Team facilitator from offshore side to drive overall scrum process

    Technical Architect (onsite + offshore), Technical Leader, QA, Developers and Designers.

    Scrum Master

    PO PO

    Cross-functional scrum team

  • Scrum Framework

    Product owner

    Scrum Master

    Team

    Roles

    Sprint planning

    Sprint review

    Sprint retrospective

    Daily scrum meeting

    Ceremonies

    Product backlog

    Sprint backlog

    Burndown charts

    Artifacts

  • Ceremony: Sprint Planning Meeting

    Team selects items from the product backlog they can commit to completing

    Sprint backlog is created Tasks are identified and each is estimated (1-16 hours)

    Collaboratively, not done alone by the Scrum Master

    High-level design is considered

  • Clarion: Sprint Planning Meeting

    Purpose: At every sprint start, sprint backlog is created out of product backlog.

    Participants: Product owner, scrum master, team

    Duration: This is a time-boxed meeting, duration depends on the duration of sprint and complexity of the items.

    Highlights: Fibonacci point based estimates which would be related to the complexity / time of

    the tasks.

    Stories are discussed in sprint planning meeting and estimation will be given by developers on based of story, planning poker is used for the user story estimation.

    Generally for 1 point we consider 2-3 hours work, 2 pointer it is a half day work, 3 pointer is a days work and 5 pointer is 2 days work.

  • Planning Poker

    Product Owner reads story

    Team estimates (including QA/Testing)

    Team Discusses

    Team estimates again

    This process is repeated till consensus is reached.

    PO

    ... ..

    5

    3

    1

  • Clarion Pre-sprint Planning Meeting

    Happens a day before actual Sprint planning meeting.

    All the internal team members participate.

    Few the tentative stories are picked from the prioritized product backlog.

    Team discuss and understands the stories and the underlying challenges and questions in the upcoming stories.

    For the new team it is suggested to do the point estimation also during pre-sprint planning.

    The purpose is to facilitate the main Sprint planning with client.

  • Ceremony: Daily Standup

    Parameters Daily

    15-minutes

    Stand-up

    Not for problem solving Whole world is invited

    Only team members, Scrum Master, Product Owner, can ta