Click here to load reader

Introducing agile-software-deveopment-with-scrum

  • View
    120

  • Download
    0

Embed Size (px)

Text of Introducing agile-software-deveopment-with-scrum

  • Agile Development with ScrumGloria StoilovaScrum Product Owner

    *

  • OutlineWhat is Scrum?The Scrum TeamThe Scrum EventsThe Scrum ArtifactsOrganizational Impacts of ScrumWho uses Scrum Resources

    *

  • What is Scrum? Scrumis a framework for dealing with complex work such as software product development. Its an alternative to traditional approaches known and used so far in manufacturing and construction.

    *

  • The meaning of ScrumA rugby scrum restarts a rugby game after a minor infringement of the rules. Understand what goes on. Who puts in? How do you win?

  • Rugby Scrum 101

    Instead of "Pause, Engage" the match official will simply call "Set".Putting in the ballScrumagingScrummaging is the very "technical" area of the game

  • . Scrum is a flexible,holisticproduct development framework within which you can employ various processes and techniques based on Empirical approach.It is where a development team: works as an unit to reach a common goal, challenges assumptions of the "traditional, sequential approach" to product Development, Scrum introduces feedback loops, encouraging us to inspect and adapt the product that we are building and the processes were using to build that productEnables teams to self-organize by encouraging physical co-location or close online collaboration of all team members, as well as daily face-to-face communication among all team members and disciplines in the project.

    SCRUM definition:

  • Scrum roles, Scrum events, Scrum artifacts, and the Scrum rules that bind them together. Scrum is: LightweightSimple to understand(but) Difficult to master

    Scrum brings challenges to individuals, teams, and organizations. It is an attempt to put chaos in a box, making the most of uncertainty. SCRUM definition consists of:

  • SCRUM framework:Scrum provides a structure of Roles, Artifacts, Meetings and Rules .

    *

  • Three pillars uphold every implementation of empirical process control: transparency, inspection, and adaptation.

    Transparency - Significant aspects of the process must be visible to those responsible for the outcome. Those performing the work and those accepting the work product must share common definition of DONE. Inspection - Scrum users must frequently inspect Scrum artifacts and progress toward a Sprint Goal to detect undesirable variances. Adaptation - If an inspector determines that one or more aspects of a process deviate outside acceptable limits, and that the resulting product will be unacceptable, the process being used must be adjusted. An adjustment must be made as soon as possible to minimize further deviation.Scrum prescribes 4 formal inspections and adaptations Sprint planning, Daily Scrum, Sprint review, Sprint retrospective.

  • Please dont go there. There are obstacles waiting. But why? If they are waiting, I wont let them wait long.

    *

  • Lets get serious about how Scrum works .

  • I said Serious!!!

  • PRODUCT OWNER SCRUM DEV TEAMSCRUM MASTER

  • The Scrum RolesProduct OwnerScrum MasterBusiness owner / stakeholderStakeholders

    Scrum Team

    QA/TestingDevelopers

    Or Scrum Product OwnerStakeholders

    *

  • Stakeholders (Business owners) Anybody whose interest is positively or negatively affected by the project OR who can exert an influence on the project. Examples of Stakeholders in Scrum Project: Team (Product Owner, Scrum Master, Developers) Management Customers End usersVendors/Contractors or external contributors

  • Scrum development team The team model in Scrum is designed to optimize flexibility, creativity, and productivity.Scrum Teams deliver products iteratively and incrementally, maximizing opportunities for feedback. Incremental deliveries of Done product ensure a potentially useful version of working product is always available.

  • The Scrum Development Team (DT) Self-organizing and cross-functional group of 4 to 7 professionals that choose how best to accomplish their work and build a potentially shippable increment fulfilling the definition of Done at the end of each Sprint. DT is structured and empowered to be self-organizing, manage their own work & continuously improving their overall efficiency and effectiveness. Team determines how to transform Product Backlog Items into shippable functionalities;

    *

  • Scrum recognizes no titles for DT members other than DEVELOPER, regardless of the work being performed by the person; there are no exceptions to this rule!!! Scrum recognizes no sub-teams in the DT, regardless of particular domains that need to be addressed, like testing or BA; there are NO exceptions of this rule!!!Accountability belongs to The Team as a whole no matter that DT members may have specialized skills and areas of focus.

    Important notes in regards DTs work:

  • Product Owner (further PO) PO is the sole person responsible for ROI of development effort.PO is managing the Product Backlog (further PB) Responsible for product vision, clearly expressing PB items, Ordering the items in the PB to best order to achieve goals and missions;Optimizing the value of the work the Development team (further DT) performs;Ensuring that the PB is visible, transparent, and clear to all, and shows what the DT will work on next;Ensuring the DT understands items in the PB to the level needed to perform their work. Represents stakeholder interests, but remains accountable; Plans product releases and maintains product roadmap;ONE person, not a committee!!!;Ultimately responsible for products success.

    *

  • Important notes in regards Pos work: For the Product Owner to succeed, the entire organization must respect his/her decisions; The Product Owners decisions are visible in the content and ordering of the PBNo one is allowed to tell the DT to work from a different set of requirements; The DT is NOT allowed to act on what anyone else says.The PO may represent the desires of a committee in the PB, but those who want to change a PB items priority must address the PO.

  • The Scrum Master (or the most misunderstood and neglected role in Scrum)Manages relationship between Product Owner and rest of the team.Ensures Scrum is understood and Scrum theory, practices and rules are enacted. SM is a servant-leader for the Scrum Team, he/she acts as coach, fixer, and gatekeeper;A leadership role rather than managerial; Plans individual Sprints together with team members;Facilitates all of the Scrum events;

    *

  • Scrum Master protects the team from distractions and interruptions! I will protect you from that bad wolf and his endless ideas!

    Gloria (G) - formula for Tylor expansion

  • Scrum Master Service to the Development Team. Helps resolve impediments.Creates an environment conducive to team self-organization.Facilitates the processes, helps ppl use Scrum.Shields the team from external interference and distractions to keep it in group flow (a.k.a. the zone).Enforces time-boxes.Keeps Scrum artifacts visible.Promotes improved engineering practices.And somehow does all this with NO management power over the team

  • The Scrum Product Owner (or the hybrid breed in Scrum Roles )The Scrum Product Owner serves the organization and the Development team as one fully operational PO plus all the above mentioned for SM and in several additional ways:Leading and coaching the organization in its Scrum adoption; Planning Scrum implementations within the organization; Helping employees and stakeholders understand and enact Scrum and empirical product development;Causing change that increases the productivity of the Scrum Team; and, Working with other Pos to increase the effectiveness of the application of Scrum in the organization.

  • Scrum EventsPrescribed events are used in Scrum to create regularity and to minimize the need for meetings not defined in Scrum.All events are time-boxed events, as every event has a maximum duration. Once a Sprint begins, its duration is fixed and cannot be shortened or lengthened. Other than the Sprint itself, which is a container of all other events, each event in Scrum is a formal opportunity to inspect and adapt something. The events are specifically designed to enable critical transparency and inspection. Failure to include any of these events results in reduced transparency and is a lost of opportunity to inspect and adapt.

    *

  • The Sprint contains and consists of: The Sprint Planning, The Daily Scrums, The development work; The Sprint Review, The Sprint Retrospective.

    *

  • Consistent duration throughout project (2 4 weeks); Team composition and quality goals remain constant (5 7 people);No changes made that affect Sprint Goal!!!;Scope can be clarified or re-negotiated as more is learned (new backlog entry is created);Risk is limited to cost of one sprint.Scope may be clarified and re-negotiated between the PO and the DT as more is learned.

  • How Sprints work?

    24 HourstaskExpanded tasks

    taskEstimated taskincrementDaily Scrum meetingSprint Backlog

    Product BacklogPotentially shippable product14 DaystasktasktaskEstimated task

    tasktask

    *

  • How a Sprint looks like?

    Kind of like this

  • Sprint Planning MeetingTime-boxed meeting to determine work to be done in 1 Sprint 4 h. max. First event of every Sprint.Answers What will be delivered in this Sprint?Answers How the work will be achieved?

    *

  • !!!

  • Daily Scrum (Standup)Daily meeting within 15 min. time-box (max).Each team member answers three questions:What did I do yesterday?What will I do today?What obstacles are in the way?

Search related