FAQ on Career Path of Scrum Product Owners for Management

complex-product-backlog-product-ownerAs Agile and Scrum grows deeper into the market it is valuable for Management to communicate the rewarding and desirable career path that a Scrum Product Owner can have… even beyond just leading single Scrum Product Teams.

Before you go through this, it may be very helpful to first understand the following:

Eventbrite - Certified Scrum Product Owner Course (CSPO) - Get Certified in Atlanta, GA

Career Paths for Scrum Product Owners

Q. Are there multiple types of PO?  If so how are they different and how do they work together?

A. See earlier questions under “Product Owner Role & Organization” that describe how Release Product Owner and team Product Owner roles work as a team with a “single voice” on priority and acceptance decisions.

Q. What are possible steps in Product Owner career path?

A. A PO may start out working as part of a PO team as team Product Owner, or they may begin as PO for a single team product.

  1. Product Owner I – Trained Entry Level Product Owner
  2. Product Owner II – Experienced w/ Continuing Ed (From Score Card requires 12 months)
  3. Senior Product Owner – Release PO responsibilities for a major product; typically leading a PO team and/or working with multiple Scrum Teams. Should be both trained and experienced and meet continuing education requirements. 3-5 years combined program management, Agile/Scrum, and Product Owner experience.
  4. Principal Product Owner – TBD.  5-8 years combined project, program, Agile/Scrum, and Product Owner experience.

Q. What is difference in job title for RPO vs team PO roles?

A.  See Career path steps above

Q. What is the next step in the Career Path for a product owner? Is it to Product Management?

Q. What are some possible stepping off points into other jobs or roles?

A. Product Owners could potentially transition either to or from Development Management or Product Management. There are multiple paths to and from a Product Owner position. It could also be back to a prior contributor job or another professional position, or leadership role.

Q. What qualifies as continuing education and who needs to approve it?

A. Example Continuing Education Activities include:

  • Internal, onsite, or public Agile training classes
  • Agile topic meetings at local professional organizations
  • Agile workshops and seminars
  • National or International Agile software development conferences such as Agile 20xx

Management has budget approval of the individual’s costs for attending continuing education. The company’s Director, Agile Methods publishes guidelines for qualified continuing education activities and may review and revise these from time to time with input from Scrum Masters and management.

Q. What professional certifications are applicable to a Product Owner?

A. The Scrum Alliance offers one level of certification:

Q. Should the company support and pay for people to be certified?

A. Not necessarily, the company will pay for Product Owners to maintain membership and certification for approved professional organizations, but not necessarily to obtain CSPO certification.

Q. Is Certified Scrum Product Owner (CSPO) required to become and serve as a Product Owner?

A. No, Certification is not required for Product Owners but CSPO or equivalent training is.  See “What training is required…” question below under Inputs section.

Q. How is the pay scale determined for a Product Owner?

A. HR should determine market value for common industry jobs that are similar to product owner responsibilities

Q. What recognition and reward do I receive as a Product Owner?

A. Compensation and recognition for Product Owner position should reflect the level of responsibility and market value.

Inputs

Q. Who is eligible to become a Product Owner?

Q. Who selects / approves Product Owner candidates?

A. Development Executives will ultimately determine who is eligible based on their confidence in an individual’s leadership abilities for Product Owners. Key stakeholders such as Product Managers should be involved in selection.

Q. Where would candidate Product Owners come from?

A. May come from BA’s, Developers, Development Manager, Product Manager, Project Managers etc. where Some have more industry experience and some have more technical experience.

Q. How does someone start out? What training or accreditation is a prerequisite?

Q. What training is required to become a Product Owner?

A. CSPO training or equivalent is required.  This may be satisfied by The company on-site courses taught following a CSPO based material, or by completing Certified ScrumMaster training plus one day of internal The company Product Owner training.

Q. Why should managers encourage their most qualified people to consider the Product Owner role?

A. For people who are seeking a challenging leadership growth opportunity this is a good opportunity for development. Product development quality and effectiveness is highly dependent on product owners to drive requirements through completion and is therefore a critical role for succeeding with Scrum.

Exits

Q. What are my options when I no longer want to be a PO?

A. See Pathways above, “There are multiple paths to and from a Product Owner position. It could also be back to a prior contributor job or another professional position, or leadership role.”

Good questions to pursue through training, self directed learning, and continuing education:

Q. How should product owners get input from stakeholders?

Q. How do product owners work across products to see that functionality syncs up & integrates properly?

Q. How do you blend customer commitments with feature work?

Q. How do management stakeholders get input into the backlog?

Q. How do PO’s work with UX/UI?

Q. How does the Product Owner engage with the UI/UX Teams on Customer Needs & Requirements?

Q. How does a PO develop acceptance criteria?

Q. How do Product Owners work across products together, especially if work done in different sprints for different teams?

Q. Are Product Owners focused on the current release, future releases, gathering customer feedback, etc?  Is that multi-tasking successful?

Q. Are there tasks Product Owners do today that would be better suited for a separate role such as Business Analyst or usability lead?

Q. How do you blend customer commitments with feature work? (Item we already had…suggestion was to include ‘and technical debt’.

Q. How does product owner deal with individual performance as an impediment?

Q. How does Scrum team give input to PO?

Q. What should a scrum team do if their PO is not fulfilling their part of the deal?

Agile Testing Days 2013 – Pure Joy @agiletd

2013.10.29-agile-testing-days-2013-2 2013.10.29-agile-testing-days-2013

It is 110% complete joy that I’m filled with whenever I come to Berlin to speak at this conference. I spoke in Berlin at Agile Dev Practices earlier this year and it was an honor to come back.

What is so unique about this conference is that in many regards it’s like returning to a family. Great people. Wonderful conversation. Unique venue. Awesome talks.

I’m already looking forward to seeing many of these people again… and we’re not even done yet!

What agile brings is a great culture of people. A community. If, for no other reason, the value of Agile is it’s vast community of caring people. What else matters?

FAQ on Most Common Product Owner Questions for Management

complex-product-backlog-product-ownerAs Agile and Scrum grows deeper into the market it is valuable for Management to communicate the rewarding and desirable career path that a Scrum Product Owner can have… even beyond just leading single Scrum Product Teams.

Before you go through this, it may be very helpful to first understand the following:

Eventbrite - Certified Scrum Product Owner Course (CSPO) - Get Certified in Atlanta, GA

Frequently Asked Questions on the Product Owner Role & Organization

Q. What is the Product Owner Role?

A. Product Owner is one of the key roles in Scrum that acts as the “single voice” for priority and acceptance of what to work on for a Scrum Development Team

Q. What is a Product Owner responsible for?

  1. Creates and Maintains the Product Backlog showing visible progress towards forecast results
  2. Prioritizes and sequences the Backlog according to business value as expressed by roadmap and stakeholder needs
  3. Prepares for each sprint and release planning session by working with team to elaborate Feature Stories into Minimal Marketable Features that deliver increments of value and User Stories that are appropriately sized for each sprint.
  4. Conveys the Vision and Goals at the beginning of every Release and Sprint.
  5. Represents customer and stakeholder interests. Engages and solicits their feedback to validate priorities and compromises.
  6. Participates in daily standup Scrums, Sprint Planning Meetings, Sprint Reviews, and Retrospectives.
  7. Accepts User Stories during the sprint to confirm implementation meets intent of acceptance criteria.
  8. Re-negotiates Sprint priorities and commitment when team communicates new discoveries that impact size or value of work.
  9. Communicates status to stakeholders including use of Visible Product Backlog for forecasting release content and dates.

Q. What is definition of Release PO versus Feature PO?

A. When a Scrum Product Team includes more than 2 Scrum Teams we have found that it’s more than one Product Owner can handle. In this case we suggest adding a Release Product Owner as a Product Owner Team lead.  The PO team covers all the responsibilities and activities of a Product Owner divided into RPO and team PO roles. 

Release Product Owner leads the PO team and is first and foremost responsible that the PO team presents a Single Voice

  • Clear statement of vision, direction, release purpose and goals
  • Managing overall Product Backlog and publishing the Product Backlog
  • Show alignment w/ product roadmap
  • Getting stakeholder buy-in on Product Backlog
  • Prioritization of Product Backlog
  • Prepare appropriate Product Backlog to drive release planning
  • Ongoing release plan forecasting
  • Deployment & release readiness checklist
  • Market launch split out to PM

Team Product Owner (or just PO) is a member of the Scrum Team responsible for working with the team from sprint to sprint and grooming the breakdown of Features into sprint sized User Stories so that they are prepared for Sprint Planning

  • Prioritize user stories to drive Sprint Planning
  • Acceptance criteria of stories in sprint
  • Day to day available to team for conversations about stories in sprint
  • Accepting stories in sprint

Q. When do we need this distinction versus having a single PO for smaller product teams?

A. Any time we have more than one PO assigned to a Scrum Product Team.

In some cases the RPO may also act as team PO for one of the Scrum Teams with assistance from additional team PO’s on other Scrum Teams.

Note that we recognize there is overhead incurred by introducing a layer with a Release PO as well as the team POs but have found it is worth it to avoid spreading a PO too thin across more than two Scrum Teams.

Q. If a product has a single PO are they also the RPO?

A. In as sense, Yes. When there is a single PO for a product they span the responsibilities of both RPO and team PO.

Q. Is the product owner a member of the Scrum Team?

A. Yes, Product Owners are considered to be a member of the Scrum Team.  See the definitions for “Scrum Team” and “Scrum Development Team” above.

Each Scrum Team should have a single Product Owner responsible for prioritizing work items for the Sprint backlog along with the corresponding acceptance criteria.  A Product Owner may be a member of up to 2 Scrum Teams. Conversely, each Scrum Team will have a single Product Owner as their input for what work to work on.

Q. Who is responsible for staffing the Product Owner role?

A. Product development quality and effectiveness is highly dependent on product owners to drive requirements through completion. Therefore, development management is responsible to staff a sufficient number of qualified Product Owners to satisfy the needs of each Scrum Team.

Q. Who should Product Owners report to?

A. Leadership over product lines and those who can help influence changes in products depending on market/client needs.

Q. What department should Product Owners report to?

A. Often this is business, and can look like the Product Management Group, sales, or even marketing.

Q. What reporting structure should Product Owners follow?

A. Release level Product Owners should report at an equivalent level to their development management peers. If the development manager(s) for people on the team(s) the PO works with report at Director or VP level, then the PO should report at the same level. Regardless of reporting structure, development management must have the authority to address any impediments. The preferred approach is for people acting as Release Product Owners to report into the Product Development organizational structure.

Q. Who should team Product Owners report to?

A. Team level Product Owners should report into the same department as their RPO.

Q. PO Role vs. full time position?

A. Full time role. It’s one of the most important and can easily take up 100% of their time to do it right.

Q. Is Product Owner a job title or a role that someone with an existing job title fills?

A. To be a release level Product Owner is a full time job that includes coordinating with stakeholders and managing dependencies in addition to working closely with the development team.

Q. Is team PO a full time job?

A. Yes, a team PO is also a full time job dedicated to success of their Scrum Team(s)

Q. How much time should a person expect to spend on Product Owner activities?

A. Full time job for both RPO and team PO’s.

Q. How many Scrum teams would we expect a full time Product Owner to handle?

A. A Product Owner should have no more than two Scrum Teams.

Q. Can one person be a PO for multiple products?

A. Not recommended

Q. Handling “Part Time Product Owners”?

A. Not recommended

Q. Handling “Distant Product Owners”?

A. PO’s assigned to teams should be co-located or at least be in a compatible time zone with their Scrum Team

Q. What is value of technical product owner versus a business focused product owner (and vice-versa)?

A. While in practice we recognize that people come to the PO role with different strengths, we don’t distinguish in the PO role based on their background; these are not recognized types of PO’s.

Q. If you are Product Owner what title would you have?

A.  Product Owner, (we’ll cover career paths next)

Q. What is common industry job title for product owner responsibilities?

A. Some typical job titles used in software development include: Program Manager, Technical Program Manager, Technical Product Manager, Product Analyst, or Product Owner

Q. What are the “lines” between the different roles, where does one stop and the next role start – PM/PO, PO/Business Analyst

A. Product Managers are responsible for a product roadmap that is detailed and aligned to corporate strategy. Product Owner is responsible for ensuring their product backlog is aligned to the roadmap.

Q. How much customer interaction is expected from a Product Owner? How is their interaction different from Product Managers?

A. Product Owners communicate with customers in a listening role to share backlog and results for checking understanding, and in order to solicit feedback. Sales and account management calls should be minimized, and are not considered a primary responsibility for the Product Owner role.

Product Managers communicates externally and across the company. Product Managers are responsible for the market message and communicating commitments and promises to customers.

Q. Where is management support to product owner role & backing their decisions?

A. In addition to coaching and budgeting for professional development and skill building activities management should:

  • Provide feedback on product backlog content, priorities, and dates with clear purpose
  • Support acceptance decisions the PO makes during each sprint
  • Management will route all work for teams through product owner to support single voice for work priorities
  • Manage consistent and qualified staffing for teams from sprint to sprint with minimal changes throughout a release
  • Key Stakeholders will provide clear direction on prioritizing to achieve corporate strategy and product management objectives shown in product roadmaps
  • Development Executives will support the PO in helping Key Stakeholders to understand and accept the necessity for making tradeoff decisions on dates and/or feature content consistent with actual team capacity

Q. Who are PO’s are accountable to?

A. Product Owners are accountable to the Key Stakeholders who make the financial commitments:

  • Business Unit President
  • CTO
  • Product Manager

Product Owners negotiate agreement to backlog priorities with these Key Stakeholders and keep them informed of any significant impacts or deviations from forecasts.

Q. What defines success for a for a product owner?

A. Profitable products and satisfied customers.

  • Product releases deliver great value as perceived by customers and stakeholders
  • Balances feature delivery with sustainable software development
  • Stakeholder and team members understand rationale for prioritization and forecasting is visible and transparent
  • There are no surprises on progress, feature content and dates, or priority changes made along the way
  • Scrum Team members feel meaningful accomplishment from delivering “winning” features
  • Continuously learning and improving use of agile principles and practices
  • Deliver a product that is aligned with the roadmap

Product Owner Competencies

Q. What are the qualifications to become a Product Owner?

Q. What levels of experience would they have?

Q. What ‘behavioral skills’ would they demonstrate?

A. The following Starting Competencies are needed to become a Product Owner:

  • Relevant background
    • Industry and/or application domain knowledge
    • Or experience in some parallel or related business field
    • Experienced in customer interactions
    • Excellent listening, verbal and written communication skills
    • Negotiation skills with ability to compromise and balance tradeoffs among multiple interests
    • Proven leadership and decision making
    • Professional presentation skills
    • Familiar with Agile and Scrum principles and practices

Q. What skills and experience do I gain as a Product Owner?

Q. What are the skills we need in a Product Owner?  Must those skills be in one person?

Q. What competencies should a Product Owner demonstrate?

A. The following Performing Competencies are needed to do the Product Owner job well:

  • Subject matter expertise and sufficient market knowledge to understand customer wants and needs
  • Manage product backlogs with priority decisions that mitigate risk and maximize value while showing steady progress towards forecast results
    • Manages backlog content consistent with priorities agreed to with key stakeholders
    • Provides a visible forecast and notifies stakeholders of any significant changes in effort or risk
    • Create Feature and User Stories that represent “vertical slices” of value
    • Collaborates effectively with Scrum Master and Scrum Development Team
    • Engage both team and stakeholders to collaborate in release planning
    • Inspires commitment by communicating clear vision, direction, purpose, and goal for each release and sprint
    • Approachable and available to team members to answer detailed questions about requirements
    • Understand and represent the interests of customers and stakeholders such as: customer service, sales, development management, and executives
    • Engages and solicits their feedback to validate priorities and compromises
    • Constructive Conflict Resolution
    • Demand / assure accountability
    • Effective planning and forecasting in spite of the inevitable uncertainty and unknowns
    • Understands and applys Agile and Scrum principles and practices

Balances new feature delivery with high quality software while minimizing creation of additional technical debt for sustainable software development.

[Next we’ll cover Product Owner Career Paths]

FAQ on Career Paths of ScrumMasters for Management

scrummasters As Agile and Scrum grows deeper into the market it is valuable for Management to communicate the rewarding and desirable career path that a ScrumMaster can have… even beyond just leading single Scrum teams.

See our first post on ScrumMaster basic FAQ for Managers

Before you go through this, it may be very helpful to first understand the following:

Eventbrite - Certified ScrumMaster Course (CSM) in Atlanta, GA - Bring a Friend = iPad!

Frequently Asked Questions on the ScrumMaster Career Path

Pathways

Q. What are possible steps in ScrumMaster career path?

A. There is more than 1 step on a ScrumMaster path including:

  1. No title appended – Entry level working ScrumMaster with CSM training < 12 months experience
  2. ScrumMaster appended – Qualified working ScrumMaster with > 1 year experience plus 2 days of continuing education per year of experience (per Scrum Score Card)
  3. Senior ScrumMaster – Full time ScrumMaster position handling multiple teams, often also acts as ScrumMaster for a Scrum of Scrums.  Demonstrates learning additional knowledge and greater experience than #2. ScrumMaster
  4. Coach ScrumMaster – Full time ScrumMaster who is booked on a regular basis to coach and train other teams, sites, and/or groups.  Demonstrates additional coaching qualifications beyond #3. Senior ScrumMaster

Q. Does this career path include the Senior ScrumMaster?

A. Yes, but it’s not a necessary step to the Coach ScrumMaster level

Q. Do we need a different career path to get to be a Senior ScrumMaster?

A. No, that is one possible step on the ScrumMaster path

Q. How does this relate to other careers in Product Development?

A.  ScrumMaster may be an add-on role to another product development job such as Software Engineer and may be considered favorably for advancement to other positions such as management.

Q. What are some possible stepping off points into other jobs or roles?

A. Some possible stepping off points include other leadership roles such as a manager job or Product Owner role.  Someone may also choose not to continue as a ScrumMaster and continue to progress in their chosen position as a development contributor.

Q.  How does Certified Scrum Developer fit into ScrumMaster career path?

A.  CSD fits into Software Engineer Career Path rather than this ScrumMaster path.  It would be a definite plus for a Certified ScrumMaster who is also a programmer to become a Certified Scrum Developer.

Q. Does a ScrumMaster career path lead to a management position?

A. Maybe.  Excellence as a ScrumMaster requires good leadership and people skills which are also critical in a management role. The ScrumMaster career path has multiple possible outcomes and we don’t suggest that any of them indicates greater success than another outcome. One possible outcome is accepting the challenges of a management position instead of ScrumMaster.  Note that it is considered a conflict of interest for a ScrumMaster to at the same time hold a manager position.

Q. Will experience in a ScrumMaster role be a requirement for progress into Management?

A. No.  It’s not a necessary pre-requisite to management.

Inputs

Q. Who is eligible to become a ScrumMaster?

A. Really anyone. But look here for best ScrumMaster characteristics.

Q. Who selects / approves ScrumMaster candidates?

A. Development Managers will ultimately determine who is eligible based on their confidence in an individual’s leadership abilities and their enthusiasm for improving agile development. Our biggest concern first is always putting the right people on the right teams, including a ScrumMaster. We use Team Science to do this. Find out more here.

Q. Where would candidate ScrumMasters come from?

A. People can volunteer to be ScrumMasters or be nominated by management

  • Needs to be voluntary, even if Management suggests or nominates a person.
    • Individuals volunteer or express interest (manager can decline)
    • Managers can identify candidates with skills (individuals can decline)

Q. What levels of experience would they have?

A. ScrumMasters should have experience in a software development job such as programmer, tester, or business analyst.  Ideally they would already have some experience as a Scrum team member.

Q. What ‘behavioral skills’ would they demonstrate?

A. Some of the more important behavioral traits include:

  • leadership
  • good communication
  • good people skills
  • facilitation
  • organizational skills
  • conflict resolution
  • negotiation
  • courage
  • assertive
  • coaching

Q. How does someone start out? What training or accreditation is a prerequisite?

A. The first step on a ScrumMaster path requires CSM training and a 6 month commitment to serve as a ScrumMaster after management approval

Q. Why should managers encourage their most qualified people to consider the ScrumMaster role?

A. ScrumMaster is a crucial role for succeeding with Scrum. A highly qualified person who has both the respected technical skills and behavioral traits can raise the performance of the whole team in the ScrumMaster role.

Q. What about people who are trained and qualify as ScrumMasters but are not currently assigned to a team.

A. People may also be qualified and ready to serve but working as a regular team member until they are asked to serve as ScrumMaster on a new or different team.  Qualifications and “active reserve” status will be documented for backup ScrumMasters in the on-line list of company ScrumMasters.

Exits

Q. What will happen if I want to go back into the team?

A. It is OK for people to decide they don’t want to continue in the ScrumMaster role.  However, new ScrumMasters should commit to serving in the role for at least 6 months.

Q. Who “pulls” a ScrumMaster if they are unsuccessful in the role; team or management?

A. ScrumMasters need the trust and confidence of both management and their team.  ScrumMasters serve the team and a team can ask for a different ScrumMaster if the entire team agrees.

FAQ on Most Common ScrumMaster Questions for Management

scrummaster-retrospective-management-agileAs Agile and Scrum grows deeper into the market it is valuable for Management to communicate the rewarding and desirable career path that a ScrumMaster can have… even beyond just leading single Scrum teams.

Before you go through this, it may be very helpful to first understand the following:

Eventbrite - Certified ScrumMaster Course (CSM) in Atlanta, GA - Bring a Friend = iPad!

Frequently Asked Questions on the ScrumMaster Role

Q. Is ScrumMaster a job title or a role that someone with an existing job title fills?

A. It is first and foremost a role in Scrum but may also be used as a title where a person is filling that role for multiple teams and it becomes a full time job.

  • ScrumMaster is a role that may be appended to a regular job title

Such as: “Sr. Software Engineer – ScrumMaster”

  • And in the case of a “full time” ScrumMaster it may be their entire job title.  Such as: “ScrumMaster”

Q. Can it be a role and still have a career path?

A. Yes, today a typical “career path” at looks something like: I – associate, II – junior, III – senior. The ScrumMaster “path” looks more like steps or supplements added to other job title oriented career paths.  It may have options and branches rather than just a “ladder” with various levels.  A ScrumMaster could also start as backup for primary on a team.

Q. How do you add it to your tile on email, business card etc?

A. Yes ScrumMasters who meet the qualifications outlined for this career path may append “- ScrumMaster” to the regular job title.  They may also show CSM or other certifications from recognized professional organizations.

Q. What models for ScrumMaster and team should we consider?

A. Valid options for ScrumMaster working with a team include:

  1. Full time ScrumMaster who fills the role for one or two teams and/or Scrum of Scrums
  2. Part time working ScrumMaster added to responsibilities of functional job title (not ideal as a SM should be focused primarily on one team.

Q. Is a ScrumMaster on the team – are they considered a team member?

A. The ScrumMaster is a team member. They could contribute either as:

  1. A working member of the same team where they contribute work in addition to filling the ScrumMaster role. This is currently the predominant pattern at the company: “I like a ScrumMaster to be a working team member.  I believe it gives them better insight to the problems/impediments that exist and a closer relationship, which builds trust, with the team itself.”
  2. A facilitator on the Team.  This is the case for “full time” ScrumMasters, and it’s also possible they could fill the role for one team while working as a contributing member of another team. Note that some people suggest that this allows the ScrumMaster to be more objective and impartial in coaching the team.

Q. What is a ScrumMaster responsible for?

A. “While a ScrumMaster does not assume responsibility for the success of the project -that remains with the team – a ScrumMaster does assume responsibility for the team’s adoption of Scrum and practice of it.”

Q. How much time should a person expect to spend on ScrumMaster activities instead of primary job title activities?

A. A ScrumMaster should make this role their top priority to focus on benefits to the overall team. Their load will vary from sprint to sprint depending on what impediments and issues the team is dealing with. Newly formed teams typically take more ScrumMaster time; 50%-100%, while experienced ScrumMasters with established well functioning teams might spend 50% or less of their time on the ScrumMaster role.

Q. How many Scrum teams would we expect a full time ScrumMaster to handle?

A. One or at most two teams.  See question above about how much time.

Q. If you were a “full time” ScrumMaster what title would you have?

A. “ScrumMaster” when not appended to another title would mean that it is a full time responsibility.

Q. Would the title for a Scrum of Scrums ScrumMaster typically be a Project Manager?

A. Not necessarily.  Only if the person previously had Project Management qualifications and experience in which case they could have a “Project Manger – ScrumMaster” title, otherwise their title would just be “ScrumMaster”.

Q. What skills and experience do I gain?

A. ScrumMasters exercise and develop their leadership and interpersonal skills along with training and continuing education in scrum and agile development.

Q. What qualifies as continuing education and who needs to approve it?

A. Example Continuing Education Activities include:

  • Internal, onsite, or public Agile training classes
  • Agile topic meetings at local professional organizations
  • Agile workshops and seminars
  • National or International Agile software development conferences such as Agile 2010

Management has budget approval of the individual’s costs for attending continuing education. The company publishes guidelines for qualified continuing education activities and may review and revise these from time to time with input from ScrumMasters and management.

Q. What professional certifications are applicable to a ScrumMaster?

A. The Scrum Alliance offers several levels of certification:

  • Certified ScrumMaster CSM – required to serve as a ScrumMaster
    • 6 month commitment to serve as a ScrumMaster at the company
  • Certified Scrum Professional CSP – 3 year of experience to qualify
    • 12 month commitment to serve as a ScrumMaster
  • Certified Scrum Coach CSC – > 5 years of experience to qualify

Q. Should the company support and pay for people to become certified?

A. Yes, The company will support and pay for Scrum related certifications based on the ongoing commitment from the individual to apply the certified skills as outlined in the prior question on applicable certifications.

Q. How does this affect desire for certification in other jobs and roles?

A. In the future we should answer this question as we define career paths in other areas based on the value and relevance to each role or position.

Q. Is certification required?

A. CSM is required to become and serve as a ScrumMaster.  Additional Certification is not required but is supported and encouraged. Continuing education is required for active ScrumMasters to spend at least 2 days a year on improving their knowledge and skills for agile software development.

Q. Will the company pay for advanced certifications?

A. Yes, based on individuals continuing commitment to serve as ScrumMaster using the certified skills

Q. What recognition and reward do I receive?

A. Opportunities for recognition and reward include:

  • Recognition from management and team members
  • Extra Career Development & training opportunities
  • Participation in the company ScrumMaster Community
  • Resume building
  • Certification

Q. Should there be a financial reward for being a ScrumMaster?

A. Additional financial compensation for ScrumMasters who take on this role in addition to an existing job title may be appropriate to recognize the added commitment and responsibility expected from ScrumMasters. Development management and HR should consider their existing position and compensation to determine the appropriate amount.

Note opinions are split on this point. There is value in this to consider that; being a ScrumMaster “feels like a thankless job” and also to make the management’s commitment to the role more tangible.  The counter argument was “is this necessary?” This would be a plus but was not necessary.

[In our next section, we cover Career Paths]

Being an Agile Coach – Making Effective Decisions

change-ownership-agile-decisionsMAKING EFFECTIVE DECISIONS

Decision-Making is obviously one of the major functions of the Agile coaching process.

Myths of Decision-Making:

  1. The higher up the decision is made the better it is. So, if the President makes the decision it is obviously a better decision than a decision made by a Vice-President. This is not better because we will be moving back to centralization where one person dominates everything. Decisions tend to naturally go up the organizational chart eventually anyway.
  1. The longer we consider a decision the better the decision will be. This is not always the case. But decisions can grow stale and stagnate if dwelt upon too long. The more complex the issue, though, typically more time needs to be allotted… not to think… but to experiment!
  1. A good decision made late is better than a mediocre decision made early. A decision that will really benefit a team needs to be made early rather then last minute. Precious time is often wasted in the lollygag scenario. Time factors often dictate that a decision must be made. And even if the best decision is not made, at least a decision was made in time.

Causes of Ineffective Decision-Making:

  1. The lack of clearly-defined goals and objectives. People don’t act because they don’t know which direction to go. Decisions can’t be made to do things that haven’t been previously decided to do.
  1. Insecurity of position or authority. Decisions are postponed because the leader  is afraid of the possible consequences.
  1. Lack of information – no alternative seems clear OR all alternatives seem viable.
  1. Desire to retain the status quo or simple fear of change – there is comfort in the comfort zone. But still, because things change and the team needs to develop and change as the market changes.

The Problem-Solving Process of Decision-Making:

Decisions are made, typically, to solve problems:

  1. The orientation to the situation – we get familiar with the background of the problem. Analysis, experience, training, skill, and administrative intuition are helpful in determining the truth of the situation.
  1. The identification of key facts – we will never have all the facts but we can get the facts that truly identify the reality. Utilize effective questioning. We want to ask “open” questions that will give us information rather than a simple yes or no. Carefully sift through the information and deduce logically
  1. The identification of the major problems in the situation: Look for the causes of the effect that have been seen or demonstrated. Why are things happening the way they are? What caused this issue? Again, carefully sift through the information and deduce logically. Get insights from others who can give information from another perspective.

Often, the unique situation you are in requires you to do a lot more research and problems solving to help leaders make good decisions… At the end of the day though, I would suggest, always taking an empirical approach. Experimentation is key. The more you experiment… the more you can learn quickly!

Being an Agile Coach – Dealing with Conflict

conflict-agile-fingers-pointing

The word “conflict” tends to stir up emotions in corporate America. Few companies want to find themselves in conflict. Most employees will view conflict as a bad thing and something to be avoided at all costs. But some conflict can actually be healthy. The reality is that disagreements do not have to turn into fights. We can keep our differences in check if we have a few basic understandings regarding conflict. Conflict occurs when two or more people with mutually exclusive viewpoints attempt to solve a problem.

Two kinds of Conflict (healthy and unhealthy)

Conflict is unhealthy when it negatively impacts the company or team by hindering or limiting their ability to do productive work.

Conflict is healthy when the opposite occurs. When conflict is viewed and handled appropriately.

We know conflict is unhealthy when:

  • People no longer calculate their remarks to edify or change others. Instead, they plan their remarks (often unconsciously) to hurt, demean, defame, or even destroy another
  • People begin to question whether their relationships can weather the storm of difference
  • People feel rejected by those who were once considered friends
  • People feel they have no control and the odds are against them
  • The pain of the competition is greater than the exhilaration of the challenge
  • People make accusations, and it seems that “others” want to destroy or split relationships down the middle.
  • People use words that have violent connotations

Conflict is healthy when:

  • The people involved feel confident they can manage the differences
  • Those involved adhere to firmly to decision-making processes authorized by the team and working agreements of the company
  • People operate within the specifically stated, generally understood rules of appropriate behavior in the company
  • People cooperate in the process suggested by the leadership

Reactions to conflict

  • Conflict is wrong.

Some individuals believe that conflict is always wrong. The mindset is that people in a copmany should be in agreement and live in harmony. They become nervous when team members express differences of opinion. They “lovingly” try to encourage people into one opinion. The attitude does not acknowledge that legitimate differences can exist among different people.

  • Conflict is an opportunity to exercise power.

Some people view any discussion as debate and any issue as a time to win at any cost. These people get their thrills in the competition of the moment. Winning the issue is oftentimes far more important than the issue itself.

  • Apathy (this doesn’t involve me)

Some people do not care much about the outcome of the issues involved. The apathetic spirit comes from several sources including burnout, fatigue, stress, a defeated spirit, or a different set of priorities.

  • Personal affect (this does involve me)

Some people do have a considerable stake in the outcome. These often include the leader, staff, board members, managers, and other directly involved individuals. People often believe that the outcome will affect their reputation and/or their feelings of self-worth. Oftentimes the emotional involvement clouds an individual’s reasoning and judgment surrounding an issue.

  • Conflict might split a company

Some people become nervous when any disagreement occurs in a company or team because they believe it will divide the team needlessly. These individuals many have vulnerable feelings left from past conflict that was handled in a hurtful way. Whatever the reason, they tend to sweep all controversial issues under the rug and hope they go away. They would rather stay in a bad situation than risk the unknown.

Responses to Conflict Continue reading “Being an Agile Coach – Dealing with Conflict”