Kanban vs Scrum Making the most of both

Save this PDF as:
 WORD  PNG  TXT  JPG

Size: px
Start display at page:

Download "Kanban vs Scrum Making the most of both"

Transcription

1 Kanban vs Scrum Making the most of both QCon, San Francisco Nov 18, 2009 Henrik Kniberg Agile/Lean Crisp, Stockholm Background: developer, manager, entreprenuer Board of directors

2 Purpose of this presentation To clarify Kanban and Scrum by comparing them...so you can figure out how these may come to use in your context. Henrik Kniberg 2

3 Scrum in a nutshell Split your product Split your organization Optimize business value Large group spending a long time building a huge thing Small team spending a little time building a small thing... but integrating regularly to see the whole Optimize process $$$ Split time January April $ Henrik Kniberg 3

4 Typical Scrumboard Henrik Kniberg 4

5 The bottom line If you achieve these you can ignore the rest of the checklist. Your process is fine. Delivering working, tested software every 4 weeks or less Delivering what the business needs most Process is continuously improving Clearly defined product owner (PO) PO is empowered to prioritize PO has knowledge to prioritize PO has direct contact with team PO has direct contact with stakeholders PO speaks with one voice (in case PO is a team) Team has a sprint backlog Highly visible Updated daily Owned exclusively by the team Daily Scrum happens Whole team participates Problems & impediments are surfaced Demo happens after every sprint Shows working, tested software Feedback received from stakeholders & PO Have Definition of Done (DoD) DoD achievable within within each sprint each Henrik iteration Kniberg Team members sit together experimenting with the process 5 Team respects DoD Core Scrum These are central to Scrum. Without these you probably shouldn t call it Scrum. Retrospective happens after every sprint Results in concrete improvement proposals Some proposals actually get implemented Whole team + PO participates PO has a product backlog (PBL) Top items are prioritized by business value Top items are estimated Estimates written by the team Top items in PBL small enough to fit in a sprint PO understands purpose of all backlog items Have sprint planning meetings PO participates PO brings up-to-date PBL Whole team participates Results in a sprint plan Whole team believes plan is achievable PO satisfied with priorities Timeboxed iterations Iteration length 4 weeks or less Always end on time Team not disrupted or controlled by outsiders Team usually delivers what they committed to Max 9 people per team the unofficial Scrum Checklist Recommended but not always necessary Most of these will usually be needed, but not always all of them. Experiment! Scaling Team has all skills needed to bring backlog items to Done Team members not locked into specific roles Iterations that are doomed to fail are terminated early PO has product vision that is in sync with PBL PBL and product vision is highly visible Everyone on the team participates in estimating PO available when team is estimating Estimate relative size (story points) rather than time Whole team knows top 1-3 impediments SM has strategy for how to fix top impediment SM focusing on removing impediments Escalated to management when team can t solve Team has a Scrum Master (SM) SM sits with the team These are pretty fundamental to any Scrum scaling effort. You have a Chief Product Owner (if many POs) Dependent teams do Scrum of Scrums Dependent teams integrate Henrik Kniberg PBL items are broken into tasks within a sprint Sprint tasks are estimated Estimates for ongoing tasks are updated daily Velocity is measured All items in sprint plan have an estimate PO uses velocity for release planning Velocity only includes items that are Done Team has a sprint burndown chart Highly visible Updated daily Daily Scrum is every day, same time & place PO participates at least a few times per week Max 15 minutes Each team member knows what the others are doing Positive indicators Leading indicators of a good Scrum implementation. Having fun! High energy level. Overtime work is rare and happens voluntarily Discussing, criticizing, and PO = Product owner SM = Scrum Master PBL = Product Backlog DoD = Definition of Done Version 2.1 ( )

6 Typical waterfall => Scrum evolution 1. Waterfall 2. Scrum But 3. Scrum Requirements Requirements PO Feature team 1 Feature team 2 Design Design & code Code Test Test Henrik Kniberg 6

7 Kanban in a nutshell Visualize the workflow Limit WIP (work in progress) Measure & optimize flow To do Dev Test Release H K G D FLOW C Done! A B Useful starting point for more info: 7

8 Roots of Kanban 看 板 Kan Ban Visual Card Buyer Supplier Consume Detach Receive Ship Allocate Manufacture The two pillars of the Toyota production system are just-in-time and automation with a human touch, or autonomation. The tool used to operate the system is kanban. Taiichi Ohno Father of the Toyota Production System Henrik Kniberg 8

9 Kanban in software development Henrik Kniberg 9

10 Typical Scrum => Kanban evolution Scrum step 1 Scrum step 2 Scrum + Kanban Feature Feature Feature Feature Feature Feature team 1 team 2 team 2 team 1 team 2 team 2 Scrum Scrum Scrum Scrum Scrum Scrum Feature team 1 Feature team 2 Feature team 2 Scrum Scrum Scrum Operations / support team Scrum Operations / support team Kanban Henrik Kniberg 10

11 Tool anything used as a means of accomplishing a task or purpose. -dictionary.com Physical tools Thinking tools a.k.a. mindsets or philosophies Lean Agile Systems Thinking Theory of Constraints Toolkits a.k.a. frameworks Scrum RUP XP Kanban Process tools a.k.a. organizational patterns Product Owner role Pair programming Visualize the workflow To do Dev Test Release H D C G K Done! A B Henrik Kniberg 11 FLOW

12 Can we compare Kanban and Scrum? Should we? Henrik Kniberg 12

13 Any tool can be misused The old tool was better! Never blame the tool! 13 Henrik Kniberg 13

14 Compare for understanding, not judgement More prescriptive More adaptive RUP (120+) XP (13) Scrum (9) Kanban (3) Do Whatever (0) Architecture Reviewer Business Designer Business-Model Reviewer Business-Process Analyst Capsule Designer Change Control Manager Code Reviewer Configuration Manager Course Developer Database Designer Deployment Manager Design Reviewer Designer Graphic Artist Implementer Integrator Process Engineer Project Manager Project Reviewer Requirements Reviewer Requirements Specifier Software Architect Stakeholder System Administrator System Analyst Technical Writer Test Analyst Test Designer Test Manager Tester Tool Specialist User-Interface Designer Architectural analysis Assess Viability of architectural proof-of-concept Capsule design Class design Construct architectural proof-ofconcept Database design Describe distribution Describe the run-time architecture Design test packages and classes Develop design guidelines Develop programming guidelines Identify design elements Identify design mechanisms Incorporate design elements Prioritize use cases Review the architecture Review the design Structure the implementation model Subsystem design Use-case analysis Use-case design Analysis model Architectural proof-of-concept Bill of materials Business architecture document Business case Business glossary Business modeling guidelines Business object model Henrik Business rules Kniberg Work order 14 Business use case Business use case realization Business use-case model Business vision Change request Configuration audit findings Configuration management plan Data model Deployment model Deployment plan Design guidelines Design model Development case Development-organization assessment End-user support mateirla Glossary Implementation model Installation artifacts Integration build plan Issues list Iteration assessment Iteration plan Manual styleguide Programming guidelines Quality assurance plan Reference architecture Release notes Requirements attributes Requirements management plan Review record Risk list Risk management plan Software architecture document Software development plan Software requirements specification Stakeholder requests Status assessment Supplementary business specification Supplementary specification Target organization assessment Test automation architecture Test cases Test environment configuration Test evaluation summary Test guidelines Test ideas list Test interface specification Test plan Test suite Tool guidelines Training materials Use case model Use case package Use-case modeling guidelines Use-case realization Use-case storyboard User-interface guidelines User-interface prototype Vision Workload analysis model Whole team Coding standard TDD Collective ownership Customer tests Pair programming Refactoring Planning game Continuous integration Simple design Sustainable pace Metaphor Small releases Scrum Master Product Owner Team Sprint planning meeting Daily Scrum Sprint review Product backlogt Sprint backlog BUrndown chart Miyamoto Musashi 17 th century samurai Visualize the workflow Limit WIP Measure and optimize lead time Do not develop an attachment to any one weapon or any one school of fighting

15 Distinguish the tool itself from specific usage techniques Specific patterns, techniques, best practices, etc Scrum core Kanban core Henrik Kniberg 15

16 Scrum prescribes 3 roles Product owner Team Scrum Master PO SM Henrik Kniberg 16

17 Scrum prescribes timeboxed iterations Scrum team Kanban team 1 Plan & commit week 1 week 2 week 3 week 4 week 5 week 6 week 7 week 8 Sprint 1 Review (release?) Retrospective Sprint 2 Kanban team 2 week 1 week 2 week 3 week 4 week 5 week 6 week 7 week 8 Retrospectives (4w) Planning cadence (2w) Release cadence (1w) Kanban team 3 week 1 week 2 week 3 week 4 week 5 week 6 week 7 week 8 Retrospectives (4w) Planning (on demand) Release (on demand) Henrik Kniberg 17

18 Both limit WIP, but in different ways Scrum board Kanban board To do Ongoing Done :o) A To do Ongoing Done :o) 2 A B B C C D D FLOW FLOW WIP limited per unit of time (iteration) WIP limited per workflow state Henrik Kniberg 18

19 Both are empirical Capacity (aka velocity) Lead time (aka cycle time) Quality (defect rate, etc) Predictability (SLA fulfillment, etc) Kanban is more configurable Many small teams Few large teams Great! More options! Oh no, more decisions! Low WIP limits High WIP limits Few workflow states Many workflow states Short iterations Long iterations Little planning Lots of planning... etc etc... Henrik Kniberg 19

20 Scrum discourages change in mid-iteration Scrum Wait until next sprint! Kanban PO I d like to have E! Wait until a ToDo slot becomes available! Or swap out C or D! To do C D Ongoing Done :o) A B To do 2 C D Ongoing Done :o) 2 A B FLOW FLOW Policies Henrik Kniberg 20

21 Scrum board is reset between each iteration Scrum First day of sprint Mid-sprint Last day of sprint Kanban Any day Henrik Kniberg 21

22 Scrum prescribes cross-functional teams Scrum team Kanban team 1 Kanban team 2 Cross-functional team Specialist Cross-functional team Specialist team Henrik Kniberg 22

23 Scrum backlog items must fit in a sprint Scrum Sprint 1 Sprint 2 Sprint 3 Sprint 4 Kanban WIP limit = 3 Long running task Long running task Henrik Kniberg 23

24 Scrum prescribes estimation and velocity V= 8 V= 7 V= Likely velocity: 8 per sprint (sustainable pace?) Sprint 1 Sprint 2 Sprint 3 Henrik Kniberg 24

25 Both allow working on multiple products simultaneously Scrum example 1 Green Product Yellow Product Green team Yellow team Kanban example 1 Color-coded tasks Scrum example 2 Scrum example 3 All products Cross-product team All products Cross-product team Kanban example 2 Color-coded swimlanes Henrik Kniberg 25

26 Both are Lean and Agile Agile Manifesto 1. Individuals and Interactions over Processes and Tools 2. Working Software over Comprehensive Documentation 3. Customer Collaboration over Contract Negotiation 4. Responding to Change over Following a Plan Henrik Kniberg The Toyota Way 1. Base your management decisions on a Long-Term Philosophy, Even at the Expense of Short-Term Financial Goals 2. Create Continuous Process Flow to Bring Problems to the Surface 3. Use Pull Systems to Avoid Overproduction 4. Level Out the Workload (Heijunka) 5. Build a Culture of Stopping to Fix Problems, to Get Quality Right the First Time 6. Standardized Tasks are the Foundation for Continuous Improvement and Employee Empowerment 7. Use Visual Controls So No Problems are Hidden 8. Use Only Reliable, Thoroughly Tested Technology That Serves Your People and Processes 9. Grow Leaders Who Thoroughly Understand the Work, Live the Philosophy, and Teach It to Others 10. Develop Exceptional People and Teams Who Follow Your Company s Philosophy 11. Respect Your Extended Network of Partners and Suppliers by Challenging Them and Helping Them Improve 12. Go and See for Yourself to Thoroughly Understand the Situation (Genchi Genbutsu) 13. Make Decisions Slowly by Concensus, Thoroughly Considering All Options; Implement Decisions Rapidly 14. Become a Learning Organization Through Relentless Reflection (Hansei) and Continuous Improvement (Kaizen) 26

27 Minor difference: Scrum prescribes a prioritized product backlog Scrum: Product backlog must exist Changes to product backlog take effect next sprint (not current sprint) Product backlog must be sorted by business value Kanban: Product backlog is optional Changes to product backlog take effect as soon as capacity becomes available Any prioritization scheme can be used. For example: Take any item Always take the top item Always take the oldest item 20% on maintainance items, 80% on new features Split capacity evenly between product A and product B Always take red items first Policies Henrik Kniberg 27

28 Minor difference: Scrum prescribes daily meetings... but many Kanban teams do that anyway. Henrik Kniberg 28

29 Minor difference: In Scrum, burndown charts are prescribed No specific types of diagrams prescribed in Kanban. Teams use whatever they need. Cumulative Flow Henrik Kniberg 29

30 Evolve your own unique board! Some of these photos courtesy of David Anderson, Mattias Skarin, and various other people Henrik Kniberg 30

31 Henrik Kniberg Next Analysis Development Acceptance Prod Ongoing Kanban kick-start example Done orem ipsum dolor sit orem ipsum dolor amet, co sit nse amet, ctetur co nse ctetur adi pis cing elit nisl Ongoing orem ipsum dolor sit amet, co adi pis cing elit nisl orem ipsum dolor sit amet, co nse ctetur Done Ongoing orem ipsum dolor sit amet, adi pis cing elit nisl Done version orem olor sit amet, co nse ctetur adi pis cing elit nisl orem ipsum dolor sit amet, co nse ctetur orem ipsum dolor sit amet, co nse ctetur xxxx kjd orem ipsum dj dolor d xxx sit amet, co nse ctetur orem ipsum dolor sit amet, co nse ctetur orem ipsum dolor sit amet, co nse ctetur orem ipsum dolor sit amet, co nse Definition of Done: Goal is clear First tasks defined Story split (if necessary) orem ipsum dolor sit amet, nse ctetur adi pis cing elit nisl orem ipsum dolor orem ipsum dolor sit amet, co nse sit amet, co nse ctetur ctetur Definition of Done: Code clean & checked in on trunk Integrated & regression tested Running on UAT environment Definition of Done: Customer accepted Ready for production orem ipsum dolor sit ctetur adi pis cing elit nisl Feature / story Date when added to board (description) Hard deadline (if applicable) = priority = panic Who is analyzing / testing right now Task / defect (description) (description) Why (description) (description) =task (description) = completed = blocked = who is doing this right now =defect What to pull first 1. Panicfeatures (should be swarmed and kept moving. Interrupt other work and break WIP limits as necessary) 2. Priority features 3. Hard deadline features (only if deadline is at risk) 4. Oldest features

32 Comparison: Typical Scrum board & Kanban board Scrum Product backlog E E F F G H G J M HL I K Sprint backlog Committed Ongoing B C D Done :o) A? Kanban Dev Backlog Next 3 2 Ongoing Done In production :o) H J M F L G I K D E B C A X Q R Henrik Kniberg 32

33 Scenario 1 one piece flow Dev Backlog Next 3 2 Ongoing Done In production :o) G A B C J H M F L I K D E Henrik Kniberg 33

34 Scenario 1 one piece flow Dev Backlog Next 3 2 Ongoing Done In production :o) G F H J L M I K C D E A B Henrik Kniberg 34

35 Scenario 1 one piece flow Dev Backlog Next 3 2 Ongoing Done In production :o) G F H J L M I K C D E B A Henrik Kniberg 35

36 Scenario 1 one piece flow Dev Backlog Next 3 2 Ongoing Done In production :o) G C D B A F J H M L I K E Henrik Kniberg 36

37 Scenario 1 one piece flow. Dev Backlog Next 3 2 Ongoing Done In production :o) G D C B A F J H M L I K E Henrik Kniberg 37

38 Scenario 2 Deployment problem Dev Backlog Next 3 PO 2 Ongoing Done In production :o) G A B C J H M F L I K D E Henrik Kniberg 38

39 Scenario 2 Deployment problem Dev Backlog Next 3 PO 2 Ongoing Done In production :o) G F H J L M I K C D E A B Henrik Kniberg 39

40 Scenario 2 Deployment problem Dev Backlog Next 3 PO 2 Ongoing Done In production :o) G F C D A B J H M L I K E Henrik Kniberg 40

41 Scenario 2 Deployment problem Dev Backlog Next 3 PO 2 Ongoing Done In production :o) G D C B A F J H M L I K E Henrik Kniberg 41

42 Scenario 2 Deployment problem Dev Backlog Next 3 PO 2 Ongoing Done In production :o) G F D C!? A B J H M L I K E Henrik Kniberg 42

43 Scenario 2 Deployment problem Dev Backlog Nexet 3 PO 2 G D Ongoing!? Done A B In production :o) J H M F L I K E C Henrik Kniberg 43

44 Scenario 2 Deployment problem Dev Backlog Next 3 PO 2 Ongoing Done In production :o) G D A B J H M F L I K E C Henrik Kniberg 44

45 Scenario 2 Deployment problem Dev Backlog Next 3 PO 2 Ongoing Done In production :o) G D A B J H M F L I K E C Henrik Kniberg 45

46 Scenario 2 Deployment problem Dev Backlog Next 3 PO 2 Ongoing Done In production :o) G F H J L M I K D E C A B Henrik Kniberg 46

47 One day in Kanban land Henrik Kniberg 47

48 Kanban & Scrum Comparison summary Similarities Both are Lean and Agile Both based on pull scheduling Both limit WIP Both use transparency to drive process improvement Both focus on delivering releasable software early and often Both are based on self-organizing teams Both require breaking the work into pieces In both cases the release plan is continuously optimized based on empirical data (velocity / lead time) Differences Scrum Timeboxed iterations prescribed. Team commits to a specific amount of work for this iteration. Uses Velocity as default metric for planning and process improvement. Cross-functional teams prescribed. Items broken down so they can be completed within 1 sprint. Burndown chart prescribed WIP limited indirectly (per sprint) Estimation prescribed Cannot add items to ongoing iteration. A sprint backlog is owned by one specific team Prescribes 3 roles (PO/SM/Team) A Scrum board is reset between each sprint Kanban Timeboxed iterations optional. Commitment optional. Uses Lead time as default metric for planning and process improvement. Cross-functional teams optional. Specialist teams allowed. No particular item size is prescribed. No particular type of diagram is prescribed WIP limited directly (per workflow state) Estimation optional Can add new items whenever capacity is available A kanban board may be shared by multiple teams or individuals Doesn t prescribe any roles A kanban board is persistent Henrik Kniberg Prescribes a prioritized product Prioritization is optional. 48 backlog

49 Don t be dogmatic Go away! Don t talk to us! We re in a Sprint. Come back in 3 weeks. Though Shalt Limit WIP Henrik Kniberg 49

50 Essential skills needed for both Kanban and Scrum Retrospectives Splitting the system into deliverable increments Software craftsmanship Teams not businessoriented Teams grouped by component Root-cause analysis Teams not focused Team not getting feedback from customer Lack of team spirit Teams don t have own PO Ineffective requirements communication Too much focus on written specs POdoesn t have own team Unclear roles & responsibilities Lack of discipline in teams Feature split across multiple teams Hard to plan Delayed releases Lack of transparancy No burndowns Fear of committing Bad throughput in development Problems estimating Not measuring velocity Cutting quality instead of scope Difficult to release Teams disrupted during sprint Many defects Lack of test automation Hard to change the code Many operational problems Customers dissatisfied Henrik Kniberg 50

51 Take-away points 1. Know your goal Hint: Agile/Lean/Kanban/Scrum isn t it. 2. Never blame the tool Tools don t fail or succeed. People do. There is no such thing as a good or bad tool. Only good or bad decisions about when, where, how, and why to use which tool. 3. Don t limit yourself to one tool Learn as many as possible. Compare for understanding, not judgement. 4. Experiment & enjoy the ride Don t worry about getting it right from start. The only real failure is the failure to learn from failure. Henrik Kniberg 51

52 Henrik Kniberg 52

Kanban vs Scrum Making the most of both

Kanban vs Scrum Making the most of both Kanban vs Scrum Making the most of both JAOO, Aarhus Oct 6, 2009 Henrik Kniberg Agile/Lean coach @ Crisp, Stockholm Board of directors henrik.kniberg@crisp.se +46 70 4925284 Purpose of this presentation

More information

Kanban. Marek Majchrzak, Andrzej Bednarz Wrocław, 07.06.2011

Kanban. Marek Majchrzak, Andrzej Bednarz Wrocław, 07.06.2011 Kanban Marek Majchrzak, Andrzej Bednarz Wrocław, 07.06.2011 Why Kanban? Jim: Now we ve finally gone all-out Scrum! Fred: So how s it going? Jim: Well, it s a lot better than what we had before... Fred:...but?

More information

Kanban vs Scrum. Henrik Kniberg - Crisp AB Agile coach & Java guy. A practical guide. Deep Lean, Stockholm May 19, 2009

Kanban vs Scrum. Henrik Kniberg - Crisp AB Agile coach & Java guy. A practical guide. Deep Lean, Stockholm May 19, 2009 Henrik Kniberg - risp gile coach & Java guy Kanban vs Scrum practical guide eep Lean, Stockholm May 19, 009 ofounder / TO of Goyada (mobile services) 30 developers Lead architect at ce Interactive (gaming)

More information

Kanban A Lean approach to Agile software development

Kanban A Lean approach to Agile software development Kanban A Lean approach to Agile software development JFokus January 26, 2010 Henrik Kniberg Agile/Lean coach www.crisp.se Board of directors henrik.kniberg@crisp.se 070 4925284 Goals of this tutorial Basic

More information

Kanban. A Toyota s manufacturing system for Software Development CERN EUROPEAN ORGANIZATION FOR NUCLEAR RESEARCH. Eloy Reguero Fuentes

Kanban. A Toyota s manufacturing system for Software Development CERN EUROPEAN ORGANIZATION FOR NUCLEAR RESEARCH. Eloy Reguero Fuentes CERN Kanban A Toyota s manufacturing system for Software Development Who am I? Eloy Reguero Fuentes (Noreña - Spain) Computer Science Engineer (Universidad de Oviedo 2007) SoKware Engineer at CERN (2007)

More information

Introduction to Agile and Scrum

Introduction to Agile and Scrum Introduction to Agile and Scrum Matthew Renze @matthewrenze COMS 309 - Software Development Practices Purpose Intro to Agile and Scrum Prepare you for the industry Questions and answers Overview Intro

More information

Agile and lean methods for managing application development process

Agile and lean methods for managing application development process Agile and lean methods for managing application development process Hannu Markkanen 27.01.2012 1 Lifecycle model To support the planning and management of activities required in the production of e.g.

More information

Agile and lean methods for managing application development process

Agile and lean methods for managing application development process Agile and lean methods for managing application development process Hannu Markkanen 24.01.2013 1 Application development lifecycle model To support the planning and management of activities required in

More information

The Agile Project Manager

The Agile Project Manager The Agile Project Manager PMI Madrid, 29/1/2014 1 Jose Barato Consulting, Training and Tools in Project Management PMPeople (Managing Director) PMI Madrid Chapter (Director) PM-IB (founder, Vice-President)

More information

MTAT.03.094 Software Engineering

MTAT.03.094 Software Engineering MTAT.03.094 Software Engineering Lecture 12: Lean & Flow-based (KANBAN) Principles and Processe Fall 2015 Dietmar Pfahl email: dietmar.pfahl@ut.ee Structure of Lecture 12 KANBAN Case Study: Scrum vs. KANBAN

More information

The Agile Manifesto is based on 12 principles:

The Agile Manifesto is based on 12 principles: The Agile Manifesto is based on 12 principles: Customer satisfaction by rapid delivery of a useful product solution Welcome changing requirements, even late in development Working products are delivered

More information

When agile is not enough

When agile is not enough When agile is not enough LESS 2010 Kati Vilkki kati.vilkki@nsn.com 1 Nokia Siemens Networks When agile is not enough What does lean thinking add to agile? Combining agile and lean Change in mind-set Management

More information

Agile Notetaker & Scrum Reference. Designed by Axosoft, the creators of OnTime the #1 selling scrum software.

Agile Notetaker & Scrum Reference. Designed by Axosoft, the creators of OnTime the #1 selling scrum software. Agile Notetaker & Scrum Reference Designed by Axosoft, the creators of OnTime the #1 selling scrum software. Scrum Diagram: Team Roles: roduct Owner: Is responsible for what goes into the product backlog

More information

10 ways to screw up with Scrum and XP Welcome! 1.Sit near the front please! 2.Are you using Scrum or XP? If so grab 3 colored ballots from the stage.

10 ways to screw up with Scrum and XP Welcome! 1.Sit near the front please! 2.Are you using Scrum or XP? If so grab 3 colored ballots from the stage. 10 ways to screw up with Scrum and XP Welcome! 1.Sit near the front please! 2.Are you using Scrum or XP? If so grab 3 colored ballots from the stage. 10 ways to screw up with Scrum and XP Henrik Kniberg

More information

10 kanban boards and their context

10 kanban boards and their context 10 kanban boards and their context Hi! I ve visualized a set of kanban boards from operations, development and sales to trigger ideas. But don t forget, a kanban board is a tool to help you think for yourself,

More information

Executive Guide to SAFe 24 July 2014. An Executive s Guide to the Scaled Agile Framework. alshall@netobjectives.com @AlShalloway

Executive Guide to SAFe 24 July 2014. An Executive s Guide to the Scaled Agile Framework. alshall@netobjectives.com @AlShalloway An Executive s Guide to the Scaled Agile Framework Al Shalloway CEO, Net Objectives Al Shalloway CEO, Founder alshall@netobjectives.com @AlShalloway co-founder of Lean-Systems Society co-founder Lean-Kanban

More information

Scrum vs. Kanban vs. Scrumban

Scrum vs. Kanban vs. Scrumban Scrum vs. Kanban vs. Scrumban Prelude As Agile methodologies are becoming more popular, more companies try to adapt them. The most popular of them are Scrum and Kanban while Scrumban is mixed guideline

More information

Role of the Business Analyst in an Agile Project

Role of the Business Analyst in an Agile Project Role of the Business Analyst in an Agile Project Agenda 1: Introduction to Agile 2: Focus on Agile Principles 3: Business Analysis and the agile process 4: Addressing challenges 5: Close off and recap

More information

The style is: a statement or question followed by four options. In each case only one option is correct.

The style is: a statement or question followed by four options. In each case only one option is correct. AGILE FOUNDATION CERTIFICATE SAMPLE FOUNDATION QUESTIONS WITH ANSWERS This document is a set of sample questions, in the style of the Agile Foundation Certificate Examination, which is a 60 question, 1

More information

Introduction to Agile Scrum

Introduction to Agile Scrum Introduction to Agile Scrum by Julia M. Lobur Penn State Harrisburg CMPSC 487W Fall 2015 Introduction to Scrum Learning Goals Relationship of Scrum to other Agile methods Scrum Framework Scrum Roles Scrum

More information

Agile Scrum Workshop

Agile Scrum Workshop Agile Scrum Workshop What is agile and scrum? Agile meaning: Able to move quickly and easily. Scrum meaning: a Rugby play Agile Scrum: It is an iterative and incremental agile software development framework

More information

SESSION 303 Wednesday, March 25, 3:00 PM - 4:00 PM Track: Support Center Optimization

SESSION 303 Wednesday, March 25, 3:00 PM - 4:00 PM Track: Support Center Optimization SESSION 303 Wednesday, March 25, 3:00 PM - 4:00 PM Track: Support Center Optimization Secrets of a Scrum Master: Agile Practices for the Service Desk Donna Knapp Curriculum Development Manager, ITSM Academy

More information

Scrum and Kanban 101

Scrum and Kanban 101 Scrum and Kanban 101 www.bebetterleader.com @jfiodorova What are your expectations What are the differences between Agile and Traditional? What do you know about Agile Two approaches to control any process:

More information

Agile Software Development. Stefan Balbo / Patrick Dolemieux

Agile Software Development. Stefan Balbo / Patrick Dolemieux Agile Software Development Stefan Balbo / Patrick Dolemieux Agile Software Development Stefan Balbo / Patrick Dolemieux Content Why go Agile? Introduction to Scrum - Process - Roles Agile Estimating and

More information

Lean Software Development and Kanban

Lean Software Development and Kanban 1 of 7 10.04.2013 21:30 Lean Software Development and Kanban Learning Objectives After completing this topic, you should be able to recognize the seven principles of lean software development identify

More information

Quality Assurance in an Agile Environment

Quality Assurance in an Agile Environment Quality Assurance in an Agile Environment 1 Discussion Topic The Agile Movement Transition of QA practice and methods to Agile from Traditional Scrum and QA Recap Open Discussion www.emids.com 2 What is

More information

LEAN AGILE POCKET GUIDE

LEAN AGILE POCKET GUIDE SATORI CONSULTING LEAN AGILE POCKET GUIDE Software Product Development Methodology Reference Guide PURPOSE This pocket guide serves as a reference to a family of lean agile software development methodologies

More information

Agile Project Management and the Real World. Emily Lynema DLF Fall 2010 November 1, 2010

Agile Project Management and the Real World. Emily Lynema DLF Fall 2010 November 1, 2010 Agile Project Management and the Real World Emily Lynema DLF Fall 2010 November 1, 2010 Outline Why care about project management? Traditional vs. Agile What is Agile? What is Scrum? Agile case study:

More information

Certified ScrumMaster (CSM) Content Outline and Learning Objectives January 2012

Certified ScrumMaster (CSM) Content Outline and Learning Objectives January 2012 Certified ScrumMaster (CSM) Content Outline and Learning Objectives January 2012 The following pages present the CSM taxonomy as validated through the 2011 Scrum Alliance Validation Study. Each percentage

More information

Global Business Services, GBS. Scrum and Kanban. Processer & IT nord seminar 5v3. Gitte Klitgaard Hansen, IBM

Global Business Services, GBS. Scrum and Kanban. Processer & IT nord seminar 5v3. Gitte Klitgaard Hansen, IBM Scrum and Kanban Processer & IT nord seminar 5v3 Gitte Klitgaard Hansen, IBM Agenda Who am I? My background in scrum and agile Basics of scrum Basics of kanban When do you use scrum and kanban? 2 Who am

More information

The Basics of Scrum An introduction to the framework

The Basics of Scrum An introduction to the framework The Basics of Scrum An introduction to the framework Introduction Scrum, the most widely practiced Agile process, has been successfully used in software development for the last 20 years. While Scrum has

More information

Lean Agile Scrum Business Value Development and Delivery using Agility. Brenden McGlinchey Software Done Right, Inc. brenden@softwaredoneright.

Lean Agile Scrum Business Value Development and Delivery using Agility. Brenden McGlinchey Software Done Right, Inc. brenden@softwaredoneright. Lean Agile Scrum Business Value Development and Delivery using Agility Brenden McGlinchey Software Done Right, Inc. brenden@softwaredoneright.net High yield software engineering team Active Customer Involvement

More information

Certified ScrumMaster (CSM) Content Outline and Learning Objectives January 2012

Certified ScrumMaster (CSM) Content Outline and Learning Objectives January 2012 Certified ScrumMaster (CSM) Content Outline and Learning Objectives January 2012 The following pages present the CSM taxonomy as validated through the 2011 Scrum Alliance Validation Study. Total questions

More information

Topics covered. Agile methods Plan-driven and agile development Extreme programming Agile project management Scaling agile methods

Topics covered. Agile methods Plan-driven and agile development Extreme programming Agile project management Scaling agile methods Topics covered Chapter 3 Agile Software Development Agile methods Plan-driven and agile Extreme programming Agile project management Scaling agile methods 1 2 Need for rapid software Rapid software Changing

More information

Agile Development to Transform FedEx

Agile Development to Transform FedEx Agile Development to Transform FedEx PPAI IT Summit Xuan Liu, Managing Director, IT FedEx and Promotional Products 2 FedEx connects people with opportunities around the world FY15 Revenue: $47.5 billion

More information

FREE ONLINE EDITION. If you like the book, please support the authors and InfoQ by. purchasing the printed book:

FREE ONLINE EDITION. If you like the book, please support the authors and InfoQ by. purchasing the printed book: FREE ONLINE EDITION If you like the book, please support the authors and InfoQ by purchasing the printed book: http://www.lulu.com/content/7731694 (only $22.95) Brought to you Courtesy of This book is

More information

Mastering the Iteration: An Agile White Paper

Mastering the Iteration: An Agile White Paper Rally Software Development Corporation Whitepaper Mastering the Iteration: An Agile White Paper Dean Leffingwell Abstract: The heartbeat of Agile development is the iteration the ability of the team to

More information

Agile Development Overview

Agile Development Overview Presented by Jennifer Bleen, PMP Project Services Practice of Cardinal Solutions Group, Inc. Contact: Agile Manifesto We are uncovering better ways of developing software by doing it and helping others

More information

Kanban For Software Engineering

Kanban For Software Engineering Kanban For Software Engineering Jaco van der Merwe Electromagnetic Software & Systems (EMSS) 18/8/2010 jvdmerwe@emss.co.za FEKO 1 General Applications of FEKO Antennas Antenna placement Microwave components

More information

Scrum. in five minutes

Scrum. in five minutes Scrum in five minutes Scrum and agile methods are hot topics these days A simple method for the management of complex projects... Older methods focus on staying on track; Scrum is aimed at delivering business

More information

Agile Projects 7. Agile Project Management 21

Agile Projects 7. Agile Project Management 21 Contents Contents 1 2 3 Agile Projects 7 Introduction 8 About the Book 9 The Problems 10 The Agile Manifesto 12 Agile Approach 14 The Benefits 16 Project Components 18 Summary 20 Agile Project Management

More information

Agile support with Kanban some tips and tricks By Tomas Björkholm

Agile support with Kanban some tips and tricks By Tomas Björkholm Agile support with Kanban some tips and tricks By Tomas Björkholm Foreword A year ago I held an Open Space at Scrum Gathering in Stockholm about Agile Support. I have since received several requests to

More information

agenda AGILE AT SCALE

agenda AGILE AT SCALE Copyright Net Objectives, Inc. All Rights Reserved 1 AGILE AT SCALE 1. THE CHALLENGE HIERARCHY VS. WORKFLOW 2. VALUE STREAM IMPEDANCE 3. ALLOCATE PEOPLE TO MOST VALUABLE WORK 4. MANAGING FLOW ACROSS ENTIRE

More information

Introduction to Agile Software Development Process. Software Development Life Cycles

Introduction to Agile Software Development Process. Software Development Life Cycles Introduction to Agile Software Development Process Presenter: Soontarin W. (Senior Software Process Specialist) Date: 24 November 2010 AGENDA Software Development Life Cycles Waterfall Model Iterative

More information

Transitioning Your Software Process To Agile Jeffery Payne Chief Executive Officer Coveros, Inc. jeff.payne@coveros.com www.coveros.

Transitioning Your Software Process To Agile Jeffery Payne Chief Executive Officer Coveros, Inc. jeff.payne@coveros.com www.coveros. Transitioning Your Software Process To Agile Jeffery Payne Chief Executive Officer Coveros, Inc. jeff.payne@coveros.com www.coveros.com 1 About Coveros Coveros helps organizations accelerate the delivery

More information

Software Development Methodologies

Software Development Methodologies Software Development Methodologies Jonathan Hoyle Eastman Kodak Thursday, June 2, 2005 Overview Predictive Methodologies Waterfall Other Predictive Methodologies Agile Methodologies Extreme Programming

More information

A Glossary of Scrum / Agile Terms

A Glossary of Scrum / Agile Terms A Glossary of Scrum / Agile Terms Acceptance Criteria: Details that indicate the scope of a user story and help the team and product owner determine done-ness. Agile: the name coined for the wider set

More information

PLM - Agile. Design Code Test. Sprints 1, 2, 3, 4.. Define requirements, perform system design, develop and test the system. Updated Project Plan

PLM - Agile. Design Code Test. Sprints 1, 2, 3, 4.. Define requirements, perform system design, develop and test the system. Updated Project Plan PLM - Agile Agile Development Evolved in the 1990s as a response to heavyweight methodologies. In 2001 representatives of various new methodologies met to discuss the need for lighter alternatives. The

More information

Agile Project Management

Agile Project Management Agile Project Management Projekt-Kick-Off-Tage Hochschule Augsburg Martin Wagner, 15. März 2011 TNG Technology Consulting GmbH, http://www.tngtech.com Agile project management with Scrum Agenda Software

More information

ScrumMaster or Armchair Psychologist Scrum Fundamentals Webinar Q&A March 9, 2016

ScrumMaster or Armchair Psychologist Scrum Fundamentals Webinar Q&A March 9, 2016 ScrumMaster or Armchair Psychologist Scrum Fundamentals Webinar Q&A March 9, 2016 As a ScrumMaster, one of your responsibilities is "Causing change that increases the productivity of the Scrum Team." What

More information

Scrum. The Essence. Tobias Mayer, http://agilethinking.net. Sonntag, 19. Februar 12

Scrum. The Essence. Tobias Mayer, http://agilethinking.net. Sonntag, 19. Februar 12 Scrum The Essence What is Scrum? Scrum is a framework that allows you to create your own lightweight process for developing new products. Scrum is simple. It can be understood and implemented in a few

More information

Scrum In 10 Slides. Inspect & Adapt

Scrum In 10 Slides. Inspect & Adapt Scrum In 10 Slides Inspect & Adapt Why Scrum? 52.7% projects cost 189% of their original estimates 60% of functionality delivered is rarely or never used 80% of the value comes from 20% of the functionality

More information

AGILE & SCRUM. Revised 9/29/2015

AGILE & SCRUM. Revised 9/29/2015 AGILE & SCRUM Revised 9/29/2015 This Page Intentionally Left Blank Table of Contents Scrum Fundamentals Certified Course... 1 Scrum Developer Certified (SDC)... 2 Scrum Master Certified (SMC)... 3 Scrum

More information

Program & Portfolio! Management using! Kanban! Copyright 2013 Davisbase Consulting. Limited Display License Provided to ASPE

Program & Portfolio! Management using! Kanban! Copyright 2013 Davisbase Consulting. Limited Display License Provided to ASPE Program & Portfolio! Management using! Kanban! Introduction and Agenda Tom Wessel, Davisbase Consulting 20 years in software development. Over 7 years working with software development teams, training,

More information

The Team... 1 The Backlog... 2 The Release... 4 The Sprint... 5 Quick Summary... 6. Stakeholders. Business Owner. Product Owner.

The Team... 1 The Backlog... 2 The Release... 4 The Sprint... 5 Quick Summary... 6. Stakeholders. Business Owner. Product Owner. Scrum In A Nutshell Scrum is about Teams producing Results in an agile way. Scrum Teams achieve results anyway they can by using a simple set of rules to guide effort. We will describe scrum as a simple

More information

Agile Project Management and Agile Practices Training; with a Scrum Project that you will do.

Agile Project Management and Agile Practices Training; with a Scrum Project that you will do. 1 PMI Agile Certified Practitioner (PMI-ACP) workshop course details. We are unique and specialists in Agile! Your workshop trainer by passion and is a senior Agile Coach who coached many teams and Kanban

More information

Course Title: Planning and Managing Agile Projects

Course Title: Planning and Managing Agile Projects Course Title: Planning and Managing Agile Projects Course ID: BA15 Credits: 21 PDUs Course Duration: 3 days (Live in person class only) Course Level: Basic/Intermediate Course Description: This 3-day course

More information

What is meant by the term, Lean Software Development? November 2014

What is meant by the term, Lean Software Development? November 2014 What is meant by the term, Lean Software Development? Scope of this Report November 2014 This report provides a definition of Lean Software Development and explains some key characteristics. It explores

More information

D25-2. Agile and Scrum Introduction

D25-2. Agile and Scrum Introduction D25-2 Agile and Scrum Introduction How to Use this Download This download is an overview of a discussion Intertech has with clients on Agile/Scrum This download has an overview of Agile, an overview of

More information

Agile extreme Development & Project Management Strategy Mentored/Component-based Workshop Series

Agile extreme Development & Project Management Strategy Mentored/Component-based Workshop Series Overview This is a 15-day live facilitator-led or virtual workshop is designed to prompt your entire team to work efficiently with Microsoft s Application Lifecycle Management solution based around Visual

More information

EXIN Agile Scrum Foundation. Sample Exam

EXIN Agile Scrum Foundation. Sample Exam EXIN Agile Scrum Foundation Sample Exam Edition June 2016 Copyright 2016 EXIN All rights reserved. No part of this publication may be published, reproduced, copied or stored in a data processing system

More information

CSPO Learning Objectives Preamble. Scrum Basics

CSPO Learning Objectives Preamble. Scrum Basics CSPO Learning Objectives Preamble This document contains topics for the Certified Scrum Product Owner (CSPO) training course. The purpose of this document is to describe the minimum set of concepts and

More information

Lean and Agile Development With Scrum (Part 2) Lucio Davide Spano

Lean and Agile Development With Scrum (Part 2) Lucio Davide Spano Lean and Agile Development With Scrum (Part 2) Lucio Davide Spano lucio.davide.spano@isti.cnr.it spano@di.unipi.it 7 May 2012 Dilbert intro Summary Sprint Review Done at the end of the Sprint Not a simple

More information

4/4/2013. Copyright 2013, Robert Ward

4/4/2013. Copyright 2013, Robert Ward Challenges In Scaling Scrum Robert Ward 3 April 2013 The Agile Manifesto In Context The Manifesto is mostly heuristics, not mandates and not first principles. It aimed to legitimize resistance to conventional

More information

A Viable Systems Engineering Approach. Presented by: Dick Carlson (richard.carlson2@boeing.com)

A Viable Systems Engineering Approach. Presented by: Dick Carlson (richard.carlson2@boeing.com) A Viable Systems Engineering Approach Presented by: Dick Carlson (richard.carlson2@boeing.com) Philip Matuzic (philip.j.matuzic@boeing.com) i i Introduction This presentation ti addresses systems engineering

More information

Applying Lean on Agile Scrum Development Methodology

Applying Lean on Agile Scrum Development Methodology ISSN:2320-0790 Applying Lean on Agile Scrum Development Methodology SurendRaj Dharmapal, Dr. K. Thirunadana Sikamani Department of Computer Science, St. Peter University St. Peter s College of Engineering

More information

Plan-Driven Methodologies

Plan-Driven Methodologies Plan-Driven Methodologies The traditional way to develop software Based on system engineering and quality disciplines (process improvement) Standards developed from DoD & industry to make process fit a

More information

CSSE 372 Software Project Management: More Agile Project Management

CSSE 372 Software Project Management: More Agile Project Management CSSE 372 Software Project Management: More Agile Project Management Shawn Bohner Office: Moench Room F212 Phone: (812) 877-8685 Email: bohner@rose-hulman.edu Learning Outcomes: Plan Create a plan for

More information

Agile So)ware Development

Agile So)ware Development Software Engineering Agile So)ware Development 1 Rapid software development Rapid development and delivery is now often the most important requirement for software systems Businesses operate in a fast

More information

Agile Metrics. It s Not All That Complicated

Agile Metrics. It s Not All That Complicated Agile Metrics It s Not All That Complicated Welcome About your Trainer, Katia Sullivan VersionOne Product Trainer and Agile Coach Certified Scrum Master Certified Scrum Product Owner Led teams/org s to

More information

Basic Trends of Modern Software Development

Basic Trends of Modern Software Development DITF LDI Lietišķo datorsistēmu programmatūras profesora grupa e-business Solutions Basic Trends of Modern Software Development 2 3 Software Engineering FAQ What is software engineering? An engineering

More information

Course Title: Managing the Agile Product Development Life Cycle

Course Title: Managing the Agile Product Development Life Cycle Course Title: Managing the Agile Product Development Life Cycle Course ID: BA25 Credits: 28 PDUs Course Duration: 4 days (with optional Executive session) Course Level: Intermediate/Advanced Course Description:

More information

Chapter 6. Iteration 0: Preparing for the First Iteration

Chapter 6. Iteration 0: Preparing for the First Iteration Chapter 6. Iteration 0: Preparing for the First Iteration People only see what they are prepared to see. Ralph Waldo Emerson There are no secrets to success. It is the result of preparation, hard work,

More information

Certified Scrum Master Workshop

Certified Scrum Master Workshop Learn, understand, and execute on the three overarching principles behind Scrum: iterative development, selfmanagement, and visibility. Even projects that have solid, well-defined project plans encounter

More information

Glossary SAFe 4.0 for Lean Software and Systems Engineering

Glossary SAFe 4.0 for Lean Software and Systems Engineering Agile Architecture Agile architecture is a set of values and practices that support the active evolution of the design and architecture of a system, concurrent with the implementation of new business functionality.

More information

Agile to the Bone. Introduction to Agile by Pietari Kettunen

Agile to the Bone. Introduction to Agile by Pietari Kettunen Agile to the Bone Introduction to Agile by Pietari Kettunen Agenda Problem with traditional software engineering Why Agile is the solution? Roots of Agile Values of Agile Common implementations Scrum Kanban

More information

Software Engineering Process Economy & Quality

Software Engineering Process Economy & Quality Project delivery: Progress report Software Engineering Process Economy & Quality ETSF 01 http://cs.lth.se/etsf01 The SPA reports you RECEIVED Your actions on received feedback Excel format preferred Lecture

More information

Getting Started with Agile Project Management Methods for Elearning

Getting Started with Agile Project Management Methods for Elearning Getting Started with Agile Project Management Methods for Elearning Megan Torrance TorranceLearning Training2013 Session 108 February 18, 2013 8am Megan Torrance has 20 years of experience in the learning

More information

Capstone Agile Model (CAM)

Capstone Agile Model (CAM) Capstone Agile Model (CAM) Capstone Agile Model (CAM) Approach Everything we do within the Capstone Agile Model promotes a disciplined project leadership process that encourages frequent inspection and

More information

This handbook is meant to be a quick-starter guide to Agile Project Management. It is meant for the following people:

This handbook is meant to be a quick-starter guide to Agile Project Management. It is meant for the following people: AGILE HANDBOOK OVERVIEW WHAT IS THIS? This handbook is meant to be a quick-starter guide to Agile Project Management. It is meant for the following people: Someone who is looking for a quick overview on

More information

ScrumMaster Certification Workshop: Preparatory Reading

ScrumMaster Certification Workshop: Preparatory Reading A S P E S D L C Tr a i n i n g ScrumMaster Certification Workshop: Preparatory Reading A WHITE PAPER PROVIDED BY ASPE ScrumMaster Certification Workshop: Preparatory Reading Greetings, Potential Certified

More information

http://www.scrum-institute.org International Scrum Institute

http://www.scrum-institute.org International Scrum Institute THE ONLY BOOK CAN SIMPLY LEARN SCRUM! Page 1 Contents ABOUT THE AUTHOR... 3 WHAT IS SCRUM?... 4 INTRODUCTION TO SCRUM - A REAL WORLD EXAMPLE... 6 WHAT MAKES WATERFALL SOFTWARE DEVELOPMENT MODEL FAIL IN

More information

XP & Scrum. extreme Programming. XP Roles, cont!d. XP Roles. Functional Tests. project stays on course. about the stories

XP & Scrum. extreme Programming. XP Roles, cont!d. XP Roles. Functional Tests. project stays on course. about the stories XP & Scrum Beatrice Åkerblom beatrice@dsv.su.se extreme Programming XP Roles XP Roles, cont!d! Customer ~ Writes User Stories and specifies Functional Tests ~ Sets priorities, explains stories ~ May or

More information

SECC Agile Foundation Certificate Examination Handbook

SECC Agile Foundation Certificate Examination Handbook Versions 2.0 Version Date Remarks 1.0 12/4/2012 Initial version 2.0 3/8/2008 REVISION HISTORY Updated knowledge areas Added questions examples Updated suggested readings section Page 2 of 15 Version 2.0

More information

Scrum Guidelines. v.2 2011 W W W. S C R U M D E S K. C O M

Scrum Guidelines. v.2 2011 W W W. S C R U M D E S K. C O M Scrum Guidelines v.2 2011 W W W. S C R U M D E S K. C O M WHY Agile Ceremonies Agile project is developed in repeatable ceremonies that give rhythm to delivery. Product Strategy Once per year Release Planning

More information

Requirement Management with the Rational Unified Process RUP practices to support Business Analyst s activities and links with BABoK

Requirement Management with the Rational Unified Process RUP practices to support Business Analyst s activities and links with BABoK IBM Software Group Requirement Management with the Rational Unified Process RUP practices to support Business Analyst s activities and links with BABoK Jean-Louis Maréchaux Software IT Specialist IBM Rational

More information

04-10-2009 KANBAN. Mads Troels Hansen. Prosa, October 4 th 2009. 2009 Mads Troels Hansen. October 09, 2009 Mads Troels Hansen

04-10-2009 KANBAN. Mads Troels Hansen. Prosa, October 4 th 2009. 2009 Mads Troels Hansen. October 09, 2009 Mads Troels Hansen KNN Mads Troels Hansen Prosa, October 4 th 2009 2009 Mads Troels Hansen 2 1 Personal Kanban Kanban Lean gile Inspiration and my experience! 3 What I do - today Project ooster Shared Product Vision Iterative

More information

How NOT to Do Scrum. Patterns and Anti-patterns. Revised July 2013. First presented at New York City Scrum User Group June 17, 2010

How NOT to Do Scrum. Patterns and Anti-patterns. Revised July 2013. First presented at New York City Scrum User Group June 17, 2010 How NOT to Do Scrum Patterns and Anti-patterns Revised July 2013 First presented at New York City Scrum User Group June 17, 2010 V 2.2 2010, 2013 Qualytic Consulting What this is about Patterns Practices

More information

AGILE METHODOLOGIES IN SOFTWARE DEVELOPMENT

AGILE METHODOLOGIES IN SOFTWARE DEVELOPMENT AGILE METHODOLOGIES IN SOFTWARE DEVELOPMENT Abstract 9 Nayab Zya #1, Mohammad Suaib #2 1 M.Tech (CSE), Second Year 2 Research Guide # Department of Computer Science and Engineering Integral University,

More information

Secrets of a Scrum Master: Agile Practices for the Service Desk

Secrets of a Scrum Master: Agile Practices for the Service Desk Secrets of a Scrum Master: Agile Practices for the Service Desk #askitsm @ITSMAcademy @ITSM_Lisa @ITSM_Donna ITSM Academy About ITSM Academy NextGen ITSM Education: Certified Process Design Engineer (CPDE)

More information

Agile with XP and Scrum

Agile with XP and Scrum Agile with XP and Scrum Amit Goel National Agile Software Workshop @ Indore Agile India Conference Agile Software Community of India Disclaimer and Credits Most of material in this presentation has been

More information

The Agile Drupalist. Methodologies & Techniques for Running Effective Drupal Projects. By Adrian AJ Jones (Canuckaholic)

The Agile Drupalist. Methodologies & Techniques for Running Effective Drupal Projects. By Adrian AJ Jones (Canuckaholic) The Agile Drupalist Methodologies & Techniques for Running Effective Drupal Projects By Adrian AJ Jones (Canuckaholic) Agenda What We Will be Talking About Today! Introductions! What kind of processes

More information

Agile Testing (October 2011) Page 1. Learning Objectives for Agile Testing

Agile Testing (October 2011) Page 1. Learning Objectives for Agile Testing Agile Testing (October 2011) Page 1 Learning Objectives for Agile Testing "Certification is the by-product; Learning is the product." Agile Testing should: Compare and contrast agile testing with traditional

More information

Agile Training Portfolio

Agile Training Portfolio Agile Training Portfolio Why agile? The question can also be: Why learn fast? Why adapt to new experiences and learnings quickly and easily? Well, the Dodo was not very agile and we all know how that ended.

More information

Agile Systems Engineering: What is it and What Have We Learned?

Agile Systems Engineering: What is it and What Have We Learned? Agile Systems Engineering: What is it and What Have We Learned? March 2012 Dr. Suzette S. Johnson Agile Engineering Northrop Grumman Suzette.Johnson@ngc.com Getting To Know You! Dr. Suzette Johnson Northrop

More information

SCRUM BODY OF KNOWLEDGE (SBOK Guide)

SCRUM BODY OF KNOWLEDGE (SBOK Guide) A Guide to the SCRUM BODY OF KNOWLEDGE (SBOK Guide) 2013 Edition A Comprehensive Guide to Deliver Projects using Scrum TABLE OF CONTENTS TABLE OF CONTENTS 1. INTRODUCTION... 1 1.1 Overview of Scrum...

More information

Waterfall to Agile. DFI Case Study By Nick Van, PMP

Waterfall to Agile. DFI Case Study By Nick Van, PMP Waterfall to Agile DFI Case Study By Nick Van, PMP DFI Case Study Waterfall Agile DFI and Waterfall Choosing Agile Managing Change Lessons Learned, Sprints Summary Q and A Waterfall Waterfall Waterfall

More information

Scrum and Testing The end of the test role Bryan Bakker 20 maart 2012

Scrum and Testing The end of the test role Bryan Bakker 20 maart 2012 Scrum and Testing The end of the test role Bryan Bakker 20 maart 2012 voordracht georganiseerd door Discussiegroep Software Testing met de steun van Ingenieurshuis, Antwerpen Scrum and Testing... The end

More information

Scaling Agile @ Spotify

Scaling Agile @ Spotify Scaling Agile @ Spotify with Tribes, Squads, Chapters & Guilds Henrik Kniberg & Anders Ivarsson Oct 2012 Dealing with multiple teams in a product development organization is always a challenge! One of

More information

Scaling Scrum. Colin Bird & Rachel Davies Scrum Gathering London 2007. conchango 2007 www.conchango.com

Scaling Scrum. Colin Bird & Rachel Davies Scrum Gathering London 2007. conchango 2007 www.conchango.com Scaling Scrum Colin Bird & Rachel Davies Scrum Gathering London 2007 Scrum on a Slide Does Scrum Scale? Ok, so Scrum is great for a small team but what happens when you have to work on a big project? Large

More information