All posts by Gene

04/11 – LeSS Talks: Branching Strategy and CI/CD in Agile Development, with Thierry de Pauw

Materials | Speaker’s Site

Main Take-away Points:
  • “Developing in isolation can help an individual go faster but it does not help a team go faster. Merge time and rework cannot be estimated and will vary wildly, and the team can only go as fast as the slowest merge.” – Steve Smith
  • “A spike solution is a very simple program to explore potential solutions. Build the spike to only address the problem under examination and ignore all other concerns. Most spikes are not good enough to keep, so expect to throw it away.” – Don Wells
  • “The objective is to eliminate unfit release candidates as early in the process as we can …You are effectively prevented from releasing into production builds that are not thoroughly tested and found to be fit for their intended purpose.” – Jez Humble and Dave Farley
  • “Feature Branching is a poor man’s modular architecture, instead of building systems with the ability to easy swap in and out features at runtime/deploy-time they couple themselves to the source control providing this mechanism through manual merging.” – Dan Bodart
  • “Feature Branching hinders integration of features.”
    “Feature Branching hides work for the rest of the team. Frequently merging back to mainline = communicating with your team”
  • “Feature Branching works against refactoring.”
  • “Feature Branching creates inventory.”
  • “Feature Branching increases risk.”
  • “Feature Branching creates cognitive overload.”
  • “Continuous Integration Your application is always in a releasable state on main line – with Trunk Based Development”
  • “Continuous Integration Your application is always in a releasable state on main line.”
  • “Break large changes into a set of small incremental changes”
  • “Use Branch by Abstraction when performing large refactoring.”
    “Feature Toggles to decouple feature release from code deployment.”
  • “Trunk-based development requires a big mindset shift. Engineers thought trunk-based development would never work, but once they started, they could not imagine ever going back.” – Gary Gruver

Additional Learning Assets:

03/14 – LeSS Talks: Johanna Rothman: How To Create a Career Ladder for Vertical and Lateral Movement

Materials

Johanna Rothman’s monthly newsletter “Pragmatic Manager” and her blogs can be found at www.jrothman.com and www.createadaptablelife.com


Additional Assets Relevant to the Topic:

Gap Between Science and Business
OKR: Narrowing the gap between “O” AND “KR”


Additional Learning Assets:

 

Changing Your Coaching Engagement Type

From Independent Coach  To Coach – FTE

Imagine yourself: you – for many years, investing into and developing your own career path, as an independent, professional coach.  You have years of experience behind your back, serving many different companies, many personal accomplishments, highest (and rarest) industry credentials, tens of thousands of community followers around the globe and lots of industry recognition, coming from the most recognized industry leaders.  Now, you are at the point in your life, when you still have enough energy to continue doing what you have been doing.  However, you come across, what seems to be, a great opportunity: you can join a great team, at a great company and work with some great people – as a full-time employee.  What do you do?  What do you need to consider, when deciding if such transition is a good idea for you?

Organizational Alignment

Initial Reporting Alignment: At the time of on-boarding, you want to make sure that you are positioned, organizationally (reporting-wise), in a way that will provide full backing and support to you, your profession/role and line of work.  It implies that your line management understands really well the essence of your role, as it is defined, according to the highest industry standards (could be different from an internal definition).

Reporting Alignment Over Time:  Organizational structures tend to change: re-orgs, down-sizing, strategic realignments. Although it is impossible to predict what exact changes may take place, it is important to inquire about any known plans for such changes for a foreseeable future, at the time of on-boarding.

Becoming a Report-Into Person:  One of the key conditions for being an effective coach is your ability to create a safety space around yourself: for your coachees, as well as junior colleagues that might be looking up to you, as a role model.  If you become a manager of other people, they will perceive you differently and your coaching relationship with them will most likely change.  It is strongly unadvisable for a coach, to take on a managerial role, at least, in the area, where coaching will take place. 

Focus of work

General Expectations: To an extent possible, try to discuss upfront what an organization will be expecting from you, as a coach, once you join it full time.  Will your role and responsibilities be consistent with your own understanding of what a coach should/should not do, as per well-defined industry standards?  How much of an impact will “staff augmentation” factor have on you?  Will there be any gap between what is expected of you as a coach (and related activities: consulting, training, mentoring) and other responsibilities you may have (a.k.a. conditions of employment)? Do you foresee any conflict of interest between multiple roles assigned to you?

Opportunity to Deliver Unique Value: How well is an organization aware of your unique coaching/coaching-related capabilities (e.g. trainer, mentor) that you bring to the table?  Will it see value in quality and authenticity of learning and education that you bring?  It is very likely that what you bring to the table is a significant extension to what an organization has today: if you don’t explicitly explain this, they will not know. 

Exemptions and pre-clearance

As an independent professional coach, over many years, you have made a lot of investment in your personal growth.  How much of this personal investment would you have to surrender, if you join a company, as a full-time employee?

Community Support: You spearhead local and global virtual communities, run public events, present at seminars and webinars, speak at conferences. For many years, this has been a huge part of your professional growth, as coach and the requirement to achieve and maintain your unique coaching credentials.  Will your new employer demand that you stop your activities?  Will it require a tedious approval process to continue each individual activity?

Blogging, Publishing, Audio/Video Recording:  You love giving back to a community. Over many years, you have written many articles, published and co-published books, have recorded podcasts and educational videos.  Will your new employer demand that you stop your activities?  Will it require a tedious approval process to continue each individual activity?

Outside Business Activities:  As a professional coach (also, trainer and mentor), you have unique capabilities to deliver coaching/mentoring/training content to general public – and it is in high demand.  You have built your own curriculums and intellectual property (lots of it is under creative commons) and this enables you to deliver your unique content. Teaching online classes and running mentoring cohorts is a part of your annual income.  Will your new employer demand that you stop your activities?  Will it require a tedious approval process to continue each individual activity?

Important: It is important that you discuss the above with your potential employer prior to on-boarding.  It is also critical that you make it very explicit that none of the above activities will be at expense of your paid work (focus, quality) that you will be expected to do for your employer. You must also make it very explicit that you will not be using any of your employer’s intellectual property or proprietary information, while engaging in outside activities.  Inquire, if you can receive in writing a one-time blanket exemption that will allow you to continue performing the above activities.

Compensation & Benefits

Base compensation: At the time of onboarding, explicitly discuss your base compensation that takes into account not only your current income that you generate as an independent coach but also the fact that your internal growth, and therefore, base compensation increase, might be different from that of a traditional employee.  Today, many traditional organizations still set employee compensation, based on how many people report into a person. As a coach, most likely you will have no people reporting into you, as his is inconsistent with how a coach should be positioned organizationally and relate to other people (see above).

Subjective compensation: Today, many companies still have subjective monetary incentives/bonuses, as a part of overall compensation structure. “How much of an overall compensation is represented by a bonus?” – it varies from industry to industry.  Many companies still pay bonuses, based on individual performance of an employee.  (Side note, as a coach, you may have to deal/challenge some of these existing organizational norms, as a part of your job.)  On a personal front, since you are a coach, all/most of your deliverables will be soft and not easy to measure (standard metrics don’t apply).  Therefore, you want to make sure that you are comfortable with your base compensation, so that if there are any omissions/shortcomings with your year-end bonus, the financial impact to you is minimal.  Ideally, you want to be less reliant on a subjective bonus, as a part of your overall compensation (“have the question of discretionary moneys removed from the table”, as per Daniel Pink)

Stock options:  You should inquire about common and/or restricted stock options.  Make sure you also find out about how equities are vested.  Some companies, may offer a stock, as a part of your retirement (see below) or bonus (see above) but under conditions that you remain employed with an organization for a certain number of years.

Pension & Retirement: This is usually standard for all employees: 401(K), annuities, other. Make sure you inquire about matching policies.

Health benefits: This is usually standard for all employees: medical, dental, other special coverage.  Make sure you inquire about who is a medical carrier(s), availability of family coverage, cost of premiums, deductibles.

 

From Coach – FTE To Independent Coach

Imagine yourself: You have been an employee with the same, or a few, reputable companies, for a number of years, as an internal coach.  You have learned a lot about internal organizational dynamics, structure, culture. You have reached a certain point in your career, where you feel that you would like to become an independent coach and explore other opportunities.  What do you do?  What do you need to consider, when deciding if such transition is a good idea for you?

Financial Cushioning: As you enter the world of independency, the first thing you must think about is how you will generate income.  Your income flow may not always be steady, there could be gaps between your engagements.  In consulting work, it is to be expected.  However, before disengaging from your employer you should either line up a few clients (at, least, short-term) or have enough financial cushioning (savings) to get you through the initial phase of being independent.

Your Personal Capabilities: As you become an independent coach, be also prepared to become your own boss, and a ‘jack of all trades’.  Your responsibilities may now include: extensive networking and business development, community service (public speaking, presenting, newsletter, etc.), becoming incorporated, purchasing general liability/other insurance coverage and other logistics.

Pipeline of Clients: As you enter the world of independency, you will have to learn how to balance between delivering quality work to your clients and developing your own ‘book of business’, for future engagements. This may require a very effective time and WIP management.  Consider going back to your past employer(s) and ask for referrals or ‘follow’ other exiting employees to their new places of work – and offer your services there.

Network and Public Visibility: As an independent coach, you will have to significantly step up your networking efforts (LinkedIn, Meetup, personal web site, presentations, podcasts, webinars) and increase your public visibility.

Uniqueness of Your Current Value: Today, the coaching market is significantly diluted. Over the last few years, many people with “used-to-be” roles have renamed themselves into coaches.  The current market supply of coaches is artificially inflated with professionals of low quality.  Unfortunately, majority of organizations are still not good at seeing a distinction between a great coach and a coach-pretender.  How do you envision positioning yourself, so that you stand out and draw clients’ attention to yourself?

Pursuit of Unique Credentials:  Just like the industry is flooded with coaches-pretenders, it is flooded with various certifications.  Be careful about certifications: not all of them come from authentic and reputable organizations; some of them are not even legit.  However, there are some unique, guide-level (elevated) credentials from more reputable organizations- industry leaders that can really add a notch on your professional belt. Consider pursuing those for your coaching and training credentials.

Opportunities for Partnership: You may wish to consider looking for people like yourself, independent, energetic individuals that have professional assets that complimentary to yours (personal certifications, training/coaching/certification capabilities, sales/marketing/networking skills). Consider forming a team. You don’t necessarily nave to be legally bound for such partnership.  Alternatively, you may consider sub-contracting through another larger and more established consulting organization (please, be careful with your choice, as not every big consultancy has a great reputation), while developing your own book of business and clientele.

Overall Business Plan:  You may wish to create a dynamic business plan, with short- and long-term goals for your business and professional development.  Please note, that these two are not the same: you don’t want to excel in one dimension at expense of another dimension. Another words, you want to stay balanced. Otherwise, you may end up being temporarily in high demand (e.g. due to great sales and marketing techniques) but underqualified or being in low demand (underutilized) but over-qualified.


Please, weight all pros and cons in all of the above dimensions, for both types of transitions and extend your research further, if required, before you make a decision.

References & Assets To Share

emphasize deemphasize
deep and narrow (meaningful, systemic improvements) broad & shallow (big-bang, “check the box”, superficial, fake changes)
system/global optimization (organizational level) local optimization (at expense of system optimization)
flat, lean, adaptive organizations complex, multi-layered, cumbersome organizations
light (very) tooling solutions and quality of human communication focus on heavy tooling and PMO management style
importance of working software (product), as success indicator metrics and reporting, as indicator of progress
feature teams (focused on products & customers) component teams (focused on applications & platforms)
component mentorship/teaching component ownership
simple, elegant, dynamic frameworks heavy, prescriptive, rigid frameworks & “operating models”
historical and market evidence, proof by experts “best practices”, cook books and unrealistic hypos
communities, as media for functional learning power towers of “special people” (e.g. center of excellence, PMO)
participation by volunteering and commitment participation by mandate and enforcement
dynamic, rolling-wave, product centric budgeting hard-fixed, fiscal year-end budgeting
creating and owning ideas renting ‘best practices’ from others
team performance, profit sharing individual performance and bonuses
job & salary security role security
simplicity of job descriptions complex titles and management roles
shared ownership, successes & failures outperformers and individual heroics
personal development goals, consistent with available career path manager-imposed, unrealistic individual goals (“legal trail for a rainy day”)
importance of hiring the best and growing the best pressure to hire/recruit low quality experts (including agile)

02/27 – LeSS Talks: Facilitating LeSS events virtually (using Miro, Mural)

Facilitating LeSS events virtually (Ideas, Tips & Tricks)

Tools and platforms shared in the session:

Additional Self-Study Assets:

DeveloperWeek2021: What is “UNDONE” Department And How To Eradicate It?

Synopsis:
Today, unfortunately, many agile teams are not yet able to create a true shippable increment every sprint. This is because their Definition of Done (DoD) is weak (immature).
As such, teams have a lot of UNDONE work at the end of every sprint. This work may take a lot of different forms and is usually passed on to a ‘special’ UNDONE department or group to be handled. In Scrum and in Large Scale Scrum UNDONE department do not exist.
It may seem that reasons for having UNDONE department are purely technical [limitations]. But this is rarely so. For the most part, they are political and have to do with traditional organizational design and sphere of control.

LeSS vs. SAFe: Understanding The Differences


History & Origins

SAFe was created by Dean Leffingwell – a successful entrepreneur and software development methodologist who has consulted to many companies, over years, including Rational Software, Rally Software, as well as many others.  Dean’s LinkedIn profile displays “Chief Methodologist” in the title.  LeSS was co-found by Craig Larman and Bas Vodde – both of whom are hands-on software developers, with many years (up until today) of experience, in large-scale, multi-site product development environments, including product companies, large telecom and investment banking.  Both co-founders have a lot of experience with organizational design and system modelling (a big part of LeSS).  Interestingly, Craig’s LinkedIn profile states “public safety, junior programmer” and Bas’s – “team member“.  The irony is in the modesty of their titles, since both co-founders have made a monumental investment in the industry, in the area of agile product development during the last few decades.

The initial release of SAFe program was in 2011, with five major release that followed.

Although, as an *official* framework, LeSS was announced only in 2015, its history goes back decades. The three Large Scale Scrum product development books were written in 2008, 2010 and 2016 years, respectively, with many field experiments collected over of the years, prior to 2008.  Essentially, LeSS has been a huge body of knowledge, collected over many years, before it became known as the framework.

 

Market Share, Framework Versioning and Certifications

SAFe is very widely known.  Its market share in the world of scaling is by far, the highest of all known frameworks.  Consultancy market is dominated by Certified SAFe Product Consultants (SPC) that hold, at least one, of many SAFe badges.  Because there are so many versions of SAFe (2.0, 4.0, 4.5, 4.6, 5.0), naturally, certification holders are driven to come back, for an upgrade training, to remain ‘up-to-date’.  Since SAFe supports a number roles that are aligned to traditional organizational roles, many SAFe courses are role-specific.  The number of instructors that can deliver SAFe courses is also high, with many course-reselling companies being actively involved in marketing, promotion and re-selling.

LeSS is not as widely known. Its market share, relatively to SAFe, is low.   There are only three main types of LeSS certifications (Basics, Practitioner and Executives),  with other few types, mainly, being on-line versions of the main ones.   LeSS training/certification is not ‘role-specific’.  LeSS adoptions are deep and narrow (as oppose to being broad & shallow).  According to field experts, there is no expectation that LeSS will become a mainstream in a foreseeable future.  This is because LeSS has high expectations for organizational design improvements (see below) that many companies are not yet ready for.  Today, there are very few LeSS trained/certified people because the number of accredited LeSS instructors is also relatively low (slightly over 20 people, globally).  LeSS, just like Scrum, does not have any versions.  There are two LeSS frameworks: [simple] LeSS framework (up to 8 teams) and LeSS Huge (stacks of LeSS, totaling hundreds or more people, if required).

 

Influence by Large Consultancies

Many large consultancies recommend SAFe to its clients, as a framework of choice (Note: As a corollary, many companies-clients, to officially remain framework-agnostic, adopt their own flavor of SAFe, essentially, using their own internal terminology, while mimicking/mapping to SAFe terminology, structure, etc).  For large consultancies, this ensures a more profitable and prolonged engagement, since SAFe implementation involves many people, processes and tools (see below).  Dave Snowden refers this type of engagement as an ‘industrial model’, since it ensures a “massive roll out, with lots of people, over a long period of time” (also, see this “Triple Taxation” illustration to understand a financial impact on companies-clients).  Another reason why SAFe happens to be a framework of choice by large consulting companies, is that the framework itself does not require any major changes to a traditional organization design and as such, does not put large consultancy representatives, in an uncomfortable position of purists-radicals that have to challenge their clients’ ways of working (not too much status quo challenging ensures a longer and more profitable engagement).

LeSS does not have much recognition by large consultancies for the following three suspected reasons: (1) organizational design of large consultancies [themselves] is inconsistent with LeSS teaching and therefore, there are no internal success stories to share with clients; 2) consultants don’t have enough LeSS adoption knowledge to comfortably support their clients with LeSS adoptions; 3) risk aversion, as stated above (fear to challenge radically, and therefore lose business), makes LeSS a bad choice.

 

Business Partnership with Tooling Companies

Today, almost any workflow management or bug tracking tool (e.g. VersionOne, Rally, VSTS/TFS, Jira, etc) is very closely aligned (some, also are strategically partnered) with SAFe.  This makes SAFe adoption especially convenient, since practically any large company today has one (sometimes, multiple) of the above mentioned tools in its arsenal, and considers them as a big part of agile transformation journey.   Practically, every tool that has the word *agile* in its name, also has a module/layer(s) that could be easily mapped (configured) to a multi-layered structure of SAFe.  This gives a sense of comfort to a company, about its own ‘agility fitness’, since now a company can conveniently fit its workload and organizational structure into a tool and framework.  This also creates great opportunities for SAFe and tooling companies to cross-sell and cross-promote each other.

LeSS is completely silent on what tools should be used to visualize work.  There are no strategic partnerships with tooling companies.  The only recommendation LeSS gives that whatever tooling is used, it should be very flat (simple) and easy to operate (e.g. no more than three levels of work decomposition; no commingling product and spring backlogs, etc).

 

Framework ‘Size’ and Traditional Organizational Design

SAFe involves many people, teams and departments.  One of the main reasons why so many organizations are comfortable to adopt SAFe is that it does not really challenge, a status quo of first-, mid-level management and traditional organizational design.  In one of his early-days webinars, recorded with VersionOne, Dean Leffingwell clearly stated: “…We don’t typically mess with your organizational structure because that is a pretty big deal…”. In SAFe, many traditional organizational layers (programs, portfolios) and roles (solutions architects, enterprise architects, various types of managers (project, program, portfolio, release, solutions, etc) have a place to exist.  SAFe provides a very safe environment for traditional managers: everyone has a role and some responsibilities. Notably, on a SAFe diagram, agile teams illustrated at the very the bottom of SAFe overall picture, with many management layers coming over the top.

LeSS product group consists of 2-8 teams (maximum 70 developers, assuming a maximum recommended number of developers in Scrum is nine), with a minimal number of additional roles involved (Product Owner, Scrum Masters, users, stakeholders).  LeSS Huge adoptions, with hundreds to thousands of people involved (they are gradual and take years) have a very minimal add-on to organizational complexity, in the form of [product] Requirement Areas, prioritized by Area Product Owners.

LeSS explicitly challenges traditional organizational design and calls for organization DE-scaling (flattening), as means of scaling agility and Scrum. In LeSS, a Team of developers is the key organizational building block.  In LeSS, middle and first-line managers are not requiredManagers in LeSS, if remain, radically change their focus from individuals and work-assignment management to capability-building and teams’ enablement.  In LeSS, programs and portfolios cease to exist.  LeSS is Scrum, applied to many teams, working together on one large product, and therefore, LeSS is best to use for product centric development, where a product centricity is really important (note: in LeSS a product could be a combination of software and hardware).

 

Team Structure and Coordination

SAFe includes various types of teams: agile teams, Kanban teams, XP teams and System teams, DevOps teams, architecture teams, etc.  In practice, these are single-functional specialty teams and component teams that are inherited from traditional organizational design and, therefore, still require a lot of additional coordination, integration of work and dependency management.  As such, there is a need for release managers (e.g. Release Train Engineers), Solutions Architects and other types of coordination managers – people that are responsible for bringing everything together.

In LeSS, all coordination between teams (each team is a cross-functional feature team) is done by teams, themselves (not even Scrum Masters).  Each team in LeSS is fully capable to deliver a product-centric backlog item (feature), from start to finish. In LeSS, teams are responsible for coordination and integration.  Dependencies in LeSS are viewed, as something highly undesirable (hard, asynchronous dependencies are viewed as a sign of organizational weakness), internal contracts (“us vs. you”) and unwillingness to work closely together – something that must be minimized, in favor of close collaboration among teams. In LeSS, a lot of emphasis is made on communication through code, mentorship, community learning and other lateral (horizontal) knowledge-sharing techniques.

 

Backlogs and Product Centricity

In SAFe, there are many different types of backlogs: team (private) backlogs, program backlogs, solution backlogs, portfolio backlogs etc. – each representing a respective organizational structure (people that are compartmentalized/departmentalized in their reporting verticals, ways of working and communication) and aligned with a specific team type, at various layers of the framework (e.g. , essential, program, solution, portfolio).  In order to keep all backlogs in sync and relevant, there is a lot of coordination and management required.

In LeSS, there is only one backlog: Product Backlog – shared by all (2-8) teams that work on the same, product, while servicing the same Product Owner.  As stated above, there are no programs or portfolios in LeSS – these traditional layers of WBS management are discontinued, in favor of a widened product definition.  There is a lot of direct coordination between teams in LeSS (intra- and cross-teams), by team members.

 

Product Ownership

SAFe Product Owner is a team member, who is responsible for defining/detailing and prioritizing team backlog items (frequently, component items).  SAFe PO can support, at most, 1 to 2 teams because focusing too much on details and tactical implementation requires a lot of time.  In practice, SAFe PO is often an ex-business analyst, ex-project manager or a tech-lead – something that works well, because majority of teams in SAFe are [technical] component teams.

LeSS Product Owner is conceptually the same as in one-team Scrum. However, in LeSS, PO focuses on an overall strategy and ensures maximum return on investment (ROI) in the product.  LeSS PO puts all of his/her focus on prioritization, whereas clarification, as much as possible, flows through users/stakeholders (see below).  In practice, LeSS PO is usually a product manager or a head of business operations (e.g. head of marketing, sales) – for external product development OR an experienced, hands-on individual from one of the major user departments, who is interested in taking on the role and is political savvy – for internal product development.

 

Proximity of Customers, Users and Stakeholders

In SAFe, it is less likely that business people will interact directly with developers, because there are specific, dedicated roles for such interaction. For example, Epic Owners (Portfolio level business people) interact directly with ART (Agile Release Team) / RTE (Release Train Engineers) and Solution Train / STE (Solution Train Engineers). Similarly, Business Owners (Essential SAFe level) that are responsible for governance and compliance, also interact with ART.

In LeSS, users and stakeholders are brought in direct contact with teams, and this is clearly defined in LeSS organizational design and rules of engagement, defined during initial (preparatory) phase of LeSS adoption (up to 2 months, prior to sprinting).  For the most part, all clarifications and details about product backlog items flow to teams directly from users and stakeholders.  In LeSS, there are no individuals or teams that are responsible for architecture only, solutions only or releases only – all these responsibilities reside within teams of LeSS Product Group, where all teams work on features, in a customer centric way.

 

Integration and Release Management

In SAFe, the System Team is responsible for development and maintenance of the toolchain that supports the Continuous Delivery Pipeline. It is also responsible for integration of code, produced by delivery (agile) teams.  ART (Agile Release Team), spearheaded by RTE (Release Train Engineer) – responsible for releases.

In LeSS, teams (2-8 teams in LeSS Product Group) share the same Definition of Done (DoD) and are responsible for their own integration and production deployment.  Teams make take turns, from sprint to sprint, in leading these activities, while closely coordinating with other teams and cross-pollinating each other with knowledge on how to do it successfully.  There are no full-time dedicated teams to handle these special activities only.  If there is any work that teams are not able to complete by Sprint-end, it is qualified as ‘Undone’ department work (highly undesirable) and is considered as an organizational impediment.

 

Agile Leadership and Frameworks

Usually, SAFe is the framework of choice, when an organization is not ready to make any major significant changes and where the following organizational facets are considered “untouchable”: a status quo of mid-level management, traditional budgeting, traditional portfolio structures (projects, programs), traditional HR norms and policies.  SAFe adoptions are typically spearheaded by traditional groups, such as PMO, CDO or a center of excellence. People that are in charge of action are best described by Larman’s Law or Organizational Behavior # 4 – individuals that have fast-tracked themselves into agile experts.  Adoption of SAFe is a very effective way to provide role safety to many traditional roles, that by minor updates to their titles will remain involved with the effort.

LeSS adoptions have chance to succeed in environments, where there is a real urgency to change, and where there is a strong need to bring real, tangible business value to real customers and users soon.  Usually, people that drive successful LeSS adoptions come from hands-on product development (technology) or from business operations (e.g. sales, marketing).  The should be also supported by by seasoned organizational design consultants, with years of experience of serving multiple organizations.  Prior to proceeding with LeSS, senior management needs to be educated on organizational design implications of LeSS and it must provide an informed consent (explicit agreement to provide support in action, not just in-spirit).

 

Conclusion

All models are wrong, but some are useful“. – George Fox.

It is probably impractical to debate which framework is best to use.  In order to decide on the best choice, we need to understand what strategic goals and objectives an organization wants to achieve:

SAFe can provide a top-down mandatory structure and control over an existing organizational disarray, without challenging significantly traditional roles, responsibilities, hierarchies (reporting and WBS) processes and tools. Most likely, organizational complexity, will not be simplified with SAFe, but it might be worth it if benefits of order out-weight expected complexity.   If an organization wants to do a major, large-scale roll out, involving thousands of people at once, and prefers a well-structured, change management process, based on play books, templates, prescriptive execution and compliance, then SAFe could be  a good  choice.

LeSS, just like Scrum, is based on empirical process control and contentious inspection, adaptation and experimentation.  If LeSS is adopted, with its minimal rules and guidelines, it can provide an array of deep systemic improvements but not every company might be ready to accept them.  LeSS would also require a significant change to a sphere of control by traditional roles, responsibilities, hierarchies, processes and tools (LeSS adoption principle #1).  LeSS will challenge a status quo of some people, and therefore, success of LeSS adoption is strongly dependent on support by senior management (LeSS adoption principle #2) that must ensure job safety and career opportunities for impacted people.  LeSS adoptions will not be fruitful if they are mandatory and based on compliance.  Instead, LeSS adoptions require a genuine commitment and are based on volunteering (LeSS adoption principle #3).  For example,  the oldest, biggest and most active global LeSS (NYC) Meetup is based on the principle of volunettering.  One of the most powerful tools (also an effective coaching tool) that is used in LeSS, is System Thinking – something that helps understand various aspects of organizational design (e.g. local optimization) that may not be otherwise obvious.

 

 

 

02/13-LeSS Talks: Co-Creator of Nexus (Richard Hundhausen) with LeSS Trainer (Greg Hutchings)

Shared Assets:

Additional Self-Study Assets:

Use of Velocity in Complex Organizational Settings

LeSS Scrum Master David Nielsen and I have discussed system dynamics in complex organizational settings, with respect to Velocity, produced by a single team and/or multiple teams.  We did only one cut (no dress rehearsals, dry runs or editing).
The following system variables were identified and their cause & effect relationship was ‘unpacked’:
  • Ability to use Velocity as a metric
  • Degree, to which combined velocity from multiple teams can be used as a measurement
  • Effectiveness of team’s estimation techniques
  • Likelihood that Customer/Product-centric development is valued, by business and the whole organization
  • Dependency on traditional organizational structure and protection of a status quo of component managers
  • Dependency on complex frameworks, processes
  • Degree of measurement dysfunction

As well as a few helpful proxy-variables to ‘glue’ the model together.

Download System Model (CLD)

Please, also refer to the following page on System Thinking, to make the best of the video and the model.

01/31 – LeSS Talks: Abusing Metrics for Dummies: How to manipulate data to make us look good?

Today’s  great presentation by Certified LeSS Trainer (CLT) from Israel – Elad Sofer. Please, contact Elad directly for an details.

Materials Used

Main points:
  • Data driven organizations are prone  to abusing metrics
  • The word agile has outgrown itself
  • The Observer Effect: the act of observing something, changes it
  • Metrics measurement: manipulates behavior
  • “Velocity is productivity metric” – against basic understanding of what -healthy organization looks like
  • Political metrics example: Transformation % progress
  • Vanity metrics example: # items that are in “dev done” status (but not tested)
  • Taiichi Ohno: “Don’t look with your eyes, look with your feet. A person who looks only at the numbers is worst of all
  • Example of four (4) metrics that count:
    • Deployment frequency
    • Lead time for changes
    • Time to restore service
    • Changes failure rate
  • Understand the difference between Leading and Lagging Metrics
  • Avoid measuring people: it is inefficient and disrespectful
  • OKR: Narrowing the gap between “O” AND “KR”

Additional Learning Assets: