Understanding Scrum Roles - keystepstosuccess.com

1 Understanding Scrum Roles through System Modelling (using Causal Loop Diagrams). Note: Causal Loop Diagram (CLD) is merely a system modelling tool, used to facilitate a dialogue between parties. It is not a final, conclusive or best way to illustrate a given interaction between variables in a system. CLDs are always situational, circumstantial and conditional. System Modelling exercises, done in corporate settings, may vary from team to team, company to company, industry to industry. They could be based, on participants' domain knowledge, perspectives and personal bias. Gene Gendel, Certified Enterprise Coach 1. Legend for Causal Loop Diagrams Goals High, overarching/strategic goal that needs to be achieved Variables System elements that have an effect or influence on other system elements (other variables).

2 Causal links Arrows that connect related variables Opposite effects o annotation near an arrow; suggests that the effect of one variable on another is negative ( - feedback loop). Delayed effect || annotation that disrupts a causal link (arrow); it implies that there is a delayed effect of one variable on another variable Extreme effects One variable has an extreme (beyond normal) effect on another variable; it is represented by a thick arrow Constraints c annotation near arrow; implies that there is a constraint on a variable Quick-fix reactions QF annotation near an arrow; action that brings short-term, lower-cost effect into a relationship between two related variables In System Modelling, we mostly care about Causations Correlation - relationship between two system variables (event or action), where there is no direct dependency.

3 A relationship can be positive or negative. Causation - cause and effect , is relationship between two system variables (event or action), where change in one leads to change in another. Gene Gendel, Certified Enterprise Coach 2. System Modeling for Product Owner Role System Goal: to support Making efforts to Improving Well-defined Scrum Teams in agile identify appropriate organizational Likelihood that || Acceptance Criteria product development, candidate for the role design on Team will and using Scrum of Product Owner business side produce PSPI. Definition of Done every Sprint Accordion QF Likelihood that ( Against the Developers are Likelihood that Wall ) Designate so o Likelihood that Conventional clearly explained sprint priorities / Fiscal called Product real & educated o organizational make sense to Budgeting Owner Product Owner strategy and Developers will get involved o vision Low cash Likelihood that real supply c Users will be o supportive of o Absence of career Extent to which Product Owner Resistance of real so called.

4 Path, trivialization of Product Owners to Product Owners the role. Lack of HR. Likelihood that real engage and work are necessary support, motivation &. Product Owners two jobs for one Likelihood that Likelihood that proper incentives for Developers are will receive quality paycheck . Product Owner waterfall artifacts are o Training/Coaching talking to real Users produced and forced and provide upon Developers clarifications Need for status Degree of frustration Level of contractual meetings, and tension, leading System gaming ( Us vs. Them ) Degree that RAGs/RYGs and || to best people & blame shifting relationships between Developers other system understand business leaving Business & IT. gaming methods domain || o Gene Gendel, Certified Enterprise Coach / You may follow embedded URLs for additional references / 3.

5 System Modeling for ScrumMaster Role System Goal: to support Efforts to identify Organizational Likelihood that good Scrum Teams in agile appropriate improvements Values and product development, candidate for the role || ( flattening) on Principles of Scrum using Scrum of ScrumMaster IT side will be followed QF. Designating left o Likelihood that Team of Likelihood that Lack of protection and over people to o o Developers is shielded right-minded & safety for ScrumMaster role from external educated ScrumMaster ScrumMaster disruptions will get elected o Likelihood that ScrumMasters will Likelihood that systemic Likelihood that Team will receive quality o impediments will be establish good dynamics, Training/Coaching escalated to sr.

6 Cadence and is able to Absence of career path, trivialization of the role, management and deliver predictably to c lack of HR support. removed Customer Lack of proper o Low cash motivation & incentives supply for ScrumMaster Need for status meetings, RAGs/RYGs and other o system gaming . Odds of seeing o methods Likelihood of falsely Command & o Odds that the role of holding Developers Control behaviors, ScrumMaster will be Accordion . accountable for micromanagement perceived as temporary Degree of frustration ( Against the systemic impediments Wall ) & bureaucracy and unimportant, from and tension, leading Conventional /. o organizational to best people Fiscal Budgeting perspective leaving Gene Gendel, Certified Enterprise Coach / You may follow embedded URLs for additional references / 4.

7 System Modeling for Scrum Team Developer Role # of low-skilled component Hiring System Goal: to developers low rate support Scrum Acquisition and Need for separate Project lateness. o QF. Teams in agile retention talented T- Integration Pressure to meet product shaped/cross- Sprints release deadlines development, using functional Developers Product quality. Poor Scrum Customer Happiness code/design Likelihood that o Teams will be working on selected Level of contractual c ( Us vs. Them ). Chances of building Components Low cash relationships between out cross-functional supply within IT. Scrum Team Desire of each o Team to have its Likelihood that own Component System gaming Teams will be Backlog & blame shifting Lack of working on motivation & customer-centric proper incentives features for Developer to Job descriptions Local Optimization become T- ( PM, BA, QA, by each Team to Degree of frustration shaped Arch) and HR stay busy and tension, leading policies not to best people supportive of Scrum Likelihood of leaving producing PSPI.

8 Accordion every Sprint Likelihood that any given ( Against the Team may work on low Wall ) Siloed Conventional / priority items from Product Fiscal Conventional departments Owner's strategic view Need for, INTERNAL to Budgeting organizational and groups of (System Optimization) IT, status meetings, design specialty RAGs/RYGs and other workers system gaming . methods Gene Gendel, Certified Enterprise Coach / You may follow embedded URLs for additional references / 5.