little a versus big a agile - qai quest intention or purpose sunday, april 21, 13 14. ......

Little ‘a’ Versus

Big “A” AgileA Focus on Intent

Jim and Melissa Yorkwww.FoxHedgeLtd.com

“Signalled Intent” © Carine06 / Wikimedia Commons / cc-by-sa-2.0

1Sunday, April 21, 13

Content © FoxHedge Ltd

Who We Are

Melissa YorkPrinciple

[email protected]

Jim YorkPrincipleCoach

[email protected]

FoxHedge Ltdwww.FoxHedgeLtd.com



What We Do

CoachingCoaching leaders to build effective teams and productsLearning on your terms, focusing on the problems you want to solve. Dealing with the real challenges building products in your business environment. On-site coaching for your teams and the people who lead and support them.

Training Teaching individuals and teams in dynamic, interactive workshops

• Certified ScrumMaster• Certified Product Owner• Agile Team Workshop• Starting Your Agile Project• Lean and Agile Orientation• Executive Agile Orientation• Agile Requirements, Planning,

and Estimation



Upcoming ClassesCertified ScrumMaster

16-17 May - Bethesda, MD19-20 June - Arlington, VA

18-19 July - Frederick, MD

Certified Scrum Product Owner22-23 April - Reston, VA

17-18 June - Arlington, VA11-12 September - Dulles, VA

Quest attendees can get $100 off Early Bird and Regular registration prices for these classesUse promotional code “Quest2013”

www.FoxHedgeLtd.com



There’s a Whole Lot of Something Going On

FragileAgilefall

ScrumButChaos!



Sources of Confusion?

Charlatans

Snake Oil Salesmen

Experts?Tools?



Dispelling an Agile MythReality

It’s a mindset, supported by practices, which enables you to react in a timely and appropriate way to change.

Agile is a Methodology!

Myth



ScrumA team-based framework for accomplishing creative work

For Example



Scrum Delivery Cycle



Scrum Delivery Cycle with Practices

Modeling

User Stories

Standup

Review

Retrospectives

Points

Small team

Sit Together

Customer in the Room

DoD

Pair Programming

TDD

Frequent Integration

Automated Testing

1-click Build & Deploy

PrioritizationEmpowered

Team

Adaptive Planning

Release PlanningSustainable Pace

YAGNI

Information Radiator



Shu Ha Ri




Agility




Mastery

“It takes time to become an expert. Even the most gifted performers need a minimum of ten years of intense training before they win international competitions.”

-- K. Anders Ericsson, Michael J. Prietula, and Edward T. Cokely, ”The Making of an Expert”, Harvard Business Review, July-August 2007 (Reprint R0707)



in𐄁tent |inˈtent|nounintention or purpose



What are thecauses of failure?



What are theenablers of success?



Some EssentialSuccess Factors




Start with the Problem!




Create Shared Understanding




Effective Leadership




Customer wants what we’re working on, now!




Customer is willing and able to engage with the team


Jim’s 80/5 Guideline forProduct Owner Engagement

The Product Owner must ensure that 80% of the Scrum Development Team’s questions are answered within 5 minutes of the question being raised.



Willingness and ability to take appropriate and timely action based on feedback




Perils and Pitfallsversus Intent




Reviews

• Proof through Demonstration• Feedback• Leads to adaptation• Open to right audience• It’s about the product

Intent• Facade or report• One-way• Feedback absent or

ignored• Customer and other

stakeholders absent• 1st time PO has seen

completed features

Here be dragons!



Retrospective

• Inspection• Causes• Improvements• It’s about the process• Team

Intent• Gripe session• Excuses• Complacency• Blaming people• Heroes & villains

Here be dragons!



Points

• Measure capacity•Work to capacity• Set expectations• Re-plan based on actual

completion rate

Intent• Measure productivity• Measure improvement• Compare teams• Roll up from multiple

teams• Ignoring velocity

projection

Here be dragons!



Workshop Exercise



•acceptance tests•adaptive planning•Agile Champion•automated build

and deploy•automated

testing•backlog•Boot Camp•Boundaries•Build Quality In•Burn Chart•Business Value

Analysis•Center of

Excellence•Co-location•Coach•coding standards•Collective Code

Ownership•Conditions of

Satisfaction•Constraints•Containers•Continuous

Integration•Core Team

•Cross-functional team

•Customer Acceptance TDD

•customer feedback

•customer-in-the-room

•Cycle time•daily meeting•dedicated team•definition of done•eliminate waste•Empowered Team•Enterprise

Transition Team•Evolutionary

Architecture•Evolutionary

Design•Fast Delivery•Feedback•Flow•frequent

feedback loops•frequent

integration•Goal

•Impediment List•incremental

development•Information

Radiator•Innovation

Games•Iteration Planning

Meeting•Iterations•just enough, just-

in-time requirements

•Kanban•Management

Tests•Minimum

Meaningful Feature Set

•Muda•One Team•Open Workspace•pair programming•Pareto (80/20)•Pay as you go•Personas•Pigs and

Chickens

•Pilots Projects•Planning Poker•prioritized

backlog•Product Lifecycle•Product Owner•Quality Criteria•Reduce Waster•refactoring•regression testing•Regular Cadence•Relative

Estimation•Release Often•retrospectives•Review•Scrum

Development Team

•Scrum of Scrums•Scrum Roles•ScrumMaster•Self-Organizing

Team•shared goal•Shared Vision•Simple Design

•single business decision maker

•Sit Together•small releases•Spikes•Sprint Backlog•Sprint Review•Stakeholder

Analysis•Story Points•Success Criteria•sustainable pace•Swarming•Test First

Development•Theory of

Constraints•timeboxes•Tune Up•unit-level TDD•user stories•Velocity•Whole team•Working Software•YAGNI

Practices



Q & A

1539 Carta Marina by Olaus Magnus, James Ford Bell Library

Here Be

Dragons“Signalled Intent” © Carine06 / Wikimedia Commons / cc-by-sa-2.0



Contact Info


little a versus big a agile - qai quest intention or purpose sunday, april 21, 13 14. ......

Documents