SlideShare uma empresa Scribd logo
1 de 79
Baixar para ler offline
Seeing What Matters

           Using the Right Vision
            to Manage Transition

                 © copyright 2010. Net Objectives, Inc.
Lean for Executives
      Product Portfolio
                                                              ASSESSMENTS
      Management                                               CONSULTING
                             Business
                                                                 T RAINING
                                                                 COACHING



                              Lean
                            Enterprise

                                          Manage
        Team
                                           ment
technical    process

Kanban / Scrum                           Lean Management
ATDD / TDD / Design Patterns             Project Management
Agenda
• What we want
• Why we can’t get there
  directly
• Manifesting visibility
What We Want
More productivity
Higher quality
Lower cost
Faster delivery




                    copyright © 2010 Net Objectives Inc.
                           ~a _so
G RO U P D I S C U S S I O N
               Lower costs
               Raising productivity
What do people look at?
  Business       Return
  Managers       Cost
  Developers     # of features implemented
  Testers        # of bugs found
  Integrators    # of integration errors
  Customers      How it helps them – pain
                 of use
• How can I improve 
  our time to market?
• How can I improve 
  visibility?
• How do I get 
  predictability?
• How do I measure my 
  success so I can both 
  ensure it as well as 
  know I’ve achieved it?  
Enterprise Agility
Ability to add value quickly




                               copyright © 2010 Net Objectives Inc.
Common Vision
It’s time to pay 
attention to time!
Consider
• Want enterprise agility
• Difference between
  scaling agility and agility
  at scale
• Team agility is a means,
  not an end
Challenges
• Defining business value
• Quick turn-around from
  dev teams
Improving Time to
Market




               copyright © 2010 Net Objectives Inc.
Business value realized



                release




                release



                release



                release

PARETO
Business value realized




                                      release




                        Time

MINIMUM BUILD RELEASE                 release
Business value realized




             Time

                           release
WATERFALL?
Business value realized




                      release




        Time
                      release




BLEND
                      release
Improving
Predictability




                 copyright © 2010 Net Objectives Inc.
Challenges
•   Building wrong stuff
•   Quality of code
•   Overloaded teams
•   Inefficiency of the team
•   Coordination problems
•   Deployment problems
Metrics for Success




                copyright © 2010 Net Objectives Inc.
Here’s a
thought
• Measure what you want
  to achieve
TIME TO MARKET
Visualizing Flow




                   copyright © 2010 Net Objectives Inc.
Concept

                                  Regional Coordinators                                              New
               Business Leaders                                                              Requirements   Customers
                                                     Trainers & Educators
 Product Managers                                                                                                   Consumption
                                                                                      Customer
  Business                          Product Champion(s)

              Capabilities

                                                                                                    Support
                                               Product Related
                                                                 Software   Software  Shared 
                                                                  Product   Release Components
                                                                                              Shared 
                                              Product Related                               Components

                                                            Development


The Continuous Flow of Technology
         Solution Delivery
Principles for Lean-Agile Management
1. Visibility - See the Value
   Stream
2. Flow
         Limit Work to Capacity
         Manage Work in
         Progress
         Remove Delays
3. Build in Quality


                                  thinking
                                   points
Approv
 Request                        Reqts          Sign Off      Analysis
                  e




    Design          Review              Code          Test        Deploy




1. Identify the actions taken in the value stream
Approv
 Request                           Reqts            Sign Off           Analysis
                   e
  0.5 hrs         8 hrs           160 hrs            8 hrs              100 hrs




     Design           Review                Code              Test           Deploy

      120 hrs             2 hrs         280 hrs              240 hrs              8 hrs




1. Identify the actions taken in the value stream
2. Calculate calendar time for each action
Approv
 Request                             Reqts             Sign Off           Analysis
 0.5 hr avg
                    e               60 hrs avg         1 hr avg           40 hrs avg
                  .1 hr avg
  0.5 hrs          8 hrs             160 hrs             8hrs              100 hrs




      Design            Review                 Code               Test           Deploy
     40 hrs avg         2 hrs avg         80 hrs avg        40 hrs avg          3 hrs avg

      120 hrs              2 hrs            280 hrs             240 hrs              8 hrs




1. Identify the actions taken in the value stream
2. Calculate calendar time for each action
3. Calculate time actually worked on the action
Approv
 Request                                                     Reqts                  Sign Off                         Analysis
 0.5 hr avg
                            e                               60 hrs avg               1 hr avg                        40 hrs avg
                320 hrs   .1 hr avg            80 hrs                     320 hrs                       80 hrs
  0.5 hrs                      8 hrs                         160 hrs                     8hrs                         100 hrs



                                                                    80 hrs


      Design                       Review                              Code                      Test                       Deploy
     40 hrs avg                    2 hrs avg            80 hrs    80 hrs avg    80 hrs      40 hrs avg           80 hrs    3 hrs avg
                     160 hrs
      120 hrs                          2 hrs                        280 hrs                     240 hrs                         8 hrs




1. Identify the actions taken in the value stream
2. Calculate calendar time for each action
3. Calculate time actually worked on the action
4. Identify time between actions
Approv
 Request                                                     Reqts                      Sign Off                         Analysis
 0.5 hr avg
                            e                               60 hrs avg                   1 hr avg                        40 hrs avg
                320 hrs    .1 hr avg           80 hrs                     320 hrs                           80 hrs
  0.5 hrs                      8 hrs                         160 hrs                         8hrs                         100 hrs



                                                                    80 hrs


      Design                       Review                              Code                          Test                       Deploy
     40 hrs avg                    2 hrs avg            80 hrs    80 hrs avg        80 hrs      40 hrs avg           80 hrs    3 hrs avg
                     160 hrs
      120 hrs                          2 hrs                        280 hrs                         240 hrs                         8 hrs

                  20% rejected                                                 65% defective
                   Repeat 1X                                                     Repeat 3X




1. Identify the actions taken in the value stream
2. Calculate calendar time for each action
3. Calculate time actually worked on the action
4. Identify time between actions
5. Identify any loop backs required

                                                                                                                                     27 September 2010
Approv
 Request                                                     Reqts                      Sign Off                         Analysis
 0.5 hr avg
                            e                               60 hrs avg                   1 hr avg                        40 hrs avg
                320 hrs    .1 hr avg           80 hrs                     320 hrs                           80 hrs
  0.5 hrs                      8 hrs                         160 hrs                         8hrs                         100 hrs



                                                                    80 hrs


      Design                       Review                              Code                          Test                       Deploy
     40 hrs avg                    2 hrs avg            80 hrs    80 hrs avg        80 hrs      40 hrs avg           80 hrs    3 hrs avg
                     160 hrs
      120 hrs                          2 hrs                        280 hrs                         240 hrs                         8 hrs

                  20% rejected                                                 65% defective
                   Repeat 1X                                                    Repeat 3X


                                                                                                            509 hrs
                                                                                         PCE =                                = 14.9%
1. Identify the actions taken in the value stream            3433 hrs
2. Calculate calendar time for each action
3. Calculate time actually worked on the action
4. Identify time between actions
5. Identify any loop backs required            Avg Time Worked
6. Calculate Process Cycle Efficiency:         Total Cycle Time
Approv
 Request                                                     Reqts                      Sign Off                         Analysis
 0.5 hr avg
                            e                               60 hrs avg                   1 hr avg                        40 hrs avg
                320 hrs    .1 hr avg           80 hrs                     320 hrs                           80 hrs
  0.5 hrs                      8 hrs                         160 hrs                         8hrs                         100 hrs



                                                                    80 hrs


      Design                       Review                              Code                          Test                       Deploy
     40 hrs avg                    2 hrs avg            80 hrs    80 hrs avg        80 hrs      40 hrs avg           80 hrs    3 hrs avg
                     160 hrs
      120 hrs                          2 hrs                        280 hrs                         240 hrs                         8 hrs

                  20% rejected                                                 65% defective
                   Repeat 1X                                                    Repeat 3X


                                                                                                            509 hrs
                                                                                         PCE =                                = 14.9%
1. Identify the actions taken in the value stream           3433 hrs
2. Calculate calendar time for each action
3. Calculate time actually worked on the action
4. Identify time between actions
5. Identify any loop backs required            Avg Time Worked
6. Calculate Process Cycle Efficiency:         Total Cycle Time
Approv
 Request                                                     Reqts                      Sign Off                         Analysis
 0.5 hr avg
                            e                               60 hrs avg                   1 hr avg                        40 hrs avg
                320 hrs    .1 hr avg           80 hrs                     320 hrs                           80 hrs
  0.5 hrs                      8 hrs                         160 hrs                         8hrs                         100 hrs



                                                                    80 hrs


      Design                       Review                              Code                          Test                       Deploy
     40 hrs avg                    2 hrs avg            80 hrs    80 hrs avg        80 hrs      40 hrs avg           80 hrs    3 hrs avg
                     160 hrs
      120 hrs                          2 hrs                        280 hrs                         240 hrs                         8 hrs

                  20% rejected                                                 65% defective
                   Repeat 1X                                                    Repeat 3X


                                                                                                            509 hrs
                                                                                         PCE =                                = 14.9%
                                                             3433 hrs
1. Identify the actions taken in the value stream
2. Calculate calendar time for each action
3. Calculate time actually worked on the action
4. Identify time between actions
5. Identify any loop backs required            Avg Time Worked
6. Calculate Process Cycle Efficiency:         Total Cycle Time
Which gives a better return?


                         Eliminating
      Getting better
                       delays between
      at what you do
                        what you do
Approv
 Request
 Request                  Approve                        Reqts                      Sign Off
                                                                                    Sign Off                         Analysis
                                                                                                                     Analysis
 0.5 hr avg
                              e
                          .1 hr avg                     60 hrs avg                   1 hr avg                        40 hrs avg
                320 hrs    .1 hr avg       80 hrs                     320 hrs                           80 hrs
  0.5 hrs                    8 hrs                       160 hrs                         8hrs                         100 hrs



                                                                80 hrs


      Design
      Design                     Review
                                 Review                            Code                          Test                       Deploy
                                                                                                                            Deploy
     40 hrs avg                  2 hrs avg          80 hrs    80 hrs avg        80 hrs      40 hrs avg           80 hrs    3 hrs avg
                     160 hrs
      120 hrs                      2 hrs                        280 hrs                         240 hrs                         8 hrs

                  20% rejected                                             65% defective
                                                                           65% defective
                   Repeat 1X                                                Repeat 3X
                                                                             Repeat 3X


                                                                                                        509 hrs
                                                                                     PCE =                                = 14.9%
1. Identify the actions taken in the value stream             3433 hrs
2. Calculate calendar time for each action
3. Calculate time actually worked on the action
4. Identify time between actions
5. Identify any loop backs required            Avg Time Worked
                                               Avg Time Worked
6. Calculate Process Cycle Efficiency:         Total Cycle Time
                                                Total Cycle Time
kanban          by   eliminating delays
improves quality and
                        by   managing WIP
         lowers cost
Approv
 Request                                                     Reqts                      Sign Off                         Analysis
 0.5 hr avg
                            e                               60 hrs avg                   1 hr avg                        40 hrs avg
                320 hrs    .1 hr avg           80 hrs                     320 hrs                           80 hrs
  0.5 hrs                      8 hrs                         160 hrs                         8hrs                         100 hrs



                                                                    80 hrs


      Design                       Review                              Code                          Test                       Deploy
     40 hrs avg                    2 hrs avg            80 hrs    80 hrs avg        80 hrs      40 hrs avg           80 hrs    3 hrs avg
                     160 hrs
      120 hrs                          2 hrs                        280 hrs                         240 hrs                         8 hrs

                  20% rejected                                                 65% defective
                   Repeat 1X                                                    Repeat 3X


                                                                                                            509 hrs
                                                                                         PCE =                                = 14.9%
1. Identify the actions taken in the value stream            3433 hrs
2. Calculate calendar time for each action
3. Calculate time actually worked on the action
4. Identify time between actions
5. Identify any loop backs required            Avg Time Worked
6. Calculate Process Cycle Efficiency:         Total Cycle Time
‐‐ Product Managers ‐‐
Waiting for approval




320



                              visual management for WIP
‐‐ Product Managers ‐‐
                       Working on approval
Waiting for approval




                               .1
320                             8



                                             visual management for WIP
Waiting for approval




                            320
                                  Working on approval




                            .1
                             8
                                  Ready for Requirements




                            80
                                                           ‐‐ Product Managers ‐‐




visual management for WIP
Waiting for approval




                            320
                                     Working on approval




                            .1
                             8
                                     Ready for Requirements

                                     Requirements




                            80 160
                                60
                                                              ‐‐ Product Managers ‐‐




visual management for WIP
Waiting for approval




                            320
                                         Working on approval




                            .1
                             8
                                         Ready for Requirements

                                         Requirements




                                60
                                                                  ‐‐ Product Managers ‐‐




                                         Ready for sign off




                            80 160 320



visual management for WIP
‐‐ Product Managers ‐‐                                                                               ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ Development Team ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐

                                             Ready for Requirements
                       Working on approval
Waiting for approval




                                                                                     Ready for sign off
                                                                      Requirements




                                                                                                           Sign Off




                               .1                    60                                                         1
320                             8                80 160 320                                                     8



                                                                                                                                   visual management for WIP
Waiting for approval




                            320
                                         Working on approval




                            .1
                             8
                                         Ready for Requirements

                                         Requirements




                                60
                                                                  ‐‐ Product Managers ‐‐




                                         Ready for sign off




                            80 160 320
                                         Sign Off




                            1
                            8
                                         Ready for Analysis

                                         Analysis




                            80 100
                                40
                                         Ready for Design

                                         Design




                                40
                                         Ready for Review




                            80 120 160
                                         Review



                            2
                            2
                                         Ready for Code
                                80
                            80 280       Code

                                         Ready for Test

                                         Test
                            80 240
                                40




                                         Ready for Deplay
                            80




                                         Deplay
                            8
                            3




                                         Done
                                                                  ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ Development Team ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐




visual management for WIP
Waiting for approval




                            320
                                         Working on approval




                            .1
                             8
                                         Ready for Requirements

                                         Requirements




                                60
                                                                  ‐‐ Product Managers ‐‐




                                         Ready for sign off




                            80 160 320
                                         Sign Off




                            1
                            8
                                         Ready for Analysis

                                         Analysis




                            80 100
                                40
                                         Ready for Design

                                         Design




                                40
                                         Ready for Review




                            80 120 160
                                         Review



                            2
                            2
                                         Ready for Code
                                80
                            80 280       Code

                                         Ready for Test

                                         Test
                            80 240
                                40




                                         Ready for Deplay
                            80




                                         Deploy
                            8
                            3




                                         Done
                                                                  ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ Development Team ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐




visual management for WIP
Kanban suggests
                     limit # of items
 Lean suggests limit
TIME between steps being worked on in
                     each step


              time
                     size of queue
G RO U P D I S C U S S I O N
               Different Ways Available
               •Add more resource
               •Manage resources
               •Improve process
Waiting for approval

                            Working on approval

                            Ready for Requirements

                            Requirements
                                                       ‐‐ Product Managers ‐‐




                            Ready for sign off


                            Sign Off

                            Ready for Analysis

                            Analysis

                            Ready for Test Specification

                            Write Test Specification

                            Ready for Design

                            Design

                            Ready for Review

                            Review

                            Ready for Code

                            Code

                            Ready for Test

                            Test

                            Ready for Deplay

                            Deploy
                                                       ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ Development Team ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐




                            Done
visual management for WIP
Waiting for approval

                            Working on approval

                            Ready for Requirements

                            Requirements
                                                       ‐‐ Product Managers ‐‐




                            Ready for sign off


                            Sign Off

                            Ready for Analysis

                            Analysis

                            Ready for Test Specification

                            Write Test Specification

                            Ready for Design

                            Design

                            Ready for Review

                            Review

                            Ready for Code

                            Code

                            Ready for Test

                            Test

                            Ready for Deplay

                            Deploy
                                                       ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ Development Team ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐




                            Done
visual management for WIP
Feedback comes in all shapes
and sizes


                                         Dev to self



                                                                  Dev to self
           Dev/QA to 
           Customer




                                                       designer
                                                        Dev to 




                                                                                Test to 
                                                                                 dev
                                                                                                                     Deploy to 
          Analysis                   Design                       Code                Test    Integrate              customer

Requirements             Define Test                                                                        Show 
                                                                                Across teams
                        Specifications                                                                    customer

                                                                                           Customer 
                                                                                            to Dev


                                         Customer to Analyst, et. Al.
MMF
                                      MMF
      Teams work on
        Split MMF
         their part
        according to team

                           Teams work on this for
                  Development teamsintegrating
                           Eventually split
                  accordingseveral interations
                           them together
                            to components
G RO U P D I S C U S S I O N
              Teams pull from backlog
              work may be over several
              sprints
              Each team pulls
              independently
              Coordinate with Scrum-of-
              Scrums
              Integration happens:
              after each team is done
              with their entire part of
              feature
MMF
      Split MMF
      into sub-features        After one iteration, teams
                               integrate their components
                  Development teams split
                    Teams work on
                  according to components
                    their part
G RO U P D I S C U S S I O N
              Teams pull from backlog
              functionality done after
              each sprint
              forces team coordination
              can manage across teams
              If change metrics to be
              feature throughput
              then Scrum-of-Scrums
              may work because all are
              being measured the same
              way
See the Value Stream
LEAN THINKING




           Visual Controls    Workflow = Process
           Release Planning   Minimize Impediments
the SILVER card

   when and what to challenge
Managing   WIP is best
Use the right perspective
   to get out of the maze
Thank You!
Register at www.netobjectives.com/register
Contact me at alshall@netobjectives.com
Twitter tag @alshalloway
Come see me at open space




                                             copyright © 2010 Net Objectives Inc.
info@netobjectives.com   
                                                                Thank You!
    www.netobjectives.com

                                               … and following is more to help you 
                                                      plan your next steps




1                               Copyright © 2009 Net Objectives. All Rights Reserved.     29 September 2010
Resources
    Resources: www.netobjectives.com/resources 
    –   Webinars/Training Videos (PowerPoint with audio)
    –   Articles and whitepapers
    –   Pre/post course support Supporting materials
    –   Quizzes
    –   Recommended reading paths
    –   Blogs
    Annotated Bibliography
    After‐Course Support (students only)
    Additional Free On‐line Training
    User Groups
    – Business Driven Software Development
            http://www.netobjectives.com/bdsdug
    – Lean‐Agile User Group
            http://tech.groups.yahoo.com/group/leanagile 
    – Lean Programming User Group
            http://tech.groups.yahoo.com/group/leanprogramming 


        Join our e‐mail list to receive regular updates and information 
              about our resources and training of interest to you
2          Copyright © 2010 Net Objectives. All Rights Reserved.       29 September 2010
A Short List of Books ‐ Lean Related
    Lean‐Agile Software Development: Achieving Enterprise Agility. Shalloway, Beaver, 
    Trott
    Managing the Design Factory: The Product Manager’s Toolkit. Reinertsen
    Implementing Lean Software Development: From Concept to Cash. Poppendieck & 
    Poppendieck
    Lean‐Thinking. Womack & Jones
    The Toyota Way. Liker
    Toyota Production System. Ohno
    Lean Software Development: An Agile Manager’s Toolkit. Poppendieck & 
    Poppendieck
    The Principles of Product Development Flow: Second Generation Lean Development.
    Reinertsen




               See www.netobjectives.com/resources/bibliography for a full bibliography
3                                 Copyright © 2010 Net Objectives. All Rights Reserved.     29 September 2010
Lean Management and Other Relevant Books

    Peter Scholtes: The Leader’s Handbook: Making Things Happen, 
    Getting Things Done
    David Mann: Creating A Lean Culture: Tools to Sustain Lean 
    Conversions
    William Bridges: Managing Transitions
    Weick & Sutcliffe: Managing the Unexpected: Assuring High 
    Performance in an Age of Complexity
    Alexander: The Timeless Way of Building
    Shalloway & Trott: Lean‐Agile Pocket Guide for Scrum Teams




          See www.netobjectives.com/resources/bibliography for a full bibliography
4                             Copyright © 2010 Net Objectives. All Rights Reserved.     29 September 2010
A Short List of Books ‐ Technical 
    Essential Skills for the Agile Developer: A Guide to Better Programming and 
    Design. Shalloway & Bain
    Emergent Design: The Evolutionary Nature of Professional Software 
    Development. Bain
    Design Patterns Explained, A New Perspective on Object‐Oriented Design. 
    Shalloway & Trott
    Refactoring: Improving the Design of Existing Code. Fowler
    Working Effectively with Legacy Code. Feathers
    Agile Software Development: Principles, Patterns and Practices. Martin
    Head First Design Patterns. Freeman, Freeman, Bates, Sierra
    Prefactoring. Pugh
    Fit for Developing Software. Mugridge & Cunningham




              See www.netobjectives.com/resources/bibliography for a full bibliography
5                              Copyright © 2010 Net Objectives. All Rights Reserved.     29 September 2010
Upcoming Conferences
    International Conference on Lean Enterprise Software and Systems
    (LESS 2010)
    October 17‐20
    Helsinki, Finland
    CEO Alan Shalloway will be giving a tutorial
    Agile software development changed the way that software development is perceived today. 
    The journey continues now in the new era where the software business meets software 
    practice in a novel way. We are proud to present at the first International Conference on Lean 
    Enterprise Software and Systems (LESS) in collaboration with the Lean Software and Systems 
    Consortium, http://www.leanssc.org/.
    Net Objectives Presentations
     – Tutorial: Scaling Agile With the Lessons of Lean Product Development Flow –
       Wed, Oct 20, 10:30 am  – 12:30 pm




                       More information: www.netobjectives.com/conferences
6                                 Copyright © 2010 Net Objectives. All Rights Reserved.     29 September 2010
Upcoming Conferences
    Øredev 2010 Conference
    November 8‐12
    Malmö, Sweden
    Senior Consultant Cory Foy will be giving a tutorial and two sessions
    Agile Øredev is the Premier developer's conference in Europe, focused on the whole software 
    development process.  Øredev means both Quality and Quantity, by bringing the best 
    speakers and expert practitioners on a range of subjects, such as Java, .Net, Project 
    Management, Web development and Testing. Øredev reflects your universe, in motion.
    Net Objectives Presentations
     – Tutorial: Koans and Katas Oh My! – Tue, Nov 9, 8:50 am  – 12:10 pm
     – Tutorial: Delivering What's Right – Thu, Nov 11, 10:15 am  – 11:05 am
     – Tutorial: Fostering Software Craftsmanship – Fri, Nov 12, 1:10 pm  – 2:00 pm




                      More information: www.netobjectives.com/conferences
7                                Copyright © 2010 Net Objectives. All Rights Reserved.     29 September 2010
Upcoming Conferences
    Agile Development Practices | East Conference & Expo
    November 14‐19
    Orlando, FL
    Net Objectives is sponsoring the conference, as well as giving onsite courses 
    and concurrent sessions, and having a booth at the Expo
    Discover Agile Development Practices and take back the latest in agile methods, technologies, 
    tools, and leadership principles from thought leaders who deliver inspiring keynote 
    presentations, in‐depth tutorials, and a wide range of conference classes. Join industry 
    experts and peers in the agile community for a week jam‐packed with learning sessions that 
    will help you make a powerful impact in your job role and for your organization. 
    Net Objectives Presentations
     – Session: Paying Down Technical Debt – Wed, Nov 17, 12:45 pm
     – Session: Applying Lean Software Development Principles Throughout the 
       Organization – Wed, Nov 17, 2:45 pm
     – Session: Serious Games: Product Planning and Prioritization Using Innovation 
       Games®– Thu, Nov 18, 12:45 pm

                      More information: www.netobjectives.com/conferences
8                                Copyright © 2010 Net Objectives. All Rights Reserved.     29 September 2010
Upcoming Public Courses
    Charlotte, NC
     – Lean‐Agile Project Management Certification – Oct 25‐27
    Orlando, FL
    at Agile Development Practices | East 2010
    – Practical Test‐Driven Development – Nov 14 ‐ 16 
    – Scrum Master Certification – Nov 14 ‐ 16 
    Philadelphia, PA
     – Lean‐Agile Project Management Certification – Dec 7‐9




                                                                                            Conference Courses: 8:30am – 5:00pm
           More information: www.netobjectives.com/courses/                                 Other Courses:          9:00am – 5:00pm
9                                 Copyright © 2010 Net Objectives. All Rights Reserved.                                      29 September 2010
New Podcast Series

     Podcast Series for Lean Agile Straight Talk
     – First Podcast in the series available
             – September 29
             – www.netobjectives.com/blogs/new‐series
           Alan Shalloway and Jim Trott talk about what is going on in the world of 
           Lean and Agile software development.  
           They introduce Net Objectives’ 2 newest books
             – Lean‐Agile Pocket Guide for Scrum Teams
             – Lean‐Agile Software Development: Achieving Enterprise Agility
     – Later podcasts in the series
           Focus on the Lean‐Agile Pocket Guide for Scrum Teams
           A talk through each of the chapters in the Lean‐Agile Software 
           Development book.
             – Each of these chapters has good, core concepts that we want you to know 
               and this approach gives us a game plan for covering all of them. 

                        More blogs/podcasts: www.netobjectives.com/blogs
10                             Copyright © 2010 Net Objectives. All Rights Reserved.     29 September 2010
Net Objectives Services
     Training in Sustainable Product Development                          Certification Programs by Net Objectives
     Net Objectives offers the most comprehensive                         Net Objectives offers certification programs that 
     Lean‐Agile training in the world. Our offerings                      provides a road‐map of knowledge as well as 
     include Lean, Agile Analysis, Design Patterns, Test‐                 resources to get there.
     Driven Development, and Lean‐Agile Testing.                          • Lean‐Agile Project Management Certification
     Our approach is a blend of principles and practices                  • Advanced Lean‐Agile Project Management for 
     to provide a complete team and/or enterprise wide                       Scrum Masters
     training solution.                                                   • Lean Product Champion Certification
                                                                          Net Objectives is not affiliated with the Scrum Alliance

     Assessment Services                                                  Lean‐Agile Coaching
     An effective way to embark on an enterprise level                    While training provides foundational knowledge 
     transition to Lean‐Agile methods is to start with an                 and is a great jump start, coaching is another 
     assessment of where you are, where you want to go                    effective way to increase the abilities of teams. 
     and options on how to get there that are right for 
                                                                          Our coaches work with your teams to provide 
     you and your budget. 
                                                                          guidance in both the direction your teams need to 
                                                                          go and in how to get there. 
                                                                          Coaching provides the knowledge transfer while 
                                                                          working on your own problem domain. 

11                                         Copyright © 2010 Net Objectives. All Rights Reserved.                                 29 September 2010
Best Practices Curriculum
                  Lean Agile 
      Exec 
                 Overview for                                                                                                                                                        Senior Management
      Mgmt
                   Leaders


                                                                                                       Scrum Master 
     IT Mgmt
                  Agility for 
                                                                                                                                                                                         IT Management
                                                                                  Lean Software         Practitioner
                  Managers 
                   (if not taking                                                 Development 
                  Implementing                                                         For 
                  Lean‐Agile for                                                  Management
     Business       Your Team)                               Lean‐Agile                                                                                                           Business Management
      Mgmt                                                   Enterprise
                                                              Release 
                                                              Planning
                                                                                  Story Writing 
     Analyst                                                     OR               & Acceptance                                                                                                                                  Analyst
                                                                                      Tests
                                     Lean‐Agile Bootcamp




                                                                                                                                                                                         Lean‐Agile Software Development
                                                                                                                       Advanced 
                                                           Lean Product                            Lean‐Agile          Lean‐Agile 
                                                                                   Lean‐                                                                                      Lean 
                                                            Champion                                 Project             Project            Lean Software 
                                                                                   Agile                                                                                     Online 
     Process                                               Certification          Project 
                                                                                                    Manager           Management            Development                                                                        Process
                 Implementing                              By Net Objectives                      Certification                                                             Training
                   Lean‐Agile                                                     Manager                              for Scrum 
                                                                                                 By Net Objectives
                    for Your                                                                                            Masters
                     Team
                                                            Lean‐Agile 
      Tester                                                  Testing                                                  Effective          Sustainable                                                                            Tester




                                                                                                                                                          Emergent Design
                                                             Practices            Story          Implementing           Object‐           Test‐Driven 
                                                                                Writing &            Story             Oriented          Development
                                                             Technical         Acceptance         Acceptance           Analysis 
                                                                                  Tests              Tests                                                                    Design 
                                                             Training:                                                and Design
                                                                                                                                            Design                           Patterns                                        Developer
     Developer                                                C++, C#,                                                 (if needed)
                                                                                                                                          Patterns for                      Explained
                                                               Java
                                                                                                                                             Agile 
                  Database Agility                            TDD Database Boot Camp               Advanced Software Design               Developers
12                                                                             Copyright © 2009 Net Objectives. All Rights Reserved.                                                                                       29 September 2010
Net Objectives Courses
     Business ‐ Management                                     Technical Agility
      – Lean Online Training                                     – Design Patterns for Agile Developers
      – Lean Software Development Overview for                   – Sustainable Test‐Driven Development
         Executives and Management                               – Emergent Design
      – Lean‐Agile Software Development for Executives           – Acceptance Test‐Driven Development
         and Directors                                           – Implementing Story Acceptance Tests
      – Lean‐Agile Software Development for Managers and         – Database Agility Online Training
         Leads
      – Lean‐Agile Enterprise Release Planning                   – Essential Skills for the Agile Developer
      – Lean‐Agile Project Management Certification by Net       – TDD Database Boot Camp
         Objectives                                              – Advanced Software Design
     Team Agility                                                – Design Patterns Explained
      – Implementing Lean‐Agile for Your Team: Using             – Lean‐Agile Testing Practices
         Kanban, Scrumban and Scrum Effectively                  – Effective Object‐Oriented Analysis and Design
      – Kanban for Lean‐Agile Teams
      – Implementing Scrum for Your Team
      – Lean‐Agile Project Management
      – The Kanban/Scrumban/Scrum Team Bootcamp
      – Acceptance Test‐Driven Development
      – Lean‐Agile Enterprise Release Planning                                   A Top 5 Course
      – Lean‐Agile Project Management Certification by Net                        A  New Course
         Objectives
      – Advanced Lean‐Agile Project Management for 
         Scrum Masters
      – Lean Product champion Certification by Net 
         Objectives
                                   More information: www.netobjectives.com/training
13                                         Copyright © 2010 Net Objectives. All Rights Reserved.         29 September 2010
Tools We Like

     Agile Project Management Tools




14                   Copyright © 2010 Net Objectives. All Rights Reserved.     29 September 2010

Mais conteúdo relacionado

Mais procurados

Corporate presentation deck (en) 1.8 detail
Corporate presentation deck (en) 1.8  detailCorporate presentation deck (en) 1.8  detail
Corporate presentation deck (en) 1.8 detailBICorporate
 
Are good SharePoint solutions only a myth?
Are good SharePoint solutions only a myth?Are good SharePoint solutions only a myth?
Are good SharePoint solutions only a myth?Adis Jugo
 
Innovation decision making new product development process design 2 powerpoin...
Innovation decision making new product development process design 2 powerpoin...Innovation decision making new product development process design 2 powerpoin...
Innovation decision making new product development process design 2 powerpoin...SlideTeam.net
 
Yashasree barve as an architect - ai2012 - 1.0 - share
Yashasree barve   as an architect - ai2012 - 1.0 - shareYashasree barve   as an architect - ai2012 - 1.0 - share
Yashasree barve as an architect - ai2012 - 1.0 - shareyashasree
 
What next in the agile world - Alan Shalloway
What next in the agile world - Alan ShallowayWhat next in the agile world - Alan Shalloway
What next in the agile world - Alan ShallowayAGILEMinds
 
Top Ways Agile Adoption Fails, How to Avoid Them!
Top Ways Agile Adoption Fails, How to Avoid Them!Top Ways Agile Adoption Fails, How to Avoid Them!
Top Ways Agile Adoption Fails, How to Avoid Them!Sally Elatta
 
Lean Strategies for IT Support Organizations
Lean Strategies for IT Support OrganizationsLean Strategies for IT Support Organizations
Lean Strategies for IT Support OrganizationsRoger Brown
 
Agile Scrum at Double V3
Agile Scrum at Double V3Agile Scrum at Double V3
Agile Scrum at Double V3bmasse @ Nexio
 
InRhythm Introduction
InRhythm IntroductionInRhythm Introduction
InRhythm IntroductionInRhythm
 
Liftoff - how to launch Agile teams and projects
Liftoff - how to launch Agile teams and projectsLiftoff - how to launch Agile teams and projects
Liftoff - how to launch Agile teams and projectsFabio Armani
 
Aras PLM Software Implementation Methodology
Aras PLM Software Implementation MethodologyAras PLM Software Implementation Methodology
Aras PLM Software Implementation MethodologyAras
 
What is 'Just Enough' Documentation in Agile?
What is 'Just Enough' Documentation in Agile?What is 'Just Enough' Documentation in Agile?
What is 'Just Enough' Documentation in Agile?Sally Elatta
 
Lean Agile Adoption Enterprise Challenges - XP 2012
Lean Agile Adoption Enterprise Challenges - XP 2012Lean Agile Adoption Enterprise Challenges - XP 2012
Lean Agile Adoption Enterprise Challenges - XP 2012Fabio Armani
 
Confessions of a Coach
Confessions of a CoachConfessions of a Coach
Confessions of a CoachMarko Taipale
 
Overview of Agile for Business Analysts
Overview of Agile for Business AnalystsOverview of Agile for Business Analysts
Overview of Agile for Business AnalystsSally Elatta
 
2012 04 18 Knoxville Agile Adoption&Adaptation
2012 04 18 Knoxville Agile Adoption&Adaptation2012 04 18 Knoxville Agile Adoption&Adaptation
2012 04 18 Knoxville Agile Adoption&Adaptationalstonhodge
 

Mais procurados (20)

Corporate presentation deck (en) 1.8 detail
Corporate presentation deck (en) 1.8  detailCorporate presentation deck (en) 1.8  detail
Corporate presentation deck (en) 1.8 detail
 
Are good SharePoint solutions only a myth?
Are good SharePoint solutions only a myth?Are good SharePoint solutions only a myth?
Are good SharePoint solutions only a myth?
 
Innovation decision making new product development process design 2 powerpoin...
Innovation decision making new product development process design 2 powerpoin...Innovation decision making new product development process design 2 powerpoin...
Innovation decision making new product development process design 2 powerpoin...
 
Yashasree barve as an architect - ai2012 - 1.0 - share
Yashasree barve   as an architect - ai2012 - 1.0 - shareYashasree barve   as an architect - ai2012 - 1.0 - share
Yashasree barve as an architect - ai2012 - 1.0 - share
 
What next in the agile world - Alan Shalloway
What next in the agile world - Alan ShallowayWhat next in the agile world - Alan Shalloway
What next in the agile world - Alan Shalloway
 
Lean Ofis Presentation
Lean Ofis PresentationLean Ofis Presentation
Lean Ofis Presentation
 
Top Ways Agile Adoption Fails, How to Avoid Them!
Top Ways Agile Adoption Fails, How to Avoid Them!Top Ways Agile Adoption Fails, How to Avoid Them!
Top Ways Agile Adoption Fails, How to Avoid Them!
 
Lean Strategies for IT Support Organizations
Lean Strategies for IT Support OrganizationsLean Strategies for IT Support Organizations
Lean Strategies for IT Support Organizations
 
Agile marries itil
Agile marries itilAgile marries itil
Agile marries itil
 
TejaServices 2.0 Model
TejaServices 2.0 ModelTejaServices 2.0 Model
TejaServices 2.0 Model
 
Imaginea qa&automation
Imaginea qa&automationImaginea qa&automation
Imaginea qa&automation
 
Agile Scrum at Double V3
Agile Scrum at Double V3Agile Scrum at Double V3
Agile Scrum at Double V3
 
InRhythm Introduction
InRhythm IntroductionInRhythm Introduction
InRhythm Introduction
 
Liftoff - how to launch Agile teams and projects
Liftoff - how to launch Agile teams and projectsLiftoff - how to launch Agile teams and projects
Liftoff - how to launch Agile teams and projects
 
Aras PLM Software Implementation Methodology
Aras PLM Software Implementation MethodologyAras PLM Software Implementation Methodology
Aras PLM Software Implementation Methodology
 
What is 'Just Enough' Documentation in Agile?
What is 'Just Enough' Documentation in Agile?What is 'Just Enough' Documentation in Agile?
What is 'Just Enough' Documentation in Agile?
 
Lean Agile Adoption Enterprise Challenges - XP 2012
Lean Agile Adoption Enterprise Challenges - XP 2012Lean Agile Adoption Enterprise Challenges - XP 2012
Lean Agile Adoption Enterprise Challenges - XP 2012
 
Confessions of a Coach
Confessions of a CoachConfessions of a Coach
Confessions of a Coach
 
Overview of Agile for Business Analysts
Overview of Agile for Business AnalystsOverview of Agile for Business Analysts
Overview of Agile for Business Analysts
 
2012 04 18 Knoxville Agile Adoption&Adaptation
2012 04 18 Knoxville Agile Adoption&Adaptation2012 04 18 Knoxville Agile Adoption&Adaptation
2012 04 18 Knoxville Agile Adoption&Adaptation
 

Destaque

China's consumer market a huge opportunity to fail
China's consumer market   a huge opportunity to failChina's consumer market   a huge opportunity to fail
China's consumer market a huge opportunity to failtusharikhar
 
Alan shalloway lean-kanban is about people
Alan shalloway   lean-kanban is about peopleAlan shalloway   lean-kanban is about people
Alan shalloway lean-kanban is about peopleAGILEMinds
 
AgileJapan2010 Alan Shalloway's keynote: What Is Next In the Agile World - Ja...
AgileJapan2010 Alan Shalloway's keynote: What Is Next In the Agile World - Ja...AgileJapan2010 Alan Shalloway's keynote: What Is Next In the Agile World - Ja...
AgileJapan2010 Alan Shalloway's keynote: What Is Next In the Agile World - Ja...Kenji Hiranabe
 
Lean Software Development Alan Shalloway
Lean Software Development   Alan ShallowayLean Software Development   Alan Shalloway
Lean Software Development Alan ShallowayValtech UK
 
Agile101 Small Batches
Agile101 Small BatchesAgile101 Small Batches
Agile101 Small BatchesSteve Rogalsky
 
Managing product development flow across an IT organization
Managing product development flow across an IT organizationManaging product development flow across an IT organization
Managing product development flow across an IT organizationInstitut Lean France
 
3 Things Every Sales Team Needs to Be Thinking About in 2017
3 Things Every Sales Team Needs to Be Thinking About in 20173 Things Every Sales Team Needs to Be Thinking About in 2017
3 Things Every Sales Team Needs to Be Thinking About in 2017Drift
 

Destaque (7)

China's consumer market a huge opportunity to fail
China's consumer market   a huge opportunity to failChina's consumer market   a huge opportunity to fail
China's consumer market a huge opportunity to fail
 
Alan shalloway lean-kanban is about people
Alan shalloway   lean-kanban is about peopleAlan shalloway   lean-kanban is about people
Alan shalloway lean-kanban is about people
 
AgileJapan2010 Alan Shalloway's keynote: What Is Next In the Agile World - Ja...
AgileJapan2010 Alan Shalloway's keynote: What Is Next In the Agile World - Ja...AgileJapan2010 Alan Shalloway's keynote: What Is Next In the Agile World - Ja...
AgileJapan2010 Alan Shalloway's keynote: What Is Next In the Agile World - Ja...
 
Lean Software Development Alan Shalloway
Lean Software Development   Alan ShallowayLean Software Development   Alan Shalloway
Lean Software Development Alan Shalloway
 
Agile101 Small Batches
Agile101 Small BatchesAgile101 Small Batches
Agile101 Small Batches
 
Managing product development flow across an IT organization
Managing product development flow across an IT organizationManaging product development flow across an IT organization
Managing product development flow across an IT organization
 
3 Things Every Sales Team Needs to Be Thinking About in 2017
3 Things Every Sales Team Needs to Be Thinking About in 20173 Things Every Sales Team Needs to Be Thinking About in 2017
3 Things Every Sales Team Needs to Be Thinking About in 2017
 

Semelhante a Seeing what matters using the right vision to manage transition - Alan Shalloway

Envisioning improving productivity and qaulity through better backlogs agi...
Envisioning   improving productivity and qaulity through better backlogs  agi...Envisioning   improving productivity and qaulity through better backlogs  agi...
Envisioning improving productivity and qaulity through better backlogs agi...Tatlock
 
Webinar on PRINCE2 + Agile - by Ashish Dhoke (projectingIT)
Webinar on PRINCE2 + Agile - by Ashish Dhoke (projectingIT)Webinar on PRINCE2 + Agile - by Ashish Dhoke (projectingIT)
Webinar on PRINCE2 + Agile - by Ashish Dhoke (projectingIT)projectingIT
 
PMI Ireland Annual Conference 2012 - Agile First Steps
PMI Ireland Annual Conference 2012 - Agile First StepsPMI Ireland Annual Conference 2012 - Agile First Steps
PMI Ireland Annual Conference 2012 - Agile First StepsColm O'hEocha
 
Requirements & scope
Requirements & scopeRequirements & scope
Requirements & scopeCraig Brown
 
Lean Thinking on Business Analysis
Lean Thinking on Business AnalysisLean Thinking on Business Analysis
Lean Thinking on Business AnalysisLuiz C. Parzianello
 
Pulse Design & Delivery Panel
Pulse Design & Delivery PanelPulse Design & Delivery Panel
Pulse Design & Delivery PanelMauricio Godoy
 
Radovan Janecek Avoiding S O A Pitfalls
Radovan  Janecek   Avoiding  S O A  PitfallsRadovan  Janecek   Avoiding  S O A  Pitfalls
Radovan Janecek Avoiding S O A PitfallsSOA Symposium
 
Business analysis and project changes
Business analysis and project changesBusiness analysis and project changes
Business analysis and project changesIIBA Romania Chapter
 
Agile Developers Create Their Own Identity
Agile Developers Create Their Own IdentityAgile Developers Create Their Own Identity
Agile Developers Create Their Own IdentityAjay Danait
 
Chasing code quality in huge multi-location team project
Chasing code quality in huge multi-location team projectChasing code quality in huge multi-location team project
Chasing code quality in huge multi-location team projectAgile Lietuva
 
Sigis jermolovicius chasing code quality in huge multi location team project
Sigis jermolovicius chasing code quality in huge multi location team projectSigis jermolovicius chasing code quality in huge multi location team project
Sigis jermolovicius chasing code quality in huge multi location team projectAgile Lietuva
 
IBM Rational Software Conference 2009 Day 1 Keynote: Jamie Thomas
IBM Rational Software Conference 2009 Day 1 Keynote: Jamie ThomasIBM Rational Software Conference 2009 Day 1 Keynote: Jamie Thomas
IBM Rational Software Conference 2009 Day 1 Keynote: Jamie ThomasKathy (Kat) Mandelstein
 
Application Lifecycle Management & VSTS
Application Lifecycle Management & VSTSApplication Lifecycle Management & VSTS
Application Lifecycle Management & VSTSMicrosoft Iceland
 
Agile developers create their own identity by Ajay Danait
Agile developers create their own identity by Ajay DanaitAgile developers create their own identity by Ajay Danait
Agile developers create their own identity by Ajay DanaitXebia IT Architects
 
Ajel Corporate Profile (RPO)
Ajel Corporate Profile (RPO)Ajel Corporate Profile (RPO)
Ajel Corporate Profile (RPO)AjelTechnologies
 
Agile v agility_v4_md
Agile v agility_v4_mdAgile v agility_v4_md
Agile v agility_v4_mdMarc Danziger
 
Portfolio Planning for 2013 - Keeping It Basic
Portfolio Planning for 2013 - Keeping It BasicPortfolio Planning for 2013 - Keeping It Basic
Portfolio Planning for 2013 - Keeping It BasicEPM Live
 
Installing PMS in shamelin - a proposal
Installing PMS in shamelin -  a proposalInstalling PMS in shamelin -  a proposal
Installing PMS in shamelin - a proposalHj Arriffin Mansor
 

Semelhante a Seeing what matters using the right vision to manage transition - Alan Shalloway (20)

Envisioning improving productivity and qaulity through better backlogs agi...
Envisioning   improving productivity and qaulity through better backlogs  agi...Envisioning   improving productivity and qaulity through better backlogs  agi...
Envisioning improving productivity and qaulity through better backlogs agi...
 
Webinar on PRINCE2 + Agile - by Ashish Dhoke (projectingIT)
Webinar on PRINCE2 + Agile - by Ashish Dhoke (projectingIT)Webinar on PRINCE2 + Agile - by Ashish Dhoke (projectingIT)
Webinar on PRINCE2 + Agile - by Ashish Dhoke (projectingIT)
 
PMI Ireland Annual Conference 2012 - Agile First Steps
PMI Ireland Annual Conference 2012 - Agile First StepsPMI Ireland Annual Conference 2012 - Agile First Steps
PMI Ireland Annual Conference 2012 - Agile First Steps
 
Requirements & scope
Requirements & scopeRequirements & scope
Requirements & scope
 
Lean Thinking on Business Analysis
Lean Thinking on Business AnalysisLean Thinking on Business Analysis
Lean Thinking on Business Analysis
 
Pulse Design & Delivery Panel
Pulse Design & Delivery PanelPulse Design & Delivery Panel
Pulse Design & Delivery Panel
 
Radovan Janecek Avoiding S O A Pitfalls
Radovan  Janecek   Avoiding  S O A  PitfallsRadovan  Janecek   Avoiding  S O A  Pitfalls
Radovan Janecek Avoiding S O A Pitfalls
 
Business analysis and project changes
Business analysis and project changesBusiness analysis and project changes
Business analysis and project changes
 
Agile Developers Create Their Own Identity
Agile Developers Create Their Own IdentityAgile Developers Create Their Own Identity
Agile Developers Create Their Own Identity
 
Agile at AT&T
Agile at AT&TAgile at AT&T
Agile at AT&T
 
Chasing code quality in huge multi-location team project
Chasing code quality in huge multi-location team projectChasing code quality in huge multi-location team project
Chasing code quality in huge multi-location team project
 
Sigis jermolovicius chasing code quality in huge multi location team project
Sigis jermolovicius chasing code quality in huge multi location team projectSigis jermolovicius chasing code quality in huge multi location team project
Sigis jermolovicius chasing code quality in huge multi location team project
 
IBM Rational Software Conference 2009 Day 1 Keynote: Jamie Thomas
IBM Rational Software Conference 2009 Day 1 Keynote: Jamie ThomasIBM Rational Software Conference 2009 Day 1 Keynote: Jamie Thomas
IBM Rational Software Conference 2009 Day 1 Keynote: Jamie Thomas
 
Application Lifecycle Management & VSTS
Application Lifecycle Management & VSTSApplication Lifecycle Management & VSTS
Application Lifecycle Management & VSTS
 
Alten calsoft labs corporate Info
Alten calsoft labs   corporate InfoAlten calsoft labs   corporate Info
Alten calsoft labs corporate Info
 
Agile developers create their own identity by Ajay Danait
Agile developers create their own identity by Ajay DanaitAgile developers create their own identity by Ajay Danait
Agile developers create their own identity by Ajay Danait
 
Ajel Corporate Profile (RPO)
Ajel Corporate Profile (RPO)Ajel Corporate Profile (RPO)
Ajel Corporate Profile (RPO)
 
Agile v agility_v4_md
Agile v agility_v4_mdAgile v agility_v4_md
Agile v agility_v4_md
 
Portfolio Planning for 2013 - Keeping It Basic
Portfolio Planning for 2013 - Keeping It BasicPortfolio Planning for 2013 - Keeping It Basic
Portfolio Planning for 2013 - Keeping It Basic
 
Installing PMS in shamelin - a proposal
Installing PMS in shamelin -  a proposalInstalling PMS in shamelin -  a proposal
Installing PMS in shamelin - a proposal
 

Mais de AGILEMinds

Lean Startup - Customer Development - Aarrr metrics
Lean Startup - Customer Development - Aarrr metricsLean Startup - Customer Development - Aarrr metrics
Lean Startup - Customer Development - Aarrr metricsAGILEMinds
 
Sami honkonen scheduling work in kanban
Sami honkonen   scheduling work in kanbanSami honkonen   scheduling work in kanban
Sami honkonen scheduling work in kanbanAGILEMinds
 
Patrick steyaert lean adaptive management - achieving complex business goal...
Patrick steyaert   lean adaptive management - achieving complex business goal...Patrick steyaert   lean adaptive management - achieving complex business goal...
Patrick steyaert lean adaptive management - achieving complex business goal...AGILEMinds
 
Olav maassen risk management
Olav maassen   risk managementOlav maassen   risk management
Olav maassen risk managementAGILEMinds
 
Nick boucart lean startups
Nick boucart   lean startupsNick boucart   lean startups
Nick boucart lean startupsAGILEMinds
 
Mike burrows level demand, balance workload and manage schedule risk with c...
Mike burrows   level demand, balance workload and manage schedule risk with c...Mike burrows   level demand, balance workload and manage schedule risk with c...
Mike burrows level demand, balance workload and manage schedule risk with c...AGILEMinds
 
Michael kennedy set-based decision making taming system complexity
Michael kennedy   set-based decision making taming system complexityMichael kennedy   set-based decision making taming system complexity
Michael kennedy set-based decision making taming system complexityAGILEMinds
 
Mattias skarin what would you do - analysing charts
Mattias skarin   what would you do - analysing chartsMattias skarin   what would you do - analysing charts
Mattias skarin what would you do - analysing chartsAGILEMinds
 
Matthias bohlen team and contracts
Matthias bohlen   team and contractsMatthias bohlen   team and contracts
Matthias bohlen team and contractsAGILEMinds
 
Mark robinson what does lean mean for software testing
Mark robinson   what does lean mean for software testingMark robinson   what does lean mean for software testing
Mark robinson what does lean mean for software testingAGILEMinds
 
Karl scotland science of kanban
Karl scotland   science of kanbanKarl scotland   science of kanban
Karl scotland science of kanbanAGILEMinds
 
Jurgen de smet yves hanoulle real options
Jurgen de smet yves hanoulle   real optionsJurgen de smet yves hanoulle   real options
Jurgen de smet yves hanoulle real optionsAGILEMinds
 
John seddon it’s the system stupid!
John seddon   it’s the system stupid!John seddon   it’s the system stupid!
John seddon it’s the system stupid!AGILEMinds
 
Jasper sonnevelt pitfalls of a large kanban implementation
Jasper sonnevelt   pitfalls of a large kanban implementationJasper sonnevelt   pitfalls of a large kanban implementation
Jasper sonnevelt pitfalls of a large kanban implementationAGILEMinds
 
Jason yip kanban for it operations
Jason yip   kanban for it operationsJason yip   kanban for it operations
Jason yip kanban for it operationsAGILEMinds
 
Eric willeke when models collide
Eric willeke   when models collideEric willeke   when models collide
Eric willeke when models collideAGILEMinds
 
Don reinertsen is it time to rethink deming
Don reinertsen   is it time to rethink demingDon reinertsen   is it time to rethink deming
Don reinertsen is it time to rethink demingAGILEMinds
 
David joyce jalipo build it and they will come
David joyce   jalipo build it and they will comeDavid joyce   jalipo build it and they will come
David joyce jalipo build it and they will comeAGILEMinds
 
David anderson kanban when is it not appropriate
David anderson   kanban when is it not appropriateDavid anderson   kanban when is it not appropriate
David anderson kanban when is it not appropriateAGILEMinds
 
Dave snowden practice without sound theory will not scale
Dave snowden   practice without sound theory will not scaleDave snowden   practice without sound theory will not scale
Dave snowden practice without sound theory will not scaleAGILEMinds
 

Mais de AGILEMinds (20)

Lean Startup - Customer Development - Aarrr metrics
Lean Startup - Customer Development - Aarrr metricsLean Startup - Customer Development - Aarrr metrics
Lean Startup - Customer Development - Aarrr metrics
 
Sami honkonen scheduling work in kanban
Sami honkonen   scheduling work in kanbanSami honkonen   scheduling work in kanban
Sami honkonen scheduling work in kanban
 
Patrick steyaert lean adaptive management - achieving complex business goal...
Patrick steyaert   lean adaptive management - achieving complex business goal...Patrick steyaert   lean adaptive management - achieving complex business goal...
Patrick steyaert lean adaptive management - achieving complex business goal...
 
Olav maassen risk management
Olav maassen   risk managementOlav maassen   risk management
Olav maassen risk management
 
Nick boucart lean startups
Nick boucart   lean startupsNick boucart   lean startups
Nick boucart lean startups
 
Mike burrows level demand, balance workload and manage schedule risk with c...
Mike burrows   level demand, balance workload and manage schedule risk with c...Mike burrows   level demand, balance workload and manage schedule risk with c...
Mike burrows level demand, balance workload and manage schedule risk with c...
 
Michael kennedy set-based decision making taming system complexity
Michael kennedy   set-based decision making taming system complexityMichael kennedy   set-based decision making taming system complexity
Michael kennedy set-based decision making taming system complexity
 
Mattias skarin what would you do - analysing charts
Mattias skarin   what would you do - analysing chartsMattias skarin   what would you do - analysing charts
Mattias skarin what would you do - analysing charts
 
Matthias bohlen team and contracts
Matthias bohlen   team and contractsMatthias bohlen   team and contracts
Matthias bohlen team and contracts
 
Mark robinson what does lean mean for software testing
Mark robinson   what does lean mean for software testingMark robinson   what does lean mean for software testing
Mark robinson what does lean mean for software testing
 
Karl scotland science of kanban
Karl scotland   science of kanbanKarl scotland   science of kanban
Karl scotland science of kanban
 
Jurgen de smet yves hanoulle real options
Jurgen de smet yves hanoulle   real optionsJurgen de smet yves hanoulle   real options
Jurgen de smet yves hanoulle real options
 
John seddon it’s the system stupid!
John seddon   it’s the system stupid!John seddon   it’s the system stupid!
John seddon it’s the system stupid!
 
Jasper sonnevelt pitfalls of a large kanban implementation
Jasper sonnevelt   pitfalls of a large kanban implementationJasper sonnevelt   pitfalls of a large kanban implementation
Jasper sonnevelt pitfalls of a large kanban implementation
 
Jason yip kanban for it operations
Jason yip   kanban for it operationsJason yip   kanban for it operations
Jason yip kanban for it operations
 
Eric willeke when models collide
Eric willeke   when models collideEric willeke   when models collide
Eric willeke when models collide
 
Don reinertsen is it time to rethink deming
Don reinertsen   is it time to rethink demingDon reinertsen   is it time to rethink deming
Don reinertsen is it time to rethink deming
 
David joyce jalipo build it and they will come
David joyce   jalipo build it and they will comeDavid joyce   jalipo build it and they will come
David joyce jalipo build it and they will come
 
David anderson kanban when is it not appropriate
David anderson   kanban when is it not appropriateDavid anderson   kanban when is it not appropriate
David anderson kanban when is it not appropriate
 
Dave snowden practice without sound theory will not scale
Dave snowden   practice without sound theory will not scaleDave snowden   practice without sound theory will not scale
Dave snowden practice without sound theory will not scale
 

Seeing what matters using the right vision to manage transition - Alan Shalloway

  • 1. Seeing What Matters Using the Right Vision to Manage Transition © copyright 2010. Net Objectives, Inc.
  • 2. Lean for Executives Product Portfolio ASSESSMENTS Management CONSULTING Business T RAINING COACHING Lean Enterprise Manage Team ment technical process Kanban / Scrum Lean Management ATDD / TDD / Design Patterns Project Management
  • 3.
  • 4. Agenda • What we want • Why we can’t get there directly • Manifesting visibility
  • 5. What We Want More productivity Higher quality Lower cost Faster delivery copyright © 2010 Net Objectives Inc. ~a _so
  • 6. G RO U P D I S C U S S I O N Lower costs Raising productivity
  • 7. What do people look at? Business Return Managers Cost Developers # of features implemented Testers # of bugs found Integrators # of integration errors Customers How it helps them – pain of use
  • 8. • How can I improve  our time to market? • How can I improve  visibility? • How do I get  predictability? • How do I measure my  success so I can both  ensure it as well as  know I’ve achieved it?  
  • 9. Enterprise Agility Ability to add value quickly copyright © 2010 Net Objectives Inc.
  • 10.
  • 11.
  • 12.
  • 14.
  • 16. Consider • Want enterprise agility • Difference between scaling agility and agility at scale • Team agility is a means, not an end
  • 17. Challenges • Defining business value • Quick turn-around from dev teams
  • 18. Improving Time to Market copyright © 2010 Net Objectives Inc.
  • 19. Business value realized release release release release PARETO
  • 20. Business value realized release Time MINIMUM BUILD RELEASE release
  • 21. Business value realized Time release WATERFALL?
  • 22. Business value realized release Time release BLEND release
  • 23.
  • 24. Improving Predictability copyright © 2010 Net Objectives Inc.
  • 25. Challenges • Building wrong stuff • Quality of code • Overloaded teams • Inefficiency of the team • Coordination problems • Deployment problems
  • 26. Metrics for Success copyright © 2010 Net Objectives Inc.
  • 27. Here’s a thought • Measure what you want to achieve TIME TO MARKET
  • 28. Visualizing Flow copyright © 2010 Net Objectives Inc.
  • 29. Concept Regional Coordinators New Business Leaders Requirements Customers Trainers & Educators Product Managers Consumption Customer Business Product Champion(s) Capabilities Support Product Related Software Software Shared  Product Release Components Shared  Product Related Components Development The Continuous Flow of Technology Solution Delivery
  • 30. Principles for Lean-Agile Management 1. Visibility - See the Value Stream 2. Flow Limit Work to Capacity Manage Work in Progress Remove Delays 3. Build in Quality thinking points
  • 31. Approv Request Reqts Sign Off Analysis e Design Review Code Test Deploy 1. Identify the actions taken in the value stream
  • 32. Approv Request Reqts Sign Off Analysis e 0.5 hrs 8 hrs 160 hrs 8 hrs 100 hrs Design Review Code Test Deploy 120 hrs 2 hrs 280 hrs 240 hrs 8 hrs 1. Identify the actions taken in the value stream 2. Calculate calendar time for each action
  • 33. Approv Request Reqts Sign Off Analysis 0.5 hr avg e 60 hrs avg 1 hr avg 40 hrs avg .1 hr avg 0.5 hrs 8 hrs 160 hrs 8hrs 100 hrs Design Review Code Test Deploy 40 hrs avg 2 hrs avg 80 hrs avg 40 hrs avg 3 hrs avg 120 hrs 2 hrs 280 hrs 240 hrs 8 hrs 1. Identify the actions taken in the value stream 2. Calculate calendar time for each action 3. Calculate time actually worked on the action
  • 34. Approv Request Reqts Sign Off Analysis 0.5 hr avg e 60 hrs avg 1 hr avg 40 hrs avg 320 hrs .1 hr avg 80 hrs 320 hrs 80 hrs 0.5 hrs 8 hrs 160 hrs 8hrs 100 hrs 80 hrs Design Review Code Test Deploy 40 hrs avg 2 hrs avg 80 hrs 80 hrs avg 80 hrs 40 hrs avg 80 hrs 3 hrs avg 160 hrs 120 hrs 2 hrs 280 hrs 240 hrs 8 hrs 1. Identify the actions taken in the value stream 2. Calculate calendar time for each action 3. Calculate time actually worked on the action 4. Identify time between actions
  • 35. Approv Request Reqts Sign Off Analysis 0.5 hr avg e 60 hrs avg 1 hr avg 40 hrs avg 320 hrs .1 hr avg 80 hrs 320 hrs 80 hrs 0.5 hrs 8 hrs 160 hrs 8hrs 100 hrs 80 hrs Design Review Code Test Deploy 40 hrs avg 2 hrs avg 80 hrs 80 hrs avg 80 hrs 40 hrs avg 80 hrs 3 hrs avg 160 hrs 120 hrs 2 hrs 280 hrs 240 hrs 8 hrs 20% rejected 65% defective Repeat 1X Repeat 3X 1. Identify the actions taken in the value stream 2. Calculate calendar time for each action 3. Calculate time actually worked on the action 4. Identify time between actions 5. Identify any loop backs required 27 September 2010
  • 36. Approv Request Reqts Sign Off Analysis 0.5 hr avg e 60 hrs avg 1 hr avg 40 hrs avg 320 hrs .1 hr avg 80 hrs 320 hrs 80 hrs 0.5 hrs 8 hrs 160 hrs 8hrs 100 hrs 80 hrs Design Review Code Test Deploy 40 hrs avg 2 hrs avg 80 hrs 80 hrs avg 80 hrs 40 hrs avg 80 hrs 3 hrs avg 160 hrs 120 hrs 2 hrs 280 hrs 240 hrs 8 hrs 20% rejected 65% defective Repeat 1X Repeat 3X 509 hrs PCE = = 14.9% 1. Identify the actions taken in the value stream 3433 hrs 2. Calculate calendar time for each action 3. Calculate time actually worked on the action 4. Identify time between actions 5. Identify any loop backs required Avg Time Worked 6. Calculate Process Cycle Efficiency: Total Cycle Time
  • 37. Approv Request Reqts Sign Off Analysis 0.5 hr avg e 60 hrs avg 1 hr avg 40 hrs avg 320 hrs .1 hr avg 80 hrs 320 hrs 80 hrs 0.5 hrs 8 hrs 160 hrs 8hrs 100 hrs 80 hrs Design Review Code Test Deploy 40 hrs avg 2 hrs avg 80 hrs 80 hrs avg 80 hrs 40 hrs avg 80 hrs 3 hrs avg 160 hrs 120 hrs 2 hrs 280 hrs 240 hrs 8 hrs 20% rejected 65% defective Repeat 1X Repeat 3X 509 hrs PCE = = 14.9% 1. Identify the actions taken in the value stream 3433 hrs 2. Calculate calendar time for each action 3. Calculate time actually worked on the action 4. Identify time between actions 5. Identify any loop backs required Avg Time Worked 6. Calculate Process Cycle Efficiency: Total Cycle Time
  • 38. Approv Request Reqts Sign Off Analysis 0.5 hr avg e 60 hrs avg 1 hr avg 40 hrs avg 320 hrs .1 hr avg 80 hrs 320 hrs 80 hrs 0.5 hrs 8 hrs 160 hrs 8hrs 100 hrs 80 hrs Design Review Code Test Deploy 40 hrs avg 2 hrs avg 80 hrs 80 hrs avg 80 hrs 40 hrs avg 80 hrs 3 hrs avg 160 hrs 120 hrs 2 hrs 280 hrs 240 hrs 8 hrs 20% rejected 65% defective Repeat 1X Repeat 3X 509 hrs PCE = = 14.9% 3433 hrs 1. Identify the actions taken in the value stream 2. Calculate calendar time for each action 3. Calculate time actually worked on the action 4. Identify time between actions 5. Identify any loop backs required Avg Time Worked 6. Calculate Process Cycle Efficiency: Total Cycle Time
  • 39. Which gives a better return? Eliminating Getting better delays between at what you do what you do
  • 40. Approv Request Request Approve Reqts Sign Off Sign Off Analysis Analysis 0.5 hr avg e .1 hr avg 60 hrs avg 1 hr avg 40 hrs avg 320 hrs .1 hr avg 80 hrs 320 hrs 80 hrs 0.5 hrs 8 hrs 160 hrs 8hrs 100 hrs 80 hrs Design Design Review Review Code Test Deploy Deploy 40 hrs avg 2 hrs avg 80 hrs 80 hrs avg 80 hrs 40 hrs avg 80 hrs 3 hrs avg 160 hrs 120 hrs 2 hrs 280 hrs 240 hrs 8 hrs 20% rejected 65% defective 65% defective Repeat 1X Repeat 3X Repeat 3X 509 hrs PCE = = 14.9% 1. Identify the actions taken in the value stream 3433 hrs 2. Calculate calendar time for each action 3. Calculate time actually worked on the action 4. Identify time between actions 5. Identify any loop backs required Avg Time Worked Avg Time Worked 6. Calculate Process Cycle Efficiency: Total Cycle Time Total Cycle Time
  • 41. kanban by eliminating delays improves quality and by managing WIP lowers cost
  • 42. Approv Request Reqts Sign Off Analysis 0.5 hr avg e 60 hrs avg 1 hr avg 40 hrs avg 320 hrs .1 hr avg 80 hrs 320 hrs 80 hrs 0.5 hrs 8 hrs 160 hrs 8hrs 100 hrs 80 hrs Design Review Code Test Deploy 40 hrs avg 2 hrs avg 80 hrs 80 hrs avg 80 hrs 40 hrs avg 80 hrs 3 hrs avg 160 hrs 120 hrs 2 hrs 280 hrs 240 hrs 8 hrs 20% rejected 65% defective Repeat 1X Repeat 3X 509 hrs PCE = = 14.9% 1. Identify the actions taken in the value stream 3433 hrs 2. Calculate calendar time for each action 3. Calculate time actually worked on the action 4. Identify time between actions 5. Identify any loop backs required Avg Time Worked 6. Calculate Process Cycle Efficiency: Total Cycle Time
  • 44. ‐‐ Product Managers ‐‐ Working on approval Waiting for approval .1 320 8 visual management for WIP
  • 45. Waiting for approval 320 Working on approval .1 8 Ready for Requirements 80 ‐‐ Product Managers ‐‐ visual management for WIP
  • 46. Waiting for approval 320 Working on approval .1 8 Ready for Requirements Requirements 80 160 60 ‐‐ Product Managers ‐‐ visual management for WIP
  • 47. Waiting for approval 320 Working on approval .1 8 Ready for Requirements Requirements 60 ‐‐ Product Managers ‐‐ Ready for sign off 80 160 320 visual management for WIP
  • 48. ‐‐ Product Managers ‐‐ ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ Development Team ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ Ready for Requirements Working on approval Waiting for approval Ready for sign off Requirements Sign Off .1 60 1 320 8 80 160 320 8 visual management for WIP
  • 49. Waiting for approval 320 Working on approval .1 8 Ready for Requirements Requirements 60 ‐‐ Product Managers ‐‐ Ready for sign off 80 160 320 Sign Off 1 8 Ready for Analysis Analysis 80 100 40 Ready for Design Design 40 Ready for Review 80 120 160 Review 2 2 Ready for Code 80 80 280 Code Ready for Test Test 80 240 40 Ready for Deplay 80 Deplay 8 3 Done ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ Development Team ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ visual management for WIP
  • 50. Waiting for approval 320 Working on approval .1 8 Ready for Requirements Requirements 60 ‐‐ Product Managers ‐‐ Ready for sign off 80 160 320 Sign Off 1 8 Ready for Analysis Analysis 80 100 40 Ready for Design Design 40 Ready for Review 80 120 160 Review 2 2 Ready for Code 80 80 280 Code Ready for Test Test 80 240 40 Ready for Deplay 80 Deploy 8 3 Done ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ Development Team ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ visual management for WIP
  • 51. Kanban suggests limit # of items Lean suggests limit TIME between steps being worked on in each step time size of queue
  • 52. G RO U P D I S C U S S I O N Different Ways Available •Add more resource •Manage resources •Improve process
  • 53. Waiting for approval Working on approval Ready for Requirements Requirements ‐‐ Product Managers ‐‐ Ready for sign off Sign Off Ready for Analysis Analysis Ready for Test Specification Write Test Specification Ready for Design Design Ready for Review Review Ready for Code Code Ready for Test Test Ready for Deplay Deploy ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ Development Team ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ Done visual management for WIP
  • 54. Waiting for approval Working on approval Ready for Requirements Requirements ‐‐ Product Managers ‐‐ Ready for sign off Sign Off Ready for Analysis Analysis Ready for Test Specification Write Test Specification Ready for Design Design Ready for Review Review Ready for Code Code Ready for Test Test Ready for Deplay Deploy ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ Development Team ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ Done visual management for WIP
  • 55. Feedback comes in all shapes and sizes Dev to self Dev to self Dev/QA to  Customer designer Dev to  Test to  dev Deploy to  Analysis Design Code Test Integrate customer Requirements Define Test  Show  Across teams Specifications customer Customer  to Dev Customer to Analyst, et. Al.
  • 56. MMF MMF Teams work on Split MMF their part according to team Teams work on this for Development teamsintegrating Eventually split accordingseveral interations them together to components
  • 57. G RO U P D I S C U S S I O N Teams pull from backlog work may be over several sprints Each team pulls independently Coordinate with Scrum-of- Scrums Integration happens: after each team is done with their entire part of feature
  • 58. MMF Split MMF into sub-features After one iteration, teams integrate their components Development teams split Teams work on according to components their part
  • 59. G RO U P D I S C U S S I O N Teams pull from backlog functionality done after each sprint forces team coordination can manage across teams If change metrics to be feature throughput then Scrum-of-Scrums may work because all are being measured the same way
  • 60. See the Value Stream LEAN THINKING Visual Controls Workflow = Process Release Planning Minimize Impediments
  • 61.
  • 62. the SILVER card when and what to challenge
  • 63. Managing WIP is best
  • 64. Use the right perspective to get out of the maze
  • 65. Thank You! Register at www.netobjectives.com/register Contact me at alshall@netobjectives.com Twitter tag @alshalloway Come see me at open space copyright © 2010 Net Objectives Inc.
  • 66. info@netobjectives.com    Thank You! www.netobjectives.com … and following is more to help you  plan your next steps 1 Copyright © 2009 Net Objectives. All Rights Reserved.   29 September 2010
  • 67. Resources Resources: www.netobjectives.com/resources  – Webinars/Training Videos (PowerPoint with audio) – Articles and whitepapers – Pre/post course support Supporting materials – Quizzes – Recommended reading paths – Blogs Annotated Bibliography After‐Course Support (students only) Additional Free On‐line Training User Groups – Business Driven Software Development http://www.netobjectives.com/bdsdug – Lean‐Agile User Group http://tech.groups.yahoo.com/group/leanagile  – Lean Programming User Group http://tech.groups.yahoo.com/group/leanprogramming  Join our e‐mail list to receive regular updates and information  about our resources and training of interest to you 2 Copyright © 2010 Net Objectives. All Rights Reserved.   29 September 2010
  • 68. A Short List of Books ‐ Lean Related Lean‐Agile Software Development: Achieving Enterprise Agility. Shalloway, Beaver,  Trott Managing the Design Factory: The Product Manager’s Toolkit. Reinertsen Implementing Lean Software Development: From Concept to Cash. Poppendieck &  Poppendieck Lean‐Thinking. Womack & Jones The Toyota Way. Liker Toyota Production System. Ohno Lean Software Development: An Agile Manager’s Toolkit. Poppendieck &  Poppendieck The Principles of Product Development Flow: Second Generation Lean Development. Reinertsen See www.netobjectives.com/resources/bibliography for a full bibliography 3 Copyright © 2010 Net Objectives. All Rights Reserved.   29 September 2010
  • 69. Lean Management and Other Relevant Books Peter Scholtes: The Leader’s Handbook: Making Things Happen,  Getting Things Done David Mann: Creating A Lean Culture: Tools to Sustain Lean  Conversions William Bridges: Managing Transitions Weick & Sutcliffe: Managing the Unexpected: Assuring High  Performance in an Age of Complexity Alexander: The Timeless Way of Building Shalloway & Trott: Lean‐Agile Pocket Guide for Scrum Teams See www.netobjectives.com/resources/bibliography for a full bibliography 4 Copyright © 2010 Net Objectives. All Rights Reserved.   29 September 2010
  • 70. A Short List of Books ‐ Technical  Essential Skills for the Agile Developer: A Guide to Better Programming and  Design. Shalloway & Bain Emergent Design: The Evolutionary Nature of Professional Software  Development. Bain Design Patterns Explained, A New Perspective on Object‐Oriented Design.  Shalloway & Trott Refactoring: Improving the Design of Existing Code. Fowler Working Effectively with Legacy Code. Feathers Agile Software Development: Principles, Patterns and Practices. Martin Head First Design Patterns. Freeman, Freeman, Bates, Sierra Prefactoring. Pugh Fit for Developing Software. Mugridge & Cunningham See www.netobjectives.com/resources/bibliography for a full bibliography 5 Copyright © 2010 Net Objectives. All Rights Reserved.   29 September 2010
  • 71. Upcoming Conferences International Conference on Lean Enterprise Software and Systems (LESS 2010) October 17‐20 Helsinki, Finland CEO Alan Shalloway will be giving a tutorial Agile software development changed the way that software development is perceived today.  The journey continues now in the new era where the software business meets software  practice in a novel way. We are proud to present at the first International Conference on Lean  Enterprise Software and Systems (LESS) in collaboration with the Lean Software and Systems  Consortium, http://www.leanssc.org/. Net Objectives Presentations – Tutorial: Scaling Agile With the Lessons of Lean Product Development Flow – Wed, Oct 20, 10:30 am  – 12:30 pm More information: www.netobjectives.com/conferences 6 Copyright © 2010 Net Objectives. All Rights Reserved.   29 September 2010
  • 72. Upcoming Conferences Øredev 2010 Conference November 8‐12 Malmö, Sweden Senior Consultant Cory Foy will be giving a tutorial and two sessions Agile Øredev is the Premier developer's conference in Europe, focused on the whole software  development process.  Øredev means both Quality and Quantity, by bringing the best  speakers and expert practitioners on a range of subjects, such as Java, .Net, Project  Management, Web development and Testing. Øredev reflects your universe, in motion. Net Objectives Presentations – Tutorial: Koans and Katas Oh My! – Tue, Nov 9, 8:50 am  – 12:10 pm – Tutorial: Delivering What's Right – Thu, Nov 11, 10:15 am  – 11:05 am – Tutorial: Fostering Software Craftsmanship – Fri, Nov 12, 1:10 pm  – 2:00 pm More information: www.netobjectives.com/conferences 7 Copyright © 2010 Net Objectives. All Rights Reserved.   29 September 2010
  • 73. Upcoming Conferences Agile Development Practices | East Conference & Expo November 14‐19 Orlando, FL Net Objectives is sponsoring the conference, as well as giving onsite courses  and concurrent sessions, and having a booth at the Expo Discover Agile Development Practices and take back the latest in agile methods, technologies,  tools, and leadership principles from thought leaders who deliver inspiring keynote  presentations, in‐depth tutorials, and a wide range of conference classes. Join industry  experts and peers in the agile community for a week jam‐packed with learning sessions that  will help you make a powerful impact in your job role and for your organization.  Net Objectives Presentations – Session: Paying Down Technical Debt – Wed, Nov 17, 12:45 pm – Session: Applying Lean Software Development Principles Throughout the  Organization – Wed, Nov 17, 2:45 pm – Session: Serious Games: Product Planning and Prioritization Using Innovation  Games®– Thu, Nov 18, 12:45 pm More information: www.netobjectives.com/conferences 8 Copyright © 2010 Net Objectives. All Rights Reserved.   29 September 2010
  • 74. Upcoming Public Courses Charlotte, NC – Lean‐Agile Project Management Certification – Oct 25‐27 Orlando, FL at Agile Development Practices | East 2010 – Practical Test‐Driven Development – Nov 14 ‐ 16  – Scrum Master Certification – Nov 14 ‐ 16  Philadelphia, PA – Lean‐Agile Project Management Certification – Dec 7‐9 Conference Courses: 8:30am – 5:00pm More information: www.netobjectives.com/courses/ Other Courses:          9:00am – 5:00pm 9 Copyright © 2010 Net Objectives. All Rights Reserved.   29 September 2010
  • 75. New Podcast Series Podcast Series for Lean Agile Straight Talk – First Podcast in the series available – September 29 – www.netobjectives.com/blogs/new‐series Alan Shalloway and Jim Trott talk about what is going on in the world of  Lean and Agile software development.   They introduce Net Objectives’ 2 newest books – Lean‐Agile Pocket Guide for Scrum Teams – Lean‐Agile Software Development: Achieving Enterprise Agility – Later podcasts in the series Focus on the Lean‐Agile Pocket Guide for Scrum Teams A talk through each of the chapters in the Lean‐Agile Software  Development book. – Each of these chapters has good, core concepts that we want you to know  and this approach gives us a game plan for covering all of them.  More blogs/podcasts: www.netobjectives.com/blogs 10 Copyright © 2010 Net Objectives. All Rights Reserved.   29 September 2010
  • 76. Net Objectives Services Training in Sustainable Product Development Certification Programs by Net Objectives Net Objectives offers the most comprehensive  Net Objectives offers certification programs that  Lean‐Agile training in the world. Our offerings  provides a road‐map of knowledge as well as  include Lean, Agile Analysis, Design Patterns, Test‐ resources to get there. Driven Development, and Lean‐Agile Testing. • Lean‐Agile Project Management Certification Our approach is a blend of principles and practices  • Advanced Lean‐Agile Project Management for  to provide a complete team and/or enterprise wide  Scrum Masters training solution. • Lean Product Champion Certification Net Objectives is not affiliated with the Scrum Alliance Assessment Services Lean‐Agile Coaching An effective way to embark on an enterprise level  While training provides foundational knowledge  transition to Lean‐Agile methods is to start with an  and is a great jump start, coaching is another  assessment of where you are, where you want to go  effective way to increase the abilities of teams.  and options on how to get there that are right for  Our coaches work with your teams to provide  you and your budget.  guidance in both the direction your teams need to  go and in how to get there.  Coaching provides the knowledge transfer while  working on your own problem domain.  11 Copyright © 2010 Net Objectives. All Rights Reserved.   29 September 2010
  • 77. Best Practices Curriculum Lean Agile  Exec  Overview for  Senior Management Mgmt Leaders Scrum Master  IT Mgmt Agility for  IT Management Lean Software  Practitioner Managers  (if not taking  Development  Implementing  For  Lean‐Agile for  Management Business  Your Team) Lean‐Agile  Business Management Mgmt Enterprise Release  Planning Story Writing  Analyst OR & Acceptance  Analyst Tests Lean‐Agile Bootcamp Lean‐Agile Software Development Advanced  Lean Product  Lean‐Agile  Lean‐Agile  Lean‐ Lean  Champion  Project  Project  Lean Software  Agile  Online  Process Certification Project  Manager  Management  Development Process Implementing  By Net Objectives Certification Training Lean‐Agile   Manager for Scrum  By Net Objectives for Your  Masters Team Lean‐Agile  Tester Testing  Effective  Sustainable  Tester Emergent Design Practices Story  Implementing  Object‐ Test‐Driven  Writing &  Story  Oriented  Development Technical  Acceptance  Acceptance  Analysis  Tests Tests Design  Training:  and Design Design  Patterns  Developer Developer C++, C#,  (if needed) Patterns for  Explained Java Agile  Database Agility TDD Database Boot Camp Advanced Software Design Developers 12 Copyright © 2009 Net Objectives. All Rights Reserved.   29 September 2010
  • 78. Net Objectives Courses Business ‐ Management Technical Agility – Lean Online Training – Design Patterns for Agile Developers – Lean Software Development Overview for  – Sustainable Test‐Driven Development Executives and Management – Emergent Design – Lean‐Agile Software Development for Executives  – Acceptance Test‐Driven Development and Directors – Implementing Story Acceptance Tests – Lean‐Agile Software Development for Managers and  – Database Agility Online Training Leads – Lean‐Agile Enterprise Release Planning – Essential Skills for the Agile Developer – Lean‐Agile Project Management Certification by Net  – TDD Database Boot Camp Objectives – Advanced Software Design Team Agility – Design Patterns Explained – Implementing Lean‐Agile for Your Team: Using  – Lean‐Agile Testing Practices Kanban, Scrumban and Scrum Effectively – Effective Object‐Oriented Analysis and Design – Kanban for Lean‐Agile Teams – Implementing Scrum for Your Team – Lean‐Agile Project Management – The Kanban/Scrumban/Scrum Team Bootcamp – Acceptance Test‐Driven Development – Lean‐Agile Enterprise Release Planning A Top 5 Course – Lean‐Agile Project Management Certification by Net  A  New Course Objectives – Advanced Lean‐Agile Project Management for  Scrum Masters – Lean Product champion Certification by Net  Objectives More information: www.netobjectives.com/training 13 Copyright © 2010 Net Objectives. All Rights Reserved.   29 September 2010
  • 79. Tools We Like Agile Project Management Tools 14 Copyright © 2010 Net Objectives. All Rights Reserved.   29 September 2010