• Skip to main content
  • Skip to footer

InRhythm

Your partners in accelerated digital transformation

  • Who We Are
  • Our Work
  • Practices & Products
  • Learning & Growth
  • Culture & Careers
  • Blog
  • Contact Us

inrhythm

Dec 20 2019

3 Themes of Thanksgiving to Apply Everyday


The Simple, Rapid Test That Every Agile Team Should be Doing

A couple of weeks ago, I shared some thoughts around the concept of leading a team of agile craftsmen and how all of us were practitioners in a living lab. Agile product development, by definition, requires that we fail fast, learn from our mistakes and develop processes that maximize efficiency. Agile values also require that we put the emphasis on people ahead of the process.


That sounds incongruous. How do you do both in parallel? It seems like it would be impossible to put people first yet adhere to the rigor required by following a process. However, there is a way. It’s called the Agile Litmus Test. Although there is no standardized template for it, the basic concept is that each team member thinks about why s/he/they is doing what they’re doing towards the goal of assessing whether or not the individual, team or corporate effort meets the values and principles as defined by the Agile Manifesto.

Many of you may recall the litmus test from your chemistry classes. The Litmus Test is a simple, low-tech, low-cost way of determining the pH (acidity) of a given solution. It’s been around for centuries and it’s still in use today both as a physical test as well as a metaphor for describing a quick method for testing out a concept. The fact that it’s been around so long illustrates how effective it is which, in turn, underscores the value of the Agile Litmus Test. One thing that surprised me is how search results returned for this test seem to drop off after 2015 – have agile developers lost sight of its importance?

Within the context of agile product development, the Agile Litmus Test is a rapid means of straddling the duality of putting people ahead of the process  (Agile Value #1) yet still adhering to it. There are several versions of what it should be, but there are only a few basic rules regarding the application of the Agile Litmus Test. In short, keep asking yourself if you’re doing the right thing. Given that we’re all agile craftsmen, we should be encouraged to use a little latitude to make the “rules” work for each of us given our own scenarios. At InRhythm, we apply it to meet our needs.

Quite simply, the Agile Litmus Test is the act of asking practical, meaningful questions to assess our priorities. Which questions you ask and which order you ask them in are not critical. What is critical is that you ask some flavor of these questions regarding everything that you do. It’s less about the rigor of the questions asked and more about accepting the personal responsibility of asking them. Whatever you’re doing, which includes posting on social media, writing content, coding, documenting, how you conduct yourself at a meeting and what you say there, etc. should all be subjected to the Agile Litmus Test. 

Consider questions along the following lines:

  • Why am I doing X this way?
  • How is doing X going to help me meet my goal(s)?
  • Should I be doing X right now?
  • Is there something else that I should be doing instead of X?
  • How will my team or project be impacted if I do X?

The idea is to self-assign a mental speedbump, not a big hurdle. You want that little bump to be big enough to get noticed but small enough to accelerate through. Take the time to pause and think about what you’re doing and why you’re doing it. Each of our actions as agile software engineers who are part of high velocity teams has consequences for us as individuals, as a team, as a client and as a vendor. We need to consider the bigger picture for all that we do and not gloss over our own accountability for using our time in a way that advances our personal and professional goals. 

In my years of experience onsite at clients and working with 10x teams, I’ve seen people get caught up in their own agendas. Somehow, they lose track of the bigger picture or their leaders have not communicated it effectively to them. Regardless of how or why it happened, they are not invested in how their efforts tie into the collective efforts of the project. So, you’re thinking, well, if one individual has lost sight of the vision and the shared end-goal, that’s probably not going to have an effect on the overall outcome. Or, if you’re that individual, you may be thinking the same thing. 

Not so, because there is rarely just one individual on an agile project that loses sight of the priorities. Typically, it’s more than one which can have dire consequences on hitting the milestones and timeline that only some people are tracking to. If you were to apply the Agile Litmus Test right now, what is the question that you ask yourself?

Thanks and Keep Growing,

Gunjan Doshi

CEO, InRhythm

What We’re Reading Around the Web

16 Quick Poll – a Litmus Test for Agile Product Development
Scrum Breakfast
“I want a litmus test, i.e. a short list of questions for challenging developers and their managers on their engineering practices.”

How to Test for Agility with the Agile Litmus Test
Dummies
“To be agile, you need to be able to ask, ‘Is this agile?’”

Taking the Agile Litmus Test
O’Reilly Safari
“When you understand these values and principles, you’ll be able to ask, “Is this agile?” and be confident in your answer.”

The Principles of Agile Manifesto
Educba
“Collectively, these principles are used to like a litmus test to identify if a project is being run on agile or not.”


Written by Gunjan Doshi · Categorized: Agile & Lean, Culture, Employee Engagement, Learning and Development, Talent · Tagged: 10x teams, agile, gunjan doshi, high performance culture, inrhythm, learning and growth, management consulting, newsletter, organizational assessments, performance, process

Dec 03 2019

Customers are Much, Much More Than Signed Contracts


December 3rd: Customer Collaboration Over Contract Negotiation

Like most things, how you see something is a matter of perspective. The lens that you look through is shaped by experience, environment, who you’re influenced by and the attitude you take towards life and the given topic in particular.

Applying a customer-centric lens to branding, product development and marketing seems like an obvious thing to do, however, it wasn’t until the 1960s when Lester Wunderman urged companies to do so. Moreover, it wasn’t until the turn of the last century when customers took control with their collective new ability to dictate a brand’s narrative via the internet and dawn of social media. So, this concept of customer-centricity, in practice, is actually a modern way of thinking.

“Agile Value #3: customer collaboration over contract negotiation” is an example of a customer-centric approach. However, the core component of the directive is essentially the same. It’s all about communication.

That doesn’t mean unilateral outreach where you as the brand are sending messages, postcards, coupons or holiday catalogues. What it does mean is creating a forum for open dialogue in the spirit of true communication where conversations are bilateral. Doing so ensures that pain points can be discussed until they are understood and then resolved.

As agile product developers, the responsibility of maintaining a health dialogue with our customers is up to us. All too often, I have heard software engineers citing that communication with a client is the responsibility of the sales and marketing team. Not so!

We’re the people who are typically onsite with the customer. It is up to us as the agile craftsmen to deliver our best work to our clients so that their light can shine brightly. Clients look to us as their trusted advisors who are there to help them meet their needs, deliver quality work on time and help ensure our client’s success with their customers. Losing sight of the value of wearing a customer-centric lens compromises our ability to deliver our best for our clients. As soon as we we make it about ourselves and not our clients, the work environment will become more challenging and potentially even toxic.

The concept of collaboration over contract negotiations delineates the difference of being regarded as a vendor versus as a partner. Here at InRhythm, we know which side we aim to be on. Approaching software engineering with agile methodology requires that we are constantly communicating with our clients, assessing their needs and anticipating their needs even before our clients realize that things have shifted.

This brings us back to perspective. If we communicate regularly, with transparency, and deliver quality work in a timely manner, our clients will view us with the lens of partnership. Conversely, if we view our clients with the lens of a signed contract and the dollars tied to it, our perspective will be tarnished. As software engineers, we will struggle to deliver our work with that passion and quality that is required to fulfill the demands of an agile effort.

Agile Value #3 is the reminder for all of us that the lens that we view our work with is critically important. Viewing our deliverables and efforts with a client-centric perspective will positively impact how they view us. And, it can make all the difference between doing business versus being out of business.

Thanks and Keep Growing,

Gunjan Doshi

CEO, InRhythm

What We’re Reading Around the Web

The Real ROI Of Being Customer-Centric
Entrepreneur
“No business will survive long without satisfying its customers. That much should be evident to any company whether it is established or just starting out.”

100 Of The Most Customer-Centric Companies
Forbes
“Customer-centric companies live and breathe their customers and are laser-focused on providing amazing experiences.”

Customer Centricity — Marketing as customer-centric corporate management
Medium
“[The] key to success: a more radical focus on humans. Genuine customer centricity requires to rethink all functions and levels.”

6 Ways to Build a Customer-Centric Culture
Harvard Business Review
“To successfully implement a customer-centric strategy and operating model, a company must have a culture that aligns with them — and leaders who deliberately cultivate the necessary mindset and values in their employees.”


Written by Gunjan Doshi · Categorized: Customer, InRhythm News, interviewing, Newsletters · Tagged: agile, CEO, coaching, customer-centric, engineering, gunjan doshi, inrhythm, insights, networking, product development, software, tech, tips

Nov 19 2019

The Importance of Placing Individuals Above Processes and Tools

Empathy should be regarded as a super-power. Not enough people have it and the workplace – indeed, the entire world – would be a better place if more people did have it. When you have project deadlines or you’re in the midst of an intense all-hands scrum, it’s easy to forget about the people factor. That is, there are people working with you and for you who are missing celebrations, concerts or the opportunity to just chill out at home because their effort is critical to your product development effort.

But you’re on a tight timeline. You have key deliverables. Your client has worked backwards from the launch and expects that you will deliver a bug-free software solution by the date circled on the calendar. As the Practice Lead, you may be luckier than most in your role if you have a dedicated team cranked up on caffeine and working late into the evening – every evening, in fact. This is great for deadlines but it can have far-reaching negative consequences if this pace is expected to  be sustained.

The Agile Value #1 requires that we value individuals and interactions over processes and tools. Yet you’re conflicted. Project deadlines and deliverables are what they are and you’ve explained them to your team. Missing a due date and delaying a launch is not going to happen on your watch. Processes for coding, testing, documenting must happen as prescribed, regardless of the yeoman’s effort required to get it done. Your team understands this, right? Surely you told each team member that they were doing great work when you met last year for their performance review?

Maybe they do. Or maybe they don’t. Agile product development places enormous demands on the people doing the work. Both the team members and their practice leads have to grapple with the relentless pressure and the temptation to skip part of the process to move things along faster. 

When you’re building high velocity teams, you need to make daily investments in your people, processes and infrastructure. Take any and every opportunity to express empathy, understanding and gratitude for the work that your team, and each individual on your team, is doing. Expressing appreciation once per year during a performance review will likely end up becoming a one-and-done experience because that employee likely won’t be around this time next year.

There are simple ways to bolster your team’s productivity and motivate them to stay on track with respect to processes. The easiest way is to say, “Thank you.” If you want a high velocity team who is loyal, dedicated to the needs of your customers and proud of the work they do, then say what you mean and mean what you say. Be sincere. 

To help ensure that your agile engineers remain “your” agile engineers, go one step further and acknowledge the efforts of individuals in front of others. People are human and their efforts, sacrifices and basic needs must be openly acknowledged. As software engineers in a hot market, we have the flexibility to go wherever we like towards the goal of being part of a community that values our membership. Agile leaders must reinforce appreciation of these “extra efforts” through grace, gratitude and occasionally, through special dispensation. Catering dinner (that’s not pizza) for the team every once in a while is a good expression of gratitude. This is how to build trust and long-term relationships, as well as high velocity, agile teams. 

Staying strong on execution and adhering to process is critical for success. Acknowledging the personal efforts that it took to enable that success must be acknowledged. Remember, as per agile Value #1 –  if you put people first, ahead of processes and tools, you will have created a space that fosters a high performing team’s success.

Written by InRhythm · Categorized: Agile & Lean, Culture, Employee Engagement, Learning and Development, Software Engineering, Web Engineering · Tagged: agile, coaching, engineering, hiring, inrhythm, insights, networking, recruiting, software, tech, tips

Nov 19 2019

Simple Test for Every Agile Team


November 19th: The Simple, Rapid Test That Every Agile Team Should be Doing

A couple of weeks ago, I shared some thoughts around the concept of leading a team of agile craftsmen and how all of us were practitioners in a living lab. Agile product development, by definition, requires that we fail fast, learn from our mistakes and develop processes that maximize efficiency. Agile values also require that we put the emphasis on people ahead of process.


That sounds incongruous. How do you do both in parallel? It seems like it would be impossible to put people first yet adhere to the rigor required by following a process. However, there is a way. It’s called the Agile Litmus Test. Although there is no standardized template for it, the basic concept is that each team member thinks about why s/he/they is doing what they’re doing towards the goal of assessing whether or not the individual, team or corporate effort meets the values and principles as defined by the Agile Manifesto.

Many of you may recall the litmus test from your chemistry classes. The Litmus Test is a simple, low-tech, low-cost way of determining the pH (acidity) of a given solution. It’s been around for centuries and it’s still in use today both as a physical test as well as a metaphor for describing a quick method for testing out a concept. The fact that it’s been around so long illustrates how effective it is which, in turn, underscores the value of the Agile Litmus Test. One thing that surprised me is how search results returned for this test seem to drop off after 2015 – have agile developers lost sight of its importance?

Within the context of agile product development, the Agile Litmus Test is a rapid means of straddling the duality of putting people ahead of process  (Agile Value #1) yet still adhering to it. There are several versions of what it should be, but there are only a few basic rules regarding the application of the Agile Litmus Test. In short, keep asking yourself if you’re doing the right thing. Given that we’re all agile craftsmen, we should be encouraged to use a little latitude to make the “rules” work for each of us given our own scenarios. At InRhythm, we apply it to meet our needs.

Quite simply, the Agile Litmus Test is the act of asking practical, meaningful questions to assess our priorities. Which questions you ask and which order you ask them in are not critical. What is critical is that you ask some flavor of these questions regarding everything that you do. It’s less about the rigor of the questions asked and more about accepting the personal responsibility of asking them. Whatever you’re doing, which includes posting on social media, writing content, coding, documenting, how you conduct yourself at a meeting and what you say there, etc. should all be subjected to the Agile Litmus Test. 

Consider questions along the following lines:

  • Why am I doing X this way?
  • How is doing X going to help me meet my goal(s)?
  • Should I be doing X right now?
  • Is there something else that I should be doing instead of X?
  • How will my team or project be impacted if I do X?

The idea is to self-assign a mental speedbump, not a big hurdle. You want that little bump to be big enough to get noticed but small enough to accelerate through. Take the time to pause and think about what you’re doing and why you’re doing it. Each of our actions as agile software engineers who are part of high velocity teams has consequences for us as individuals, as a team, as a client and as a vendor. We need to consider the bigger picture for all that we do and not gloss over our own accountability for using our time in a way that advances our personal and professional goals. 

In my years of experience onsite at clients and working with 10x teams, I’ve seen people get caught up in their own agendas. Somehow, they lose track of the bigger picture or their leaders have not communicated it effectively to them. Regardless of how or why it happened, they are not invested in how their efforts tie into the collective efforts of the project. So, you’re thinking, well, if one individual has lost sight of the vision and the shared end-goal, that’s probably not going to have an effect on the overall outcome. Or, if you’re that individual, you may be thinking the same thing. 

Not so, because there is rarely just one individual on an agile project that loses sight of the priorities. Typically, it’s more than one which can have dire consequences on hitting the milestones and timeline that only some people are tracking to. If you were to apply the Agile Litmus Test right now, what is the question that you ask yourself?

Thanks and Keep Growing,

Gunjan Doshi

CEO, InRhythm

What We’re Reading Around the Web

16 Quick Poll – a Litmus Test for Agile Product Development
Scrum Breakfast
“I want a litmus test, i.e. a short list of questions for challenging developers and their managers on their engineering practices.”

How to Test for Agility with the Agile Litmus Test
Dummies
“To be agile, you need to be able to ask, ‘Is this agile?’”

Taking the Agile Litmus Test
O’Reilly Safari
“When you understand these values and principles, you’ll be able to ask, “Is this agile?” and be confident in your answer.”

The Principles of Agile Manifesto
Educba
“Collectively, these principles are used to like a litmus test to identify if a project is being run on agile or not.”


Written by Gunjan Doshi · Categorized: Agile & Lean, Culture, Employee Engagement, Learning and Development, Talent · Tagged: 10x teams, agile, gunjan doshi, high performance culture, inrhythm, learning and growth, management consulting, newsletter, organizational assessments, performance, process

Nov 14 2019

Say Thank You Now: Don’t Wait for Employee Appreciation Day


November 13th: Say Thank You Now: Don’t Wait for Employee Appreciation Day

Having a dedicated holiday or annual occasion to formally celebrate someone sounds like a good idea on the surface, however, it doesn’t reflect the first value of agile product development. Why do we need to wait for a special day to tell someone that we appreciate them for who they are, for what they do and how they impact our lives? In fact, it seems a little disingenuous to share a message or token of appreciation on that given day because society obligates us to do so.

Let’s turn this around and refocus on the first value of agile methodology. We need to routinely take a moment to pause and communicate our appreciation. “Value 1 = individuals and interactions over processes and tools.” We could just as easily add “… over formalized events or occasions or annual performance reviews.” What this agile value is essentially saying is that expressing appreciation, gratitude or human decency and kindness to another human doesn’t have to be prescriptive. Instead, it’s quite the opposite. It should flow freely, be a natural expression and happen in the moment. 

When you’re building high velocity teams, you need to make daily investments in your people, processes and infrastructure. Waiting for a full 364 days or 90 days (or whatever your performance review cadence is) to tell someone that they are doing a good job and that you sincerely applaud and value all their late nights and extra effort is too long to wait. Telling them how valuable they are to your company and client as often as they deserve to be told (without being overly expressive as that has a similar negative outcome through the dilution of the message) is the best way to bolster your team. 

Do you want a high velocity team who is loyal, dedicated to the needs of your customers and proud of the work they do? I’m sure that you do. And, assuming that you do want your agile craftsmen to remain “your” agile craftsmen, then go one step further and acknowledge that person’s efforts in front of others.

The pace of software development is best described like that multi-movie franchise, “Fast and Furious.” It can be relentless. Many projects are inherently complex requiring sophisticated engineering. As if that wasn’t already challenging enough, layered on top of the work itself are the difficulties associated with logistics, managing international and remote teams, coordinating individual efforts, and keeping your teams motivated. These factors compound the burden carried by practice leads and executives. 

Just as the agile value mandates, we must put people ahead of processes and tools. The ones doing the work are human. They have human needs: they want to be with their families, spouses, and friends. Missing a night out or birthday or some other event can be tough, but manageable if it’s once in a while. However, repeatedly missing every social outing with friends and family month after month during an extended project sprint is not going to have a positive outcome. Nor will missing even one of the “big rocks” milestones like a graduation or wedding. These losses will have lasting repercussions on employee morale and taint corporate culture.

People are human. We need to belong and we long to be part of a community that values our membership. Agile leaders must reinforce appreciation of these “extra efforts” through grace, gratitude and occasionally, through special dispensation. This is how to build trusted and long-term relationships, as well as high velocity, agile teams. 

Leaders of agile craftsmen, particularly of those who are placed onsite at a client and disconnected from the “mothership HQ” must take time to pause and recognize the importance of showing appreciation. Yes, these sprints are fast and furious but they will never be successful if you don’t show your people that you care. Not to mention how one sprint flows into another, then another, and then the epic wraps up as another begins. As a leader, you must also impress upon your clients who are hosting your agile craftsmen that they also express appreciation for a job well done. Doing so fosters a sense of community and helps the onsite workers feel like they belong and are playing a valuable role alongside the client’s employees.

Staying strong on execution and adhering to process is critical for success. Yet there must be time deliberately factored in to pause, however briefly, to recognize the efforts of one individual at a time. In so doing, it won’t be long before everyone has been recognized for their contribution and be made to feel that they are indeed, an important part of a special community. Remember, as per agile Value #1 –  if you put people first, ahead of processes and tools, you will have a high velocity 10x team.

Thanks and Keep Growing,

Gunjan Doshi

CEO, InRhythm

What We’re Reading Around the Web

10 Creative Ways to Show Employees Appreciation
Business News Daily
“There’s no better time of year to brush up on your employee appreciation best practices than right now.”

The Importance of Saying “Thank You” in the Workplace
Forbes
“In fact, companies that spend a mere 1% of their payroll budget on thanking and recognizing their employees ‘are more likely to perceive greater impacts on retention and financial outcomes.’”

If Bosses Want Happier Employees, Start by Saying “Tank You”
CNBC
“In fact, 75% of U.S. employees surveyed agreed that motivation and company morale would improve if managers simply thanked workers in real-time for a job well done.”

16 Best Practices for Conducting Employee Reviews
PrimePay
“Be sure to highlight good performance and explain why it was good and how it helped the team and the company as a whole. Recognition is key in making your employees feel valued for the hard work they put in.”

The Employer’s Guide for Boosting Employee Retention with Recognition
Workest
“One study polled over 1,500 workers, finding more than half were considering a job move. When asked what would motivate them to stay with their employer, 69% said recognition and rewards.”


Written by Gunjan Doshi · Categorized: Culture, Employee Engagement, Talent · Tagged: 10x teams, agile, gunjan doshi, high performance culture, inrhythm, learning and growth, management consulting, newsletter, organizational assessments, performance, process

  • « Go to Previous Page
  • Go to page 1
  • Go to page 2
  • Go to page 3
  • Go to Next Page »

Footer

Interested in learning more?
Connect with Us
InRhythm

140 Broadway
Suite 2270
New York, NY 10005

1 800 683 7813
get@inrhythm.com

Copyright © 2022 · InRhythm on Genesis Framework · WordPress · Log in

This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish. Cookie settingsACCEPT
Privacy & Cookies Policy

Privacy Overview

This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Non-necessary
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.
SAVE & ACCEPT