ScrumMaster vs. Project Manager
V. Lee Henson CST ~ @AgileDad


                                1
✤   Founded in 2007 - Salt Lake City, UT

✤   Specialize in Public & Private Certification Workshops
    & Courses

✤   Deep understanding of Agile & Traditional Project
    Management, (PMP), RUP, Lean, Kanban, Scrum, (CST),
    XP, & PMI-ACP

✤   Proven Applied Agile Principles in Software, Hardware,
    Financial, Insurance, Construction, Medical,
    Marketing, Legal, Entertainment, Research, Military,
    Government, Retail, Education, Law Enforcement, and
    many more...



                                                             2
V. Lee Henson CST

✤   Certified Scrum Trainer

✤   Project Management Professional

✤   PMI- Agile Certified Practitioner

✤   Certified Lean Agile Professional

✤   Motivational Speaker & Executive
    Coach

✤   Author of The Definitive Agile
    Checklist

✤   Inventor of Rapid Release Planning

✤   Information Technology / Psychology

Copyright 2012 AgileDad LLC Licensed for Classroom Use Only.   3
The Agile Manifesto
     We are uncovering better ways of developing software
             by doing it and helping others do it.

           Through this work we have come to value:

      Individuals & Interactions over processes & tools

            Working software over comprehensive
                      documentation

      Customer collaboration over contract negotiation

         Responding to change over following a plan

     That is , while there is value in the items on the right,

               we value the items on the left more.

            Copyright 2012 AgileDad LLC Licensed for Classroom Use Only.   4
Agile vs. Plan Driven




        Copyright 2012 AgileDad LLC Licensed for Classroom Use Only.   5
Scrum vs. Waterfall




        Copyright 2012 AgileDad LLC Licensed for Classroom Use Only.   6
Let Us Compare...




       Copyright 2012 AgileDad LLC Licensed for Classroom Use Only.   7
Roles - An Overview
✤   Most Agile methods profess the
    use of 3-5 different roles.

✤   Many teams adopting Agile
    struggle to determine where
    their traditional roles fit into an
    Agile landscape

✤   Every role fits into 3 Simple
    classes:

    ✤   Customer

    ✤   Facilitator

    ✤   Implementor
                      Copyright 2012 AgileDad LLC Licensed for Classroom Use Only.   8
Traditional Project Managers:
                                    ✤   A project manager is a professional
                                        in the field of project management

                                    ✤   Project managers can have the
                                        responsibility of the planning,
                                        execution, & closing of any project

                                    ✤   In traditional project management
                                        a heavyweight, predictive
                                        methodology such as the waterfall
                                        model is most often employed

                                    ✤   Software Project managers are also
                                        expected to be familiar with the
                                        Software Development Life Cycle

        Copyright 2012 AgileDad LLC Licensed for Classroom Use Only.          9
How Does It All Divi Up?
            PM Responsibilities                                                SMaster POwner
Engage with Stakeholders                                                              X   X
Develop Project Plan                                                                  O   O
Direct Project Resources                                                              O   O
Monitor & Manage Project Schedule & Budget                                            O   X
Monitor & Manage Project Risk                                                         X   X
Deals With Operational Issues & Impediments                                           X   O
Ensures the Project Meets Requirements & Objectives                                   O   X
Manages Project Team Members                                                          O   O
Looks After the Interests of the Team                                                 X   O
Communicate Project Status To Sponsor & Stakeholder                                   O   X
                       Copyright 2012 AgileDad LLC Licensed for Classroom Use Only.           10
ScrumMaster:
                              ✤   Should be a full time role

                              ✤   Could be a delivery team member in a pinch

                              ✤   Used to be called project manager but:

                                   ✤   No longer has delivery responsibility

                                   ✤   Does not commit to dates, budgets, profits, etc.

                              ✤   Is primarily a facilitator and servant leader.

                              ✤   You will have to deal with:

                                   ✤   The era of opacity

                                   ✤   The tyranny of command & control

                              ✤   Must be able to multi-task - run multiple sprints at the
                                  same time.

                              ✤   Should use spare time to assist the Product Owner in
                                  maintaining and grooming the product backlog.


       Copyright 2012 AgileDad LLC Licensed for Classroom Use Only.                          11
ScrumMaster & The Team:
                                          ✤   Acts as a sheepdog for the team

                                               ✤   Improves the lives of the delivery team
                                                   by facilitating creativity and
                                                   empowerment

                                               ✤   Improves the productivity of the delivery
                                                   team in any way possible.

                                               ✤   Improves the engineering practices and
                                                   tools so that each increment of
                                                   functionality is potentially shippable.

                                          ✤   Removes barriers so that the customer can
                                              more directly drive delivery.

                                          ✤   Safeguards the Scrum Process

                                          ✤   Fosters Team communication &
                                              collaboration

                                          ✤   Serves, Leads, & Facilitates

       Copyright 2012 AgileDad LLC Licensed for Classroom Use Only.                       12
ScrumMaster & The
Organization
                                          ✤   Teaches Scrum as a simple
                                              framework with few rules

                                          ✤   Organizations should be
                                              equipped with a resolute,
                                              patient, ScrumMaster.

                                          ✤   Sometimes People cannot stand
                                              what Scrum exposes.

                                          ✤   A dead ScrumMaster is a
                                              useless ScrumMaster

                                          ✤   ScrumMaster’s are the key to
                                              the degree of success in
                                              transforming organizations.
       Copyright 2012 AgileDad LLC Licensed for Classroom Use Only.          13
ScrumMaster Skills:
✤   Leading

    ✤   Learn to lead! It doesn’t always come
        naturally

✤   Facilitating

    ✤   Enhance communications - always and
        everywhere

        ✤   Meetings, one-on-one, in the team,
            between teams

    ✤   Get a facilitation toolkit

    ✤   Read, practice, improve

✤   Work towards self organizing teams

✤   Ask meaningful questions

✤   Listen twice as much as you speak


                             Copyright 2012 AgileDad LLC Licensed for Classroom Use Only.   14
A Short Quiz..
✤   Think about what you have learned about
    the ScrumMaster Role. Answer the
    following questions :

✤   1) In your opinion, do you feel that the
    ScrumMaster should also be responsible
    for prioritizing requirements? Why or
    Why not?

✤   2) Do you feel that a technical lead or
    manager would experience any difficulty
    with being a ScrumMaster? Why or Why
    not?

✤   3) What do you envision are the
    differences in responsibilities between a
    ScrumMaster, development manager, and
    product/solutions manager?
                      Copyright 2012 AgileDad LLC Licensed for Classroom Use Only.   15
Making The Transition - 3?’s
✤   1) Have you studied the
    differences between Agile & Non-
    Agile projects and understand
    them well enough that you feel
    confident in taking the leap?

✤   2) Are you willing to act as a
    leader without authority and do all
    that is needed to assist the team
    in being successful?

✤   3) Do you have the required set of
    skills to perform well in the role of
    a ScrumMaster? If not, what should
    my PM role transition into?
                   Copyright 2012 AgileDad LLC Licensed for Classroom Use Only.   16
5 FACTS About YOUR Agile Adoption

  1) Management has invested a lot of money and time into
  helping your organization adopt and or embrace Agile
  Methods.

  2) I have been out to train and certify ScrumMasters &
  Product Owners on both the business & technical sides of
  the organization.

  3) Many groups who were trained early on are already
  beginning to see GREATLY improved results as a result of
  the implementation of this process.

  4) Consistency in training & coaching is the key to
  successfully rolling this into your group within the
  organization.

  5) People are willing to invest in your future through Agile
  Training.   Copyright 2012 AgileDad LLC Licensed for Classroom Use Only.   17
So What Happens To Project Managers?




                          Do I need to worry?

          Copyright 2012 AgileDad LLC Licensed for Classroom Use Only.   18
Open Question & Answer Period




                     No Need To Worry!

         Copyright 2012 AgileDad LLC Licensed for Classroom Use Only.   19
Thank You!
 Lee@AgileDad.Com- Twitter @AgileDad - LinkedIn leehenson@gmail.com


               Copyright 2012 AgileDad LLC Licensed for Classroom Use Only.   20

ScrumMaster vs Project Manager

  • 1.
    ScrumMaster vs. ProjectManager V. Lee Henson CST ~ @AgileDad 1
  • 2.
    Founded in 2007 - Salt Lake City, UT ✤ Specialize in Public & Private Certification Workshops & Courses ✤ Deep understanding of Agile & Traditional Project Management, (PMP), RUP, Lean, Kanban, Scrum, (CST), XP, & PMI-ACP ✤ Proven Applied Agile Principles in Software, Hardware, Financial, Insurance, Construction, Medical, Marketing, Legal, Entertainment, Research, Military, Government, Retail, Education, Law Enforcement, and many more... 2
  • 3.
    V. Lee HensonCST ✤ Certified Scrum Trainer ✤ Project Management Professional ✤ PMI- Agile Certified Practitioner ✤ Certified Lean Agile Professional ✤ Motivational Speaker & Executive Coach ✤ Author of The Definitive Agile Checklist ✤ Inventor of Rapid Release Planning ✤ Information Technology / Psychology Copyright 2012 AgileDad LLC Licensed for Classroom Use Only. 3
  • 4.
    The Agile Manifesto We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals & Interactions over processes & tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is , while there is value in the items on the right, we value the items on the left more. Copyright 2012 AgileDad LLC Licensed for Classroom Use Only. 4
  • 5.
    Agile vs. PlanDriven Copyright 2012 AgileDad LLC Licensed for Classroom Use Only. 5
  • 6.
    Scrum vs. Waterfall Copyright 2012 AgileDad LLC Licensed for Classroom Use Only. 6
  • 7.
    Let Us Compare... Copyright 2012 AgileDad LLC Licensed for Classroom Use Only. 7
  • 8.
    Roles - AnOverview ✤ Most Agile methods profess the use of 3-5 different roles. ✤ Many teams adopting Agile struggle to determine where their traditional roles fit into an Agile landscape ✤ Every role fits into 3 Simple classes: ✤ Customer ✤ Facilitator ✤ Implementor Copyright 2012 AgileDad LLC Licensed for Classroom Use Only. 8
  • 9.
    Traditional Project Managers: ✤ A project manager is a professional in the field of project management ✤ Project managers can have the responsibility of the planning, execution, & closing of any project ✤ In traditional project management a heavyweight, predictive methodology such as the waterfall model is most often employed ✤ Software Project managers are also expected to be familiar with the Software Development Life Cycle Copyright 2012 AgileDad LLC Licensed for Classroom Use Only. 9
  • 10.
    How Does ItAll Divi Up? PM Responsibilities SMaster POwner Engage with Stakeholders X X Develop Project Plan O O Direct Project Resources O O Monitor & Manage Project Schedule & Budget O X Monitor & Manage Project Risk X X Deals With Operational Issues & Impediments X O Ensures the Project Meets Requirements & Objectives O X Manages Project Team Members O O Looks After the Interests of the Team X O Communicate Project Status To Sponsor & Stakeholder O X Copyright 2012 AgileDad LLC Licensed for Classroom Use Only. 10
  • 11.
    ScrumMaster: ✤ Should be a full time role ✤ Could be a delivery team member in a pinch ✤ Used to be called project manager but: ✤ No longer has delivery responsibility ✤ Does not commit to dates, budgets, profits, etc. ✤ Is primarily a facilitator and servant leader. ✤ You will have to deal with: ✤ The era of opacity ✤ The tyranny of command & control ✤ Must be able to multi-task - run multiple sprints at the same time. ✤ Should use spare time to assist the Product Owner in maintaining and grooming the product backlog. Copyright 2012 AgileDad LLC Licensed for Classroom Use Only. 11
  • 12.
    ScrumMaster & TheTeam: ✤ Acts as a sheepdog for the team ✤ Improves the lives of the delivery team by facilitating creativity and empowerment ✤ Improves the productivity of the delivery team in any way possible. ✤ Improves the engineering practices and tools so that each increment of functionality is potentially shippable. ✤ Removes barriers so that the customer can more directly drive delivery. ✤ Safeguards the Scrum Process ✤ Fosters Team communication & collaboration ✤ Serves, Leads, & Facilitates Copyright 2012 AgileDad LLC Licensed for Classroom Use Only. 12
  • 13.
    ScrumMaster & The Organization ✤ Teaches Scrum as a simple framework with few rules ✤ Organizations should be equipped with a resolute, patient, ScrumMaster. ✤ Sometimes People cannot stand what Scrum exposes. ✤ A dead ScrumMaster is a useless ScrumMaster ✤ ScrumMaster’s are the key to the degree of success in transforming organizations. Copyright 2012 AgileDad LLC Licensed for Classroom Use Only. 13
  • 14.
    ScrumMaster Skills: ✤ Leading ✤ Learn to lead! It doesn’t always come naturally ✤ Facilitating ✤ Enhance communications - always and everywhere ✤ Meetings, one-on-one, in the team, between teams ✤ Get a facilitation toolkit ✤ Read, practice, improve ✤ Work towards self organizing teams ✤ Ask meaningful questions ✤ Listen twice as much as you speak Copyright 2012 AgileDad LLC Licensed for Classroom Use Only. 14
  • 15.
    A Short Quiz.. ✤ Think about what you have learned about the ScrumMaster Role. Answer the following questions : ✤ 1) In your opinion, do you feel that the ScrumMaster should also be responsible for prioritizing requirements? Why or Why not? ✤ 2) Do you feel that a technical lead or manager would experience any difficulty with being a ScrumMaster? Why or Why not? ✤ 3) What do you envision are the differences in responsibilities between a ScrumMaster, development manager, and product/solutions manager? Copyright 2012 AgileDad LLC Licensed for Classroom Use Only. 15
  • 16.
    Making The Transition- 3?’s ✤ 1) Have you studied the differences between Agile & Non- Agile projects and understand them well enough that you feel confident in taking the leap? ✤ 2) Are you willing to act as a leader without authority and do all that is needed to assist the team in being successful? ✤ 3) Do you have the required set of skills to perform well in the role of a ScrumMaster? If not, what should my PM role transition into? Copyright 2012 AgileDad LLC Licensed for Classroom Use Only. 16
  • 17.
    5 FACTS AboutYOUR Agile Adoption 1) Management has invested a lot of money and time into helping your organization adopt and or embrace Agile Methods. 2) I have been out to train and certify ScrumMasters & Product Owners on both the business & technical sides of the organization. 3) Many groups who were trained early on are already beginning to see GREATLY improved results as a result of the implementation of this process. 4) Consistency in training & coaching is the key to successfully rolling this into your group within the organization. 5) People are willing to invest in your future through Agile Training. Copyright 2012 AgileDad LLC Licensed for Classroom Use Only. 17
  • 18.
    So What HappensTo Project Managers? Do I need to worry? Copyright 2012 AgileDad LLC Licensed for Classroom Use Only. 18
  • 19.
    Open Question &Answer Period No Need To Worry! Copyright 2012 AgileDad LLC Licensed for Classroom Use Only. 19
  • 20.
    Thank You! Lee@AgileDad.Com-Twitter @AgileDad - LinkedIn leehenson@gmail.com Copyright 2012 AgileDad LLC Licensed for Classroom Use Only. 20

Editor's Notes

  • #2 \n
  • #3 \n
  • #4 \n
  • #5 \n
  • #6 \n
  • #7 \n
  • #8 \n
  • #9 \n
  • #10 \n
  • #11 \n
  • #12 \n
  • #13 \n
  • #14 \n
  • #15 \n
  • #16 \n
  • #17 \n
  • #18 On occasion the truth may be too much to handle. The team needs to deliver the truth first and always in order to maintain high visibility and to become trusted amongst management. \nWork should never be assigned or delegated. The team may have a subject matter expert on the particular story at hand, but cross pollination is encouraged. Teams should take advantage of every opportunity to learn and educate each other. Over time the team’s velocity will increase as a result. \nThe worst decision that can be made is no decision at all. Make and embrace decisions. Your leaders will thank you for it. \nTeams really should be having items signed off on throughout the iteration. When a great product owner or manager makes themselves available to you for questions etc., make certain you set aside time to regularly demo what you have internally to prepare for the external release. \nNo team can be successful without a champion to remove the impediments and assist the team in running interference. This leader should be both a champion of the cause and a great facilitator. \nRegular short meetings have proven time and time again that they are far more effective than the once weekly status updates. Keeping on top of the information daily provides for crisper communication and increased visibility.\nAll committed parties should attend every team meeting. The meetings should be short, time boxed, and to the point. (This includes the retrospective)\nThe team should set rules, define done, and make & take commitments seriously. \n
  • #19 \n
  • #20 \n
  • #21 \n