All posts by Gene

Motivation 3.0 Is Required to Transition from Tribe Stage 3 to Tribe Stage 4

black_green_black_thin_2

Author: Gene Gendel

In his book Drive, Daniel Pink says that when it comes to motivation, there’s a gap between what science knows and what business does. Our current business operating system is built around external, carrot-and-stick motivators — which don’t work and often do more harm than good. We need a system upgrade. And the science shows the way.

This new approach has three essential elements:

  1. Autonomy: The desire to direct our own lives
  2. Mastery: The urge to make progress and get better at something that matters
  3. Purpose: The yearning to do what we do in the service of something larger than ourselves

According to Pink, humans evolve through three distinct stages of the Human Operating System:

  1. Motivation 1.0 presumes that humans are biological creatures, struggling to meet basic needs for food, security, and sex. This system is mainly good for survival struggles.
  2. Motivation 2.0 rests on Theory X of Human Motivation, when management assumes that employees are lazy, tend to avoid work, and best respond to rewards and punishments in their environment.
  3. Motivation 3.0 rests on Theory Y of Human Motivation, when management begins to understand that when it comes to intellectual work, employees are ambitious and self-motivated and will exercise self-control. This system presumes that humans seek purpose maximization no less than profit maximization…

– See more at: https://www.scrumalliance.org/community/articles/2014/july/motivation-3-0-is-required-to-transition-from-trib#sthash.sQjXb3CU.dpuf

Scrum and Kanban at the Enterprise and Team Levels

black_green_black_thin_2

Author: Gene Gendel

Scrum, as the most structured of all Agile frameworks, is a great way to ensure predictable, strategically planned, incremental product delivery. Scrum ensures good responsiveness to frequently changing market demands. Although nonprescriptive, Scrum clearly defines certain roles, responsibilities, and ceremonies.

Kanban, for the most part, is silent about certain aspects that Scrum suggests explicitly (e.g., team size, velocity, story point estimation, timeboxing, Scrum ceremonies, etc.). Kanban is less structured than Scrum. Being a true pull-based system, Kanban is a great work-flow visualization tool that can be effectively used for WIP management. It is a great tool to use in production support or the gradual redesign of legacy systems; business priority-driven new product development is not the main goal….

Handling Interruptions in Scrum: 4 Options (Part 2)

black_green_black_thin_2Author: Gene Gendel

There are four commonly known ways that teams use to handle production support, or other “interrupt” items. Frequently, these items are classified by “levels” of priority/criticality, with L1 being the lowest and L3 being the highest priority. As we continue from Part 1 of this two-part article, we look at the remaining two ways of interrupting Scrum sprints–and share what can be done about them.

Read more at: http://www.projectmanagement.com/articles/303519/Handling-Interruptions-in-Scrum–4-Options–Part-2-

Handling Interruptions in Scrum: 4 Options (Part 1)

black_green_black_thin_2Author: Gene Gendel

In an ideal world, a cross-functional Scrum team must be fully focused on Scrum. The team is also expected to hear a voice of one customer only: the product owner. But what happens when reality intervenes and you get pulled in other directions?

In this two-part article I will:

  • Highlight common interrupt challenges I’ve encountered for organizations new to Scrum in general, and large organizations in particular
  • Outline four common interrupt scenarios and explain what you can do to handle these interrupts and maximize your productivity.

I’ll use the example of my old-time friend “Joe,” a senior software engineer who served as ScrumMaster on one of the Scrum teams….

Read more at http://www.projectmanagement.com/articles/302036/Handling-Interruptions-in-Scrum–4-Options–Part-1-

Epic-Level Estimation

black_green_black_thin_2

Author: Gene Gendel

Imagine: You are about to form a new feature team that is composed of bright, cross-functional experts, self-motivated and self-managed. They all worked in Scrum settings before and are fully supportive of Agile principles. The organization they work for is properly structured and it nicely supports the adoption of Agile/Kaizen culture.

Imagine that the team interfaces with an experienced PO who comes from an end-user community, has a lot of client-facing product management experience, fully understands principles of Agile product development, does not tolerate waste, appreciates benefits of incremental value delivery, is fully empowered, and knows how to effectively partner up with technology. . . .

Reviews, Appraisals and Incentives

black_green_black_thin_2Author: Gene Gendel

I wanted to start this discussion with Wikipedia definition of Performance Appraisal:

A performance appraisal (PA), also referred to as a performance review, performance evaluation,[1] (career) development discussion,[2] or employee appraisal[3] is a method by which the job performance of an employee is documented and evaluated. Performance appraisals are a part of career development and consist of regular reviews of employee performance within organizations.”

Interestingly enough, while all three terms are being included in the same definition (“review”, “evaluation”, “appraisal”), in practice, companies predominantly use the term “review” to describe PA as it implies less scrutiny and preconception towards an employee. But does this change the essence of the process if a less abrasive term is being used?

Usually, PA process starts with setting individual career goals by an employee. Of course, this is not done in a vacuum of what an employee only chooses for herself. Individual career goals should be in-line with organizational/department career goals, usually set by management. It is expected that throughout a year, an employee has to steer herself towards set goals, while performing her day-to-day job responsibilities.

Every company that supports PA process has a scoring system (variations exist) to rank employees, against other employees, based on score that an employee earns, while performing her yearly accomplishments (goals set vs. goals achieved). Some organizations offer a mid-year (quarterly, at best) check-point to employees, at which an employee reviews with her manager how she is performing with respect to the goals, set originally. Practically, no companies handle PA as an actively managed, iterative agile process.

For most companies the whole PA process, typically serves the following three main purposes:
1. To identify low-performing employees that are potentially a subject to downsizing
2. To identify high-performing employees that are potentially a subject to promotions
3. To decide how discretionary incentives (bonuses) can be distributed among employees
While on the surface PAs still appear as an effective way ensure quality of employees and provide benefits to organizations, under the surface this process presents real challenges. These challenges become more visible at organizations that are in the process of adopting agile culture, since in agile environments systemic organizational dysfunctions get exposed much better.

But before we dive deeper in the discussion, let us first briefly refer to some credible research and studies that exists today:

In his book “Out of the Crisis”, originally published in 1982, Edward Deming discusses Seven Deadly Diseases of Management and refers to individual performance reviews and performance evaluation as Disease # 3. Deming’s philosophy of transformational management is about seriousness of barriers that management faces today, while improving effectiveness and striving for continual improvement. Deming argues that trying to evaluate and measure workers with the same yard stick causes more harm than good to individuals and companies.

Tom Coens and Mary Jenkins offer specific suggestions on how to replace performance appraisals with a more effective system that emphasizes teamwork and empowerment in their book “Abolishing Performance Appraisals: Why They Backfire and What to Do Instead. Coen and Jenkins discuss new alternatives that produce better results for both managers and employees.

In his Forbes article “Eliminating Performance Appraisals”, Edward E. Lawler III, a distinguished professor of Business at the University of Southern California, advocates that organizations stop doing performance appraisals. Professor Lawler states that performance appraisals frequently do more damage than good, with damage levels fluctuating between wasted time (least troublesome) to reasons for alienation of employees and creating conflicts between them and their supervisors (most troublesome).

Garold Markle, an author, executive consultant and speaker, leverages his studies and experience with systems theory to illustrate his points with real-life examples of why employees and managers both have come to believe the “ubiquitous performance evaluation as industry’s poorest performing, most ineffective, and least efficient personnel practice”. In his book “Catalytic Coaching: The End of the Performance Review”. Markle provides an innovative way to measure ineffectiveness and inefficiency of performance evaluations and then introduces his catalytic coaching to replace them. His statement is awakening: “People hate performance reviews”.

In his book “Drive”, Daniel Pink offers a paradigm-shattering view on what truly motivates people in their lives. Pink draws on four decades of scientific research on human motivation, to expose a mismatch “between what science knows and what business does”. Pink challenges the mistaken belief of many that people doing intellectual work, will demonstrate higher performance, when incentivized monetarily. Bas to Pink’s research, it becomes clear that individual performance evaluations and individual appraisals that are linked to monetary rewards, are not an effective way to steer individuals to become more efficient and productive. Therefore, they should be abolished. And the list goes on….

So, now lets take a closer look at the problem, with some specific examples:

 

Fabricating Goals to Game the System

Are goals that employees officially set for themselves (in a system of record) truly reflect their genuine, personal goals?

It is not uncommon that real personal goals are risky and challenging to achieve or may take longer than initially expected. Many other goals can be also situational or opportunistic: they may change as a situation changes or unforeseen opportunity presents itself (job market trends, other job opportunities, personal life). People want to have freedom and flexibility to adjust their goals to optimize their personal benefits; this is a human nature. There is no true personal benefit for an individual to “set in stone” her goals into a personal development plan at year-start and then having to deal with unpleasant consequences at year-end, IF she does not meet her goals. In general, in order to set her real goals, a person needs to know that it is safe to actively manage them along the way and, if needed, safely change and/or fail them, without fearing negative consequences.

But is there any safety with PA processes if job security, career advancement ability and ability to collect fair compensation are at risk? If there is no personal safety, the exercise of setting personal goals becomes nothing but a routine of faking objectives that are “definitively achievable”. People are forced to do it, to minimize the risk of being scrutinized by their management for not meeting their goals. Setting individual goals becomes just a formality that brings no true value to an employee.
The process of individual performance reviews becomes even less meaningful if people work in small teams, where swarming and collective ownership is important, and joint delivery is expected. In cases such as these, people are forced into unhealthy competition with each other over goals, trying to privatize what should be owned and claimed collectively.
Another challenge with evaluating employees’ individual career goals is that in pursuit of personal goals, people frequently “drop the ball” and de-prioritize common goals. Again, this dysfunction becomes much more vivid in going-agile environments, where agile frameworks (e.g. Scrum, Kanban) de-emphasize individual ownership and reinforce the importance of collective ownership. Often, close to mid-year and end-year performance reviews, collaboration and mutual support of team members worsens, as silos get created and everyone begins to think about their own goals, at expense of shared goals. This translates into inefficiency and productivity drop: swarming, velocity and throughput go down; cycle time and queues grow; handovers take longer.

 

Example:

Jane is an employee of a large insurance company. She is being requested to enter in a company’s system of record her personal goals – things that she intends to achieve throughout a year.   Jane is smart and in order to avoid any unwarranted risk, where her personal success depends on success of others, she creates goals that are free of dependencies. Jane creates a set of personal goals that other group members do not know and don’t care about. Her line manager John, also discourages Jane from sharing such information.

However, Jane does not work alone. Her day-to-day work is tightly coupled with work of other individuals in her group: Jim, Jeff, Jill, Joe and Julie.

Jane really values team work. She also feels that by closely working with her group members, by swarming and sharing day-to-day activities she can earn a lot more than if she worked by herself.   This is where Jane decides to put her full focus: on team work. She does not feel that creating an additional set of personal goals can add real value to her professional growth. But Jane needs to “feed the beast”: she needs to provide her line manager with a list of “achievable” bullets that the latter can measure. At the same time, Jane does not want to create a conflicting situation with her colleagues, by diluting her focus on shared goals by shifting it personal goals. Therefore, she fabricates her personal goals: “quick kills” and “low hanging fruits” – something that she can easily claim as her “achievement”, without jeopardizing common interests of her team. Jane is forced to “game” the system to minimize harm to herself and her team.
In his book “Tribal Leadership”, David Logan describes five tribal stages of societal evolution. According to his research, corporate cultures typically oscillate between Stage 3 (“I am great and you are not”) and Stage 4 (“We are great and they are not”), with agile organizations trending more towards Stage 4. When individuals are motivated (a.k.a. “manipulated”) to think more about individual performance than about collective performance, they mentally descend to Tribal Stage 3 and, as a result, drag along their organization to this lower stage. It is very important for organizations and their senior leaders to understand that motivation is one of the most important factors that drive evolution of corporate culture.

Note: To understand how Motivation Evolution (defined by Daniel Pink in “Drive”) relates to Tribal Evolution (defined by David Logan in “Tribal Leadership”), please refer to this tool.

 

Unhealthy Competition, Rivalry and Jealousy

Let’s face it, overemphasizing individual performance evaluations and allowing them affect job security, promotions and compensation of individuals does not come free to organizations. It comes at high expense of lowered collaboration, unwillingness to share knowledge and provide peer-to-peer support, increased selfishness and self-centric behaviors. For individuals that are encouraged to work and produce collectively (e.g. Scrum or Kanban teams) uneven performance evaluations frequently result in jealousy and feelings of unfair treatment. These dysfunctions become more frequent around times when employees are due to mid-year and end-year reviews. PAs have adverse effects on individuals’ ability to focus on work and, as a result, produce high quality products and think of customer satisfaction.

It is worth mentioning, ironically, when dysfunctions are uncovered, it is agile that becomes the target for blaming.

But agile is hardly at fault here as it only provides transparency and reflection of already existing dysfunction.
Example:

Jane works alongside Jim, Jeff, Jill, Joe and Julie. All of them are smart, self-motivated and talented technical experts that cumulatively have more than 70 years of software development experience. Their work is intense: there are lot of deliverables and their timeframes are rigid. The group serves the same client for a number of few years and, so far, a client is happy. The work that this team performs, requires a lot of collaboration, collective thinking and brainstorming, teaching/learning from each other and, of course, collective delivery.

But then comes a mid-year review period and Jill notices that Jeff is not as supportive of her as he was at the beginning of the year. Jeff becomes less responsive to Jill’s requests, he does not share his knowledge as readily as he used to; he does not give advice. Tasks that used to be handled collectively by Jill and Jeff are now illogically split by Jeff as he tries to focus only on what he assigns to himself.

There is also a noticeable change in Julie’s behavior. Julie becomes very eager to be the one who stands in front of a client and presents deliverables of the whole team. This responsibility used to be rotated from one person to another, with no one caring too much about being a “spokesman”. But as mid-review came, Julie clearly stepped up to be the main, customer-facing presenter. Julie also tries to make it very obvious to John (the group’s manager) that it is her – Julie, who presents to a customer. Julie wants to be viewed as a “centerpiece” and gain most of spot light.

Jim’s contribution to the group’s efforts have also subsided. Early in the year, Jim used to be a very active participant at the team’s brainstorming meetings and workshops. As mid-year arrived, Jim started spending a significant portion of his time working on items that are not related to the team’s shared work; his focus has noticeably shifted to personal work that he does not even discuss with others.

Since the beginning of the year, it has been customary for the group to go out for drinks to a local bar, every Friday. But this tradition is now barely followed, at mid-year period. There seems to be less desire for the group to socialize outside work settings. Everyone finds an excuse not to make it. The group’s synergy has gone down noticeably. What used to be a well jelled team of great collective performers has turned into a group of self-centered individual achievers that want to be acknowledged for their heroics.
“Scripted” Ranking to Force-Fit into Bell-Shaped Curve
Typically, when an organization ranks its employees based on individual performance, a bell-shaped curve is produced, where samples (ranked employees) are binomially distributed around the median: majority of samples are centered (“center mass”), representing average performing employees, left tail – representing low performing, and right tail – representing high performing (over-achievers). Statistically, a bell-shaped curve is a normal distribution of any large sample. The symmetrical shape of a curve (“bell”), however, can be influenced by additional three main factors (forces):

  • Platykurtic distribution – it lowers amount of samples around the median (average performers) and increases amount of outliers (under-performers and over-achievers), equally on both sides. A curve remains symmetrical.
  • Leptokurtic distribution – it increases amount of samples around the median (average performers) and lowers amount of outliers (under-performers and over-achievers). A curve remains symmetrical.
  • Uneven distribution of samples on left and right sides from median – Typically, this increases amount of samples on left (under-performers) or right (over-achievers) tails of a curve, while also disturbing symmetry of a curve and evenness of sample distribution around median (average performers). A curve loses its symmetry

 

This statistical distribution is tightly coupled to actions that management takes towards its employees at year-end. However, the shape of bell curve, does not “drive” (as it might be expected) managerial year-end decisions; it is rather driven by them.

Managerial decisions are driven by financial conditions of an organization as well as other strategic organizational plans. When managers review their employees, they have to account for such factors to make sure that a bell-shaped curve does not exceed organizational capabilities of promoting too many employees and giving out too much money. Effectively, the entire process of performance assessments becomes a retro-fitting exercise that shapes a bell curve, basing it on organizational capabilities. This makes the process, practically, staged or “scripted”. What further ads to the irony of this situation is that at times an employee may report into a manager that does not even have sufficient skills for perform an objective assessment of an employee’s performance. For example, an architect or a software engineer that reports into a non-technical manager (e.g. PMO) has a much lower chance to objectively discuss her work accomplishments and receive an objective feedback during PA.

There is a need for an alternative approach that will help dealing with overly complex, over-staffed organizations that spend so much time and energy trying price-tag its employees.

Here is an idea: how about more thorough checks of background and references, more rigorous interviewing processes that involve practical (hands-on) skills assessments, try & buy periods, before hiring an individual full time or some other, more objective methods?

Instead of attracting cohorts of workers of questionable quality and then dealing with inevitable force reduction or worrying (or pretending to worry!) about employees maintaining and/or improving their quality, hiring managers should be striving to acquire and retain lower quantities of higher quality workers: self-motivated, enthusiastic professionals, with a proven track record and clearly defined career goals…AND be willing to pay them higher compensations. This may require offering more competitive base salaries, and abolishing manipulative discretionary incentives: removing money from the table makes intellectual workers think more about work, and less about getting paid. This approach would also ensure that quantity of employees is kept at a minimum (this also ensures lowering overhead, complexity reduction, organizational descaling), while maximizing quality. Such alternative should render performance reviews much less important or even obsolete as there will be no need to reduce employees at year-end or thin-slice discretionary incentives among too many candidates.

 

Example:

John is a line manager for the development group. John has great organizational skills, he is well spoken and can greatly articulate his thoughts. But John, has never developed software products; he is not technical. John knows that all of his team members are “good guys”: knowledgeable, enthusiastic, and mutually supportive. But when the team works together, John really cannot validate quality of work that they produce. (Luckily, there is one reliable measurement of the team’s success – it is customer satisfaction). The only thing that John can validate is the team’s vibe and spirit. But even when John notices disagreements or temporary misalignment among the team members, it is impossible for him to offer a constructive advice or understand a root cause. What is even more challenging and frustrating for John is that due to the nature of team’s work (closely collaborative, collectively shared) he cannot objectively assess individual performance of every team member. In conversations with John, the team members rarely use the word “I”; it is typically “we”.

John is in a tough position. How can he decide who the best performer on his team is and who is not? John needs to be able to ‘rank’ his people and based on ranking, decide who gets promoted and paid more at the end of the year. Deep at heart, John feels that everyone deserves a promotion and monetary “thanks” but he cannot satisfy everyone. John’s management informs him that only one person from the team can get promoted and the amount of incentive money allocated to his group is limited; in fact, it is less than last year.

Around mid-year time, John begins evaluating how each of his team members has performed up-to-date. John does this based on “achievable” goals that were set by each employee at year-start. John’s inability to truly understand the nature of peoples’ technical work adds to his challenge…and frustration.   He cannot objectively evaluate his employees, let alone rank them against each other.

Meanwhile, John’s management expects from him a ranking model that will fit into a bigger picture of organizational capabilities to give promotions and bonuses, for a given year. It means that even if John feels that all of his members are outstanding performers he will not be able recognize this officially. At most, he will be able to recognize that they have achieved their set goals. Further, based on what John learns from his management, he has to commit even less unpleasant act. Learning that certain percentage of a company’s workforce has to be reduced, John has to identify and set up for possible future downsizing some people from his group. It is clear to John that people that are outstanding performers are not the best candidates for downsizing (potential HR cases). Therefore, John decides to force-fit some of his team members into bell-shaped curve, away from the right-sided tail, towards the middle (average performers) and left-sized tail (underperformers). John uses organizational “script” to play his own team. What John does, is a wasteful act that is full of subjectivity and ambiguity. The process is also destructive to the team’s cohesiveness and morale. John is at risk of losing some good people sooner than he could expect.

 

Generating Waste
Rarely, do companies consciously analyze how much time and effort is being spent on performance evaluation process by employees, line management, senior management and HR. Unfortunately, for large, enterprise-size companies, these expenditures are already “budgeted for”. From the standpoint of lean thinking, today’s typical process of PA is conducted by line managers is a clear example of organizational overhead that slows corporate cultural evolution and prevents companies from maturing to Tribal Stage 4.
Example:

All members of the team: Jane, Jim, Jeff, Jill, Joe and Julie spend a lot of time during the year writing and reviewing their personal coals. John spends a lot of time reviewing and discussing personal goals of every team member. John also spends a significant portion of his time with his line management, discussing achievements and intended ranking for each of his subordinates. Overall, the amount of time this entire group of people spends on the PA process creates a lot of unnecessary procedural overhead and over processing.
Alternative Approaches to Performance Reviews

Are there any working solutions to this problem? Is it possible to ensure that organizational behavior towards employees (e.g. motivating and incentivizing) is more in-line with what is best for organizational prosperity, business satisfaction, waste reduction and the creation of more efficient organizational structure and Kaizen culture?  Is there a way to depart from archaic norms and behaviors gradually, without causing too much stress to an organizational ecosystem, perhaps, by offering alternative, less harmful, interim solutions?

First, lets be clear: a natural “knee-jerk” reaction of any individual when she is told by someone why she is not “perfect” and what she needs to do to improve is defensive. Of all reasons, the biggest reason is her understanding that based on the evaluation someone will decide how much she will get paid. Although an individual may keep her feelings and emotions concealed under political correctness and diplomacy deep under covers, there is harm being done. The end goal of any organization should be abolishing performance appraisals completely and substituting them with other, more effective methods of motivating individuals. But for now, lets look at some interim alternatives that can help us depart from individual performance appraisals gradually, by moving to less harmful approaches.

Here are some potential, interim (short term solutions) alternatives of how co-dependency between individual PA process and incentives allocation process can be dissolved (graphics are here):

  • Instead of prizing individuals – prizing teams and do this based on what an entire team produces, not a single individual.  If individuals must work in tight collaboration and are expected to cross-pollinate with expertise and produce together, what is the point to stress individual contribution and individual performance? Let a team, internally, decide who is pulling them up and who is dragging them down. Individual underperformers will be quickly identified in such settings, and a team will try to either expel them or help them to improve. Also, please note that prizing a team (monetarily, team bonus) does not have to be coupled to “performance assessment”. This could be done, simply, as a profit sharing model between business and technology: if work of technology has noticeably improved the bottom line of its business partners, the latter should be happy to prize hard and successful work of the latter.
  • Take away singleton decision making capability of defining a team deserves in terms a “monetary prize” out of line managers’ hands and “spread the wealth” across multiple parties: make it based on customers/stakeholders satisfaction, senior management satisfaction, third party feedback, etc. But again, judge teams, not individuals (important!).
  • Make monetary incentives allocation more objective and formula-driven, than subjective and single opinion-based. Here are a few “formulas” to achieve this:
    1. Monetary Incentives Are Equally Allocated among all employees whose work is tightly coupled and collective ownership is expected
    2. Monetary Incentives Are Allocated in Proportion to Base Salary of an employee: decide on employee’s costs when she is hired (based on expertize, experience, etc) and then fall back on formula “a”)
    3. Monetary Incentives Are Allocated based on Team’s Internal Voting, done confidentially (incremental, 360 review by all team members).

Note: Consider the above options as short-term, interim solutions on the way to completely abolishing conditional monetary incentives. Although, team-level incentives are less dangerous than individual incentives, they still carry harm in them: they make people think of getting paid, not about doing work.   Ideally, for any kind of intellectual work, money should be removed from the table.

 

Conclusion

The famous quote from the book “Out of Crisis” written by Edward Deming (originally published in 1982) summarizes this topic well:

“The idea of a merit rating is alluring. The sound of the words captivates the imagination: pay for what you get; get what you pay for; motivate people to do their best, for their own good. The effect is exactly the opposite of what the words promise.”

 

References

 

Feb 1-3, 2016. Certified LeSS Practitioner in New York

black_green_black_thin_2

Author: Gene Gendel

IMG_0336

Event Details

 Large-Scale Scrum (LeSS) is a framework for scaling agile development to multiple teams. LeSS builds on top of the Scrum principles such as empiricism, cross-functional, self-managing teams and provides a framework for applying that at scale. It provides simple structural rules and guidelines on how to adopt Scrum in large product development.

The Certified LeSS Practitioner course is an in-depth course covering the LeSS principles, framework, rules, and guides. It provides essential information for adopting and continuously improving LeSS in your product development group using various thinking tools, organizational tools and action tools. The course contains an overview of LeSS, stories on LeSS adoptions, exercises and extensive Q&A sessions to ensure we discuss the topics most of interest to the participants.

The Certified LeSS Practitioner course is for anyone who is involved a large agile adoption. Basic Scrum knowledge is expected. This can be achieved by attending a Certified ScrumMaster courseProfessional ScrumMaster course, or by thoroughly reading Scrum introduction material such as the Scrum Primer and practicing Scrum.

(To view photos and summary of the previous LeSS course (September, 2015) in NYC please click here.)


Registration:


Agenda

In this highly interactive course, participants will get a thorough introduction to LeSS, a deep understanding of the underlying principles and the concrete practices to help them to implement LeSS in their own organization.

Day 1

  • Introduction
  • The History and Overview of LeSS
  • LeSS Principles
  • Organising by Customer Value

Day 2

  • Organisational Impact
  • Feature Teams
  • What is Your Product?
  • The Product Owner Role in LeSS
  • Defining Done
  • Product Backlog

Day 3

  • The role of Management
  • Adoption in your Organisation
  • The ScrumMaster Role in LeSS
  • LeSS Sprint
  • Product Backlog Refinement
  • Sprint Planning
  • Sprint Review & Retrospective
  • Coordination & Integration
  • Technical Excellence
  • Working with multiple sites

There will also be multiple opportunities for participant-driven Q&A sessions.

After course completion

All participants will be a Certified LeSS Practitioner and will get an account on the less.works website. Here they can find additional information about LeSS, share course information and stay in contact with the other course participants.

All participants get access to the draft of the new upcoming book: Large-Scale Scrum: More with LeSS.

About the trainer

This workshop will be led by Karim Harbott.  Karim is an experienced enterprise Agile Coach and trainer. He has guided many large organizations through ‘Agile transformations’ and helped them on their journey to continuous improvement in their product development capability.

As a former Head of Scaled Agile at McKinsey & Co. Karim is comfortable operating at all levels of the organization, but specialists in the enterprise level and organizational redesign.

A trained business and executive coach, Karim is well placed to build internal capabilities in an organization; be it developing Agile Coaches, ScrumMasters, Product Owners, Developers or working at the C-level to help leaders make the changes necessary to enable true, large-scale business agility.

Karim is a Certified Scrum Coach, Certified LeSS Trainer, SAFe Program Consultant and Accredited Kanban Trainer.

  IMG_2289 IMG_2307 IMG_2304 IMG_2293 IMG_2292 IMG_2291 IMG_2290 IMG_2296 IMG_2298

Fallacies of RAG Reports

black_green_black_thin_2Author: Gene Gendel

How Much Can You Trust Your Navigation Instruments?

1944…Imagine you are flying back home from a risky military mission…If you are not able to vividly imagine what this experience is like, please follow this link:  http://www.keystepstosuccess.com/2016/01/b-17e-bomber-tight-coupling-of-color-coding-with-numerical-data/

RAG System in Conventional Project Management

Today, the RAG system is still widely used in conventional project management, as the method of rating   issues or reporting on status. The approach is based on the same basic colors: Red, Amber (or Yellow) and Green…

See more at http://www.projectmanagement.com/articles/315648/The-Fallacy-of-Red–Amber–Green-Reporting