Search

Agile Adoption: Should It Be Data-Centric At All Levels Of The Organization?

Introduction to Data-centric Agile TransformationsTeams and Organizations adopt Agile to bring in the changes- faster turnaround, better results, quick reviews, dynamic teams.The mindset change that is constantly talked about in Agile is still challenging to fathom because no one really knows how much of a change it is. Yet, the philosophy seems nice to look at- people over tools, working software over documentation- yes everyone needs it.While teams get structured, work is re-evaluated, Scrum masters trained and Agile coaches hired, everyone knows change is coming. 66 days is what it takes for any change to happen… and no matter what your role is, this is tough on everybody.Data, as it happens, is so underused in Agile transformations that it needs a book by itself. Data-centric approach to Agile methodology can be used to inspire, create gamification models to encourage team dynamics as well as create a monitoring mechanism to help convince stakeholders that things are moving.So, let’s look at these categories and see how data can be mapped.IntrospectData is neutral and yet has the ability to create an environment of positivity. Used correctly (both qualitative and quantitative) in the early stages, it can help us understand and build the environment. The following points can help you introspect as a team as well as individually.The Happiness Index- On a scale of 1-5, rate your team on how happy you are working with them and give a reason for it. Done anonymously in team retros or just randomly is stand-ups, this brings out anger, conflicts, and reasoning in a completely different way. However, beware this works only when this is conducted by a third party (like an Agile coach/facilitator). The score, of course, stays for further comparisons in the future (you can do it release wise, yearly etc). It makes everyone open up; however at the same time realize their opinions matter or someone is listening. You can find the points that get repeated and connect with the right person who can get it resolved.Find Your Team Mate- In this scenario, ask your team to anonymously write one quality about themselves that no one’s know about (not related to work). Now take those sticky notes and put it up on a wall. On the other column write the name of the team members- now ask the team to match the quality with the name. This is an amazing exercise for any team whether the dynamics are good or bad, new team or seasoned team, co-located or distributed.The reason it works so well is, in our everyday mad rush at work, we often forget to appreciate each other as humans and focus on the skills and getting the work done. We don’t even know who we work with anymore. This exercise is always eagerly participated and the results astonish team members themselves. It gives introverts and extroverts the same playing field and helps teammates understand how to motivate each other.MotivateMotivation is essential in any Agile team and yet this is an overlooked category in transformations. We know from Harvard Business Review that happy teams take up more complex challenges (https://hbr.org/2013/04/to-find-happiness-at-work-tap). So, what data can be looked at to ensure teams are intrinsically challenged?1) Publish Case Studies- Publishing case studies of successful teams with adequate data might be a wonderful information radiator of teams that truly motivate others.2) Team Reports- For retrospections, using the available team data can bring insights which are otherwise difficult to trace. Team reports can start at a basic level and track:1. User Story Committed vs Delivered2. Team velocity3. Sprint Burn DownUnderstanding what they have done and where things could have been improved under the guidance of an able manager, should inspire teams to perform better in the next sprint.3) Value Stream Mapping- Look at the entire cycle flow for a sprint with your team, take the waste out, make changes to your practice, keep tracking, talking and changing till you think the process is completely yours.4) Defect Reports- While looking at what went wrong or missed isn’t always motivating in the short run, seeing and ensuring a root-cause analysis is done and changing the strategy accordingly and reducing the account definitely is a mood booster for teams.5) Velocity Charts- Another way of looking at what has been delivered in terms of complexities over a period of time and if the chart differs way too much, the reasoning behind when and in what condition more complexity was delivered. The dips could be because of holidays or new joiners or attrition rates.CamaraderieA happy team is a productive team. Conflicts and egos are added complexities that are best resolved immediately.Retrospective- Seeing what the trend has been as a team and if the action items are being resolved should improve the team dynamics to continuously strive to improve. Track the action items to the positive changes made in the team and publish the data. Or alternatively, find the trend and see where usually the blockers are, this set of data while can be used fantastically by the team it can also be used by the manager or the coach, who when implementing for another team will use strategies to ensure the same trend doesn’t surface.Kudo Cards- Recognitions from team members would be a wonderful feeling for anyone, tracking them over releases or yearly on what someone is doing to help can create team appraisals and not individual ones.To summarize, data is always your ally, nudging and pushing you towards the right direction. Data isn’t just for management/stakeholder reports which it’s usually thought out to be, it should be embraced with equal inquisitiveness by teams and coaches and anyone who is remotely really trying to understand how transformation happens and how teams and individuals react to it.Data-centric Agile transformations shouldn’t just be e-mails sent out by management, it should be about thinking deeply about what it entails, what might change, the reality, and the expectations.

Agile Adoption: Should It Be Data-Centric At All Levels Of The Organization?

298
Agile Adoption: Should It Be Data-Centric At All Levels Of The Organization?

Introduction to Data-centric Agile Transformations

Teams and Organizations adopt Agile to bring in the changes- faster turnaround, better results, quick reviews, dynamic teams.

The mindset change that is constantly talked about in Agile is still challenging to fathom because no one really knows how much of a change it is. Yet, the philosophy seems nice to look at- people over tools, working software over documentation- yes everyone needs it.

While teams get structured, work is re-evaluated, Scrum masters trained and Agile coaches hired, everyone knows change is coming. 66 days is what it takes for any change to happen… and no matter what your role is, this is tough on everybody.

Data, as it happens, is so underused in Agile transformations that it needs a book by itself. Data-centric approach to Agile methodology can be used to inspire, create gamification models to encourage team dynamics as well as create a monitoring mechanism to help convince stakeholders that things are moving.
















So, let’s look at these categories and see how data can be mapped.

Introspect

Data is neutral and yet has the ability to create an environment of positivity. Used correctly (both qualitative and quantitative) in the early stages, it can help us understand and build the environment. The following points can help you introspect as a team as well as individually.

The Happiness Index- On a scale of 1-5, rate your team on how happy you are working with them and give a reason for it. Done anonymously in team retros or just randomly is stand-ups, this brings out anger, conflicts, and reasoning in a completely different way. However, beware this works only when this is conducted by a third party (like an Agile coach/facilitator). The score, of course, stays for further comparisons in the future (you can do it release wise, yearly etc). It makes everyone open up; however at the same time realize their opinions matter or someone is listening. You can find the points that get repeated and connect with the right person who can get it resolved.

Find Your Team Mate- In this scenario, ask your team to anonymously write one quality about themselves that no one’s know about (not related to work). Now take those sticky notes and put it up on a wall. On the other column write the name of the team members- now ask the team to match the quality with the name. This is an amazing exercise for any team whether the dynamics are good or bad, new team or seasoned team, co-located or distributed.

The reason it works so well is, in our everyday mad rush at work, we often forget to appreciate each other as humans and focus on the skills and getting the work done. We don’t even know who we work with anymore. This exercise is always eagerly participated and the results astonish team members themselves. It gives introverts and extroverts the same playing field and helps teammates understand how to motivate each other.

Motivate

Motivation is essential in any Agile team and yet this is an overlooked category in transformations. We know from Harvard Business Review that happy teams take up more complex challenges (https://hbr.org/2013/04/to-find-happiness-at-work-tap). So, what data can be looked at to ensure teams are intrinsically challenged?
1) Publish Case Studies- Publishing case studies of successful teams with adequate data might be a wonderful information radiator of teams that truly motivate others.

2) Team Reports- For retrospections, using the available team data can bring insights which are otherwise difficult to trace. Team reports can start at a basic level and track:

1. User Story Committed vs Delivered
2. Team velocity
3. Sprint Burn Down

Understanding what they have done and where things could have been improved under the guidance of an able manager, should inspire teams to perform better in the next sprint.

3) Value Stream Mapping- Look at the entire cycle flow for a sprint with your team, take the waste out, make changes to your practice, keep tracking, talking and changing till you think the process is completely yours.

4) Defect Reports- While looking at what went wrong or missed isn’t always motivating in the short run, seeing and ensuring a root-cause analysis is done and changing the strategy accordingly and reducing the account definitely is a mood booster for teams.

5) Velocity Charts- Another way of looking at what has been delivered in terms of complexities over a period of time and if the chart differs way too much, the reasoning behind when and in what condition more complexity was delivered. The dips could be because of holidays or new joiners or attrition rates.

Camaraderie

A happy team is a productive team. Conflicts and egos are added complexities that are best resolved immediately.

Retrospective- Seeing what the trend has been as a team and if the action items are being resolved should improve the team dynamics to continuously strive to improve. Track the action items to the positive changes made in the team and publish the data. Or alternatively, find the trend and see where usually the blockers are, this set of data while can be used fantastically by the team it can also be used by the manager or the coach, who when implementing for another team will use strategies to ensure the same trend doesn’t surface.

Kudo Cards- Recognitions from team members would be a wonderful feeling for anyone, tracking them over releases or yearly on what someone is doing to help can create team appraisals and not individual ones.

To summarize, data is always your ally, nudging and pushing you towards the right direction. Data isn’t just for management/stakeholder reports which it’s usually thought out to be, it should be embraced with equal inquisitiveness by teams and coaches and anyone who is remotely really trying to understand how transformation happens and how teams and individuals react to it.

Data-centric Agile transformations shouldn’t just be e-mails sent out by management, it should be about thinking deeply about what it entails, what might change, the reality, and the expectations.

Soma

Soma Bhattacharya

Blog Author

Soma Bhattacharya is an Agile Coach working out of Hyderabad (India). When not at work, she can be found reading (non fiction), running her blog www.steppingintopm.com, planning her next big project and exploring life

Join the Discussion

Your email address will not be published. Required fields are marked *

Suggested Blogs

Combination Of Agile & DevOps – The Roots

Agile and DevOps are two notions that originate from the same schools of thought, but whose paths now have digressed. However, a major amount of confusion still remains within the IT services industry with regards to the relationship between the two and has emerging agile & devops trends in 2017. Hence, it is of value to look at the origins of each and to clarify the disparities between them. ‘Tell me what you want, what you really really want!!’ Does the tune ring a bell? Back in the 1990s, the Spice Girls were expressing to the world what they really really wanted, and similarly business owners and corporate leaders were doing pretty much the same, indicating what they wanted to software developers who were working on enabling these organizations through technology. Unfortunately, these business owners were not as lucky as the Spice Girls. More often than not they really didn’t get what they wanted. By the time business requirements were properly understood, validated and finally realized through software products the business requirements more or less had changed.  This was mainly due to the ‘application delivery lag time period’ that sometimes went up to three years. The result of the aforementioned delay from concept to realization meant that a large proportion of projects were stopped before completion. Even then, those that eventually reached the finish line more often than not did not meet the end users’ expectations.  The introduction of Agile – The change-driven management approach The search was on for a more lightweight approach to solution delivery and the result was ‘agile’ – a project management approach with a series of new concepts with regards to collaboration between business owners and the implementation team including UI / UX engineers, developers and even QA engineers. Instead of eliciting, documenting and signing off all the requirements up front and getting it signed off before work began, the focus shifted to delivering value through increments of functional software that would evolve over time. The results indicated that the software implementation team had become more productive, businesses could be more responsive in responding to queries of the implementation team, and user demands could be met more efficiently. However, problems remained. The agile approach didn’t always deliver on the promise of continuous, seamless software development. Blockers continued to exist. So, what is DevOps? The first thing to note is the fact that DevOps is not an individual tool or a suite of solutions but more of a philosophy whose primary purpose is to reduce the distance between the worlds of software development and IT operations. It defines how the original concepts of agile have moved downstream to the level of infrastructure and operations. The DevOps concept sounds relatively straightforward, but in reality it is a little bit more complicated. Software development and IT operations have historically had very different approaches. Software developers appreciate the ability to change things quickly and often they do end up changing things rapidly. In the meantime IT operators focus on stability and on minimizing alteration. This philosophical disparity has often resulted in conflicts. Thus, one of the main challenges of DevOps is to ensure that this conflict decreases before it affects the businesses. Importance of DevOps Principles For this very reason indicated above, it is very important to consider and act up on the core principles of DevOps. They are, Close collaboration and communication between developers, system operators and software testers Continuous integration that requires developers and operators to commit to changes more frequently Continuous delivery to increase the team’s speed and efficiency while enabling early detection of bugs Continuous deployment to ensure new developments can be released without system downtime The DevOps philosophy goes hand-in-hand with the delivery processes described in ITIL Framework in terms of support and IT services management. DevOps can therefore be seen as a way to implement ITIL processes in such a manner that meets the demands placed on systems today.  
3326
Combination Of Agile & DevOps – The Roots

Agile and DevOps are two notions that originate fr... Read More

Metrics that matters for DevOps Success

DevOps is generally introduced for the development teams to speed up the software delivery. DevOps is considered as a step beyond Agile. Many enterprises accepted DevOps as a part of software delivery process from planning, developing, deploying and updating an application, according to reviews. In this competitive world, DevOps allows businesses to speed up with the rapid pace of demands by the customers.Here are the top Ways to Obtaining Business Benefits of DevOps. Customers of today demand quality as well as security based products. DevOps, making the best use of its principles, provides superior quality and lowers the risk. On the contrary, in traditional software development approach, increased speed often results in poor quality and increased vulnerabilities. Why are metrics essential? Most organizations implement DevOps because of the demand for quality, time improvement and the need for defect-free products. Since DevOps has no specified framework, there exist a few standard ways to measure DevOps success. How do you find out how well it can work? How will you come to know whether it is working or not? The answer to this question, and the solution to all the existing problems, is the use of Metrics. Metrics are essential to stay in sync with DevOps. DevOps will be used extensively which therefore requires continuous treatment. But if you are not measuring its outcomes, you cannot understand how to incorporate DevOps in your organization. The focus of DevOps metrics is on deployment, operations, and support (feedback). Let us have a look at the Devops metrics which will lead to improved delivery performances. People: People are the major elements of the DevOps process. People-oriented metrics measure the things like yielding, capacity and response time. People are the hardest element of DevOps. So always start with the phase ‘People’. Process: In some ways, DevOps is considered as a process of  continuous deployment. There are many process-oriented metrics. Development to deployment is a large process-oriented metrics. Process metrics can be the measurement of speed, appropriateness and effectiveness. Technology: Technology metrics also plays a major role in DevOps. It measures the things like uptime (time during which the computer performs operations), network and support, and failure rate. Deployment (or Change) Frequency: DevOps metrics includes continuous deployment. Updated software deployment in every few days can be possible with fast feedback and piecemeal development. In a DevOps environment, deployment frequency can be measured in terms of the response time, the teamwork, the developer capacities, development tools and the overall efficiency. Change Lead Time: Change lead time is the time period between the initialization phase to the deployment phase. In DevOps, it is a measure of development process efficiency, code and the development systems’ complexity, and also of team capabilities. A protracted ‘change lead time’ is an indicator of an inefficient deployment system. Change Failure Rate: One of the main goals of DevOps is to do frequent deployment with less failure rates. Failure rates metrics should be decreased over time, as the experience and the capabilities of the team and developers get increased. If the frequency of failure is very high, it is definitely a red flag, as it gives rise to problems in the overall DevOps process. Mean Time to Recover: Time taken between ‘recovering the failure’ from the ‘failure’ is known as Mean Time to Recover (MTTR). It can be fragmented into three phases- detection, diagnosis and recovery phases. MTTR metrics is the sign of a good teamwork which identifies how effectively the teams handle the changes, and also, how collaboratively they do so. By all means, this metric is becoming a trend for DevOps to remodel organizational processes in a better way.
Metrics that matters for DevOps Success

DevOps is generally introduced for the development... Read More

Agile and DevOps Or Agile vs DevOps: Differences

Agile is the standard in today’s application development world. Development teams are adopting it over the last 10 years, as it has been proved to be more efficient methodology of getting quality software. Agile has improved user experience by frequently rewarding with focussed goals and quick delivery. In addition to this, the broad use of DevOps in Agile methodology has made it a more compelling approach for IT commercials. In this context, it is important to know that Agile is not DevOps, and DevOps is not Agile. It is difficult to achieve success in DevOps, if Agile practices are not followed. While Agile can make sense independent of DevOps, it can be more complete when accompanied by DevOps practices.Here are the emerging Agile and DevOps Trends. Many people have set their minds about Agile, that Agile means Scrum and DevOps means continuous delivery. This simplification creates unnecessary confusion between Agile and DevOps, making people think that they are perfectly compatible. So, let us have a look at the practical connections between Agile and DevOps. Planning for Unplanned work: In the DevOps circle, those using Agile acknowledges that Scrum is used to track the planned work. Tasks like releasing updated system, performing system upgrades etc, can be planned. On the other hand, the operations like performance spikes, system expiry, and standard security, can be unplanned. These types of tasks need immediate response. You cannot wait for the next sprint planning session. For this reason, many organizations embrace DevOps (more than Scrum and Kanban), which helps to track both kinds of work. Before, there were priorities from multiple masters, but now a single set of priorities are in use. Similarly, for a long list of assigned work, the time period is planned to accomplish the work. These lightweight management practices by Scrum make a huge difference for a team. Speed vs Risk: Teams using Agile with or without DevOps have to remember that, to support the rapid change, a sound application structure and a solid foundation are mandatory. Applications must have good underlying framework that must be used constantly by the team members. In the DevOps context, the teams must make sure that the changes which are made to the architecture should not introduce any risk. Also, there should not be any hidden side-effects associated with the changes, because the iterative process consists of regular changes in the architecture. So you should be concerned about the risks associated with each and every change made. Only with this type of work will you get rapid delivery without any risk. Agile and Quality: Both Agile and DevOps help develop an application fast, keeping sound structure and risk-free application.  But neither of them concentrates on the quality of the product. Mostly, IT organizations rely on the ‘fail fast’ principle- “ Early failures cost less to fix”. But with this, only fast deployments can be maintained, not quality. Agile produces applications that fit better with the desired requirements and can adapt quickly to respond to the requirement changes made on time, during the project life. DevOps, along with the automation and early bug removal, contributes to creating better quality. Developers must follow Coding and Architectural best practices to  embed quality in the applications. Agile and DevOps should try reach the next level to become highly effective within the organizations. They must conform to the industry standards using Agile and DevOps practices, to allow the development team to improve quality, make delivery faster and avoid software risks.
1443
Agile and DevOps Or Agile vs DevOps: Differences

Agile is the standard in today’s application dev... Read More

Useful links