why can't i, we, it produce anything quickly

Why Can't I, We, It Produce Anything Quickly?

By Brian Sjoberg (@onek2go)

AnAgileMind.net

https://twitter.com/onek2go

http://anagilemind.net/

6

Information

Systems Electronic

Systems

Geospatial

Systems

Mission

Systems

AgendaIntroductions

So What?

Agile Manifesto

Game Time!!

Wrap Up

DoneDoing

7

Information

Systems Electronic

Systems

Geospatial

Systems

Mission

Systems

AgendaIntroductions

So What?

Agile Manifesto

Game Time!!

Wrap Up

DoneDoing

• Who are you?

• Where are you on your agile journey?

• Who am I?

Introductions

8

• Agile Coach with Excella Consulting

– Find me on LinkedIn

• Connect. Share. Learn.

– DC Scrum User Group Organizer

– Tweet - @onek2go

– Blog - AnAgileMind.net

– Email - [email protected]

Who Am I?

http://www.excella.com/

http://www.meetup.com/DC-Scrum/



mailto:[email protected]

10

Information

Systems Electronic

Systems

Geospatial

Systems

Mission

Systems

AgendaIntroductions

Agile Manifesto

Game Time!!

Wrap Up

Done

So What?

Doing

11

Information

Systems Electronic

Systems

Geospatial

Systems

Mission

Systems

AgendaIntroductions

So What?

Agile Manifesto

Game Time!!

Wrap Up

DoneDoing

Do you have difficulty explaining

the cost associated with behaviors

within a complex system?

So What?

Do you keep doing something even

though you know it reduces your

productivity?

So What?

Insanity: Repeating the same

behaviors and

expecting a different

outcome.- Albert Einstein

• As a facilitator, I would like to run a game that

helps understand impacts of behaviors so that it

may help attendees and others ADAPT(credit: Mike Cohn)

User Story

15

Awareness

Desire

Ability

Promote

Transfer

16

Information

Systems Electronic

Systems

Geospatial

Systems

Mission

Systems

AgendaIntroductions

So What?

Game Time!!

Wrap Up

Done

Agile Manifesto

Doing

17

Information

Systems Electronic

Systems

Geospatial

Systems

Mission

Systems

AgendaIntroductions

So What?

Agile Manifesto

Game Time!!

Wrap Up

DoneDoing

1. Our highest priority is to satisfy the

customer through early and

continuous delivery of valuable

software.

Agile Manifesto (Principles)

2. Welcome changing requirements,

even late in development. Agile

processes harness change for the

customer's competitive advantage.


3. Deliver working software frequently,

from a couple of weeks to a couple

of months, with a preference to the

shorter timescale.


4. Business people and developers

must work together daily throughout

the project.


5. Build projects around motivated

individuals. Give them the environment

and support they need, and trust them to

get the job done.


6. The most efficient and effective

method of conveying information to

and within a development team is

face-to-face conversation.


7. Working software is the primary

measure of progress.


8. Agile processes promote

sustainable development. The

sponsors, developers, and users

should be able to maintain a

constant pace indefinitely.


9. Continuous attention to technical

excellence and good design

enhances agility.


10.Simplicity--the art of maximizing the

amount of work not done--is

essential.


11.The best architectures,

requirements, and designs emerge

from self-organizing teams.


12.At regular intervals, the team

reflects on how to become more

effective, then tunes and adjusts its

behavior accordingly.


1. Satisfy the customer through early and continuous delivery

2. Welcome changing requirements

3. Deliver frequently, preferring a shorter timescale

4. Business & technical team working together daily

5. Pick the right team, support them & trust them

6. Face-to-Face communication

Agile Manifesto (Principles)7. Working software is the

primary measure of progress

8. Sustainable constant pace

9. Technical excellence and

good design enhances

agility

10. Simplicity; maximizing the

amount of work not done

11. Best results emerge from

self-organizing teams

12. Team inspects and adapts to

become more effective

35

Information

Systems Electronic

Systems

Geospatial

Systems

Mission

Systems

AgendaIntroductions

So What?

Agile Manifesto

Wrap Up

Done

Game Time!!

Doing

36

Information

Systems Electronic

Systems

Geospatial

Systems

Mission

Systems

AgendaIntroductions

So What?

Agile Manifesto

Game Time!!

Wrap Up

DoneDoing

Name Game

BrianOriginally created by Henrik Kniberg, THANK YOU!

Round 1

Credit: Henrik Kniberg

• Never keep a customer waiting

• Start early = Finish early

Round 1 Policy

Name Game

• Limit WIP (Work In Process)

• Current Limit = 1 Customer at a Time

Round 2 Policy

Round 2


Name Game

Now What?

Team working 4 projects

Project A

Project B

Project C

Project D

JAN FEB MAR APR MAY JUN

Org Working ProgramsQ1 Q2 Q3 Q4

Program A

Program B

Program C

Program D

Priority

Q5 Q6

Team Working ProjectsJAN FEB MAR APR

Project A

Project B

Project C

Project D

Priority

MAY JUN

Team Working User StoriesDay 2 Day 4 Day 6 Day 8

User Story A

User Story B

User Story C

User Story D

Priority

Day 10

Individual Working Tasks9 AM 11 AM 1 PM 3 PM

Task A

Task B

Task C

Task D

Priority

5 PM

• Create a Vision

• Create long term goals

– Release

– Epics

• Create short term goals

– Iteration

– User Stories

• Align priorities based on the above

How to Prioritize?

56

Information

Systems Electronic

Systems

Geospatial

Systems

Mission

Systems

AgendaIntroductions

So What?

Agile Manifesto

Game Time!!

Done

Wrap Up

Doing

57

Information

Systems Electronic

Systems

Geospatial

Systems

Mission

Systems

AgendaIntroductions

So What?

Agile Manifesto

Game Time!!

Wrap Up

DoneDoing

58

Information

Systems Electronic

Systems

Geospatial

Systems

Mission

Systems

AgendaIntroductions

So What?

Agile Manifesto

Game Time!!

Wrap Up

Doing Done

Contact MeBrian Sjoberg (@onek2go)

[email protected]

301.404.0765 (USA)

AnAgileMind.net blog


mailto:[email protected]


why can't i, we, it produce anything quickly

Leadership & Management