Agile Beyond Scrum

Agile: From Concept to High Performance

who is this guy?andersonmouriques@gmail.com

linkedin.com/in/andersonmouriques

@aouriques

ANDERSON MACHADO OURIQUESSoftware Development Manager

● Over 15 years of experience in Software Development○ 1 year of software development for desktops○ 8 years of software development for web○ 6 years of management

Certified

My ElePHPants

Agile Manifesto - Values

Individuals and interactions over processes and toolsWorking Software over comprehensive documentation

Customer Collaboration over contract negotiationResponding to Change over following a plan

Agile Manifesto - Principles● Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.● Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.● Deliver Working Software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.● Business people and developers must work together daily throughout the project.● build projects around motivated individuals. Give them the environment and support they need, and trust

them to get the job done.● The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.● Working software is the primary measure of progress.● Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace

indefinitely.● Continuous attention to technical excellence and good design enhances agility.● Simplicity - the art of maximizing the amount of work not done - is essential.● The best architectures, requirements, and designs emerge from self-organizing teams.● At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

● Extreme Programming● Scrum● Kanban● ScrumBan● Feature Driven Development● Lean Software Development● Dynamic Systems Development Method

Agile Methods● Agile Unified Process● Crystal Clear● Rapid Application Development● Agile Modeling● Adaptive Software Development● Disciplined Agile Delivery● Business Analyst Designer Method

Extreme Programming

Agile Methods: Theories, Principles and Core Values

TransparencyInspectionAdaptationOpenness

FocusCourageCommitmentRespect

ScrumTransparencyBalanceAgreement

RespectUnderstandingLeadership

Customer FocusFlow

Kanban

Collaboration

SimplicityCourage

RespectCommunication

Extreme Programming

Agile Methods: Theories, Principles and Core Values

TransparencyInspectionAdaptationOpenness

FocusCourageCommitmentRespect

ScrumTransparencyBalanceAgreement

RespectUnderstandingLeadership

Customer FocusFlow

Kanban

Collaboration

SimplicityCourage

RespectCommunication

PDCA (Plan - Do - Check - Act)

Extreme Programming (XP)

XP Practices

Kanban - Taiichi Ohno (TOYOTA)

Bottlenecks

WIP Limit

Visibility

Value Stream Map (example)

Minimum Viable Product

Scrum - What is it?

A framework within which people can address complex adaptive problems, while productively and

creatively delivering products of the highest possible value.

Scrum - Another Agile Framework

Scrum

Scrum - Pigs And Chicken

The Product Owner is the sole person responsible for managing the Product Backlog: ● Clearly expressing Product Backlog items;● Ordering the items in the Product Backlog to best achieve goals and missions;● Optimizing the value of the work the Development Team performs;● Ensuring that the Product Backlog is visible, transparent, and clear to all, and

shows what the Scrum Team will work on next; and,● Ensuring the Development Team understands items in the Product Backlog to the

level needed.

Scrum Roles - Product Owner

“from the short list of things a team needs a product owner to be: business value driver, vision keeper, daily decision maker, heat

shield, and the one ultimately responsible.”Lyssa Adkins

Scrum Roles - Product Owner

The Scrum Master is responsible for ensuring Scrum is understood and enacted. Scrum Masters do this by ensuring that the Scrum Team adheres to Scrum theory, practices, and rules. The Scrum Master is a servant-leader for the Scrum Team. ● Coach● Facilitator● Guardian of Quality and Performance● Remove Impediments

Scrum Roles - ScrumMaster

● Scrum/Agile Voice To All● Focused in Productivity● Build High Performance Teams

The Development Team consists of professionals who do the work of delivering a potentially releasable Increment of “Done” product at the end of each Sprint.● Self-Organized● Cross-Functional● Developers (no titles)● Accountable

Scrum Roles - Team

● Commitment● Focus● Skilled Members

Scrum Artifacts - Product Backlog

Themes

Epics

User Stories

Scrum Artifacts - Sprint Backlog

Scrum Artifacts - Increment or Burn-Down/Up Chart

Scrum Events - The Sprint

● Timeboxed from 1 to 4 weeks● No changes are made that would endanger the Sprint Goal;● Quality goals do not decrease; and,● Scope may be clarified and re-negotiated between the Product

Owner and Development Team as more is learned. (Grooming or Refinement)

● Timeboxed to 2 hours per week sprint● What can be delivered in the Increment resulting from the

upcoming Sprint? (Planning 1)● How will the work needed to deliver the Increment be achieved?

(Planning 2)

Scrum Events - Sprint Planning

● Timeboxed to 15 minutes per day● What did I do yesterday that helped the Development Team meet the

Sprint Goal?● What will I do today to help the Development Team meet the Sprint

Goal?● Do I see any impediment that prevents me or the Development Team

from meeting the Sprint Goal?

Scrum Events - Daily Scrum

● Timeboxed to 1 hour per week Sprint● P.O. Presents what is done and what is not done● Dev Team Discusses what went well, what problems they faced and how they

solved them.● The Dev Team Demonstrates the work done and answers questions.● Group collaborates on what to do next.● Backlog Refinement and Review of the timeline, budget, Potential

capabilities, and marketplace for the next anticipated release

Scrum Events - Sprint Review

● Timeboxed to 45 minutes per week Sprint● Inspect how the last Sprint went with regards to people, relationships,

process, and tools;● Identify and order the major items that went well and potential

improvements; and,● Create a plan for implementing improvements to the way the Scrum Team does

its work.

Scrum Events - Sprint Retrospective

Scrum EstimationPlanning Poker

T-Shirt Size

● Ideal Days● Story Points● Delphi

Agile Process

http://knowledge21.org

What else? BusinessLean Startup P.O. Techniques

OrganizationLean Kanban Management 3.0

Leadership Scaling Agile

TeamFacilitation Leadership Lean Kanban

TechniqueAutomated

TestsContinuous

DeliveryObject

Orientedhttp://knowledge21.org

Agility Health Radar

http://agiletransformation.com/