DevOps & Agile • Digital Transformation • IT Strategy & Business Alignment • Leadership

Leveraging The Agile Manifesto for Digital Transformation

Leveraging The Agile Manifesto for Digital Transformation

This is an audio conversation from the CIO Talk Network podcast. The timestamps in the chapters and transcript below refer to the audio recording.

About this conversation

A CIO Talk Network conversation with Nicholas Colisto (Avery Dennison), Kevin Jones (Indiana Department of Child Services), hosted by Sanjog Aul.

What the conversation established

The conversation established that the two journeys should run together, with Colisto advising companies to define the digital ambition first and treat agile as the means to reach it, building muscle on proof of concept work before a large program. Both leaders framed agile as a tool, not the goal. Kevin Jones said a minimum viable product let his team turn a five year DDI into a two year delivery with three years of continuous improvement, and that failing early at the end of each sprint exposes wrong assumptions. He moved a team off a 23 year old mainframe to a Salesforce cloud using the ADKAR change model, running two major projects across eight scrum teams on SAFe. Colisto plans teams at 80 percent capacity rather than 100 percent, separates security and quality control from the project team, and measures value delivery, speed, and quality, including the percent of revenue from new digital sources and customer NPS.

Host Sanjog Aul talks with Nicholas Colisto, Vice President and Chief Information Officer at Avery Dennison, and Kevin Jones, Chief Information Officer at the Indiana Department of Child Services, about treating digital transformation and agile as one combined effort. Colisto argues for setting the digital ambition first and building agile practice on smaller, lower risk work before a large program. Kevin Jones describes making agile a requirement of his digital mandate and using a minimum viable product to shrink multi year delivery. They compare the SAFe and LeSS frameworks, the ADKAR change model, how to keep security and quality separate, and the metrics that show whether the work is paying off.

Contributors

  • Nicholas Colisto, Vice President and Chief Information Officer, Avery Dennison
  • Kevin Jones, Chief Information Officer, Indiana Department of Child Services

Host: Sanjog Aul, Founder and Host, CIO Talk Network

On this page: Key takeaways · Chapters · Explore more · Transcript

Key takeaways

  • Nicholas Colisto, Chief Information Officer of Avery Dennison, recommends defining the digital ambition first and treating agile as the means to reach it. He builds agile skill on smaller, lower risk proof of concept work so teams have muscle memory before taking on a large transformation.
  • Colisto of Avery Dennison argues that agile beats waterfall on large, capital intensive transformation because the work is broken into minimum viable products that deliver measurable value sooner. He fixes team capacity rather than scope and budget, which forces stakeholders to prioritize what matters.
  • Kevin Jones, Chief Information Officer of the Indiana Department of Child Services, says a minimum viable product let his team turn a five year DDI into a two year delivery followed by three years of continuous improvement. He treats failing early at the end of each sprint as the way to catch wrong assumptions and course correct.
  • Kevin Jones of the Indiana Department of Child Services used the ADKAR change model, awareness, desire, knowledge, ability, and reinforcement, to shift people off waterfall thinking before applying agile. He ran two major projects across eight scrum teams on SAFe while moving staff off a 23 year old mainframe to a Salesforce cloud.
  • Colisto of Avery Dennison keeps the security and quality control teams separate from the agile project team and tests for vulnerabilities and defects continuously, including SOC 2 compliance. He warns that functional complexity creates security problems, so teams should keep each feature as simple as possible.
  • Colisto of Avery Dennison measures an agile digital transformation in two buckets, value delivery such as the percent of revenue and margin from new digital sources and customer NPS, and team speed and quality such as on time delivery and defect counts. Kevin Jones of the Indiana Department of Child Services adds that the CIO must build empathy and learn the business well enough to act as a practitioner of it.

Chapters

  • 0:00 Introduction: pairing agile with digital transformation
  • 3:02 Define the digital ambition first
  • 6:02 Agile driven by the digital mandate
  • 8:53 The case for agile over waterfall
  • 11:50 Minimum viable product and failing early
  • 17:33 Shared operating model and frameworks
  • 21:36 ADKAR and changing how people think
  • 24:39 Locking in teams for resilience
  • 31:47 Retraining a mainframe team for agile
  • 37:15 Separating security and quality teams
  • 42:33 KPIs for value, speed, and quality
  • 45:00 Leadership muscle the CIO must build

Explore more

Transcript

Introduction: pairing agile with digital transformation 0:00

Sanjog Aul [00:00:24]:
Today’s topic is Leveraging The Agile Manifesto for Digital Transformation. So companies are trying to transform their organizations digitally, and they are doing so because they want to change their customer experience and build some competitive advantage and other things because of which someone will go digital, but then in parallel, in many cases, they’re also trying to bring agility into the organization and trying to adopt the agile principles, but wouldn’t it be cool if what you’re doing in the digital transformation space, it could also leverage the principles that were laid out in the agile manifesto, and it becomes an agile digital transformation initiative, but easier said than done, two different animals, two different constructs, two different types of changes we need to bring about. How do you do it? What would it take? What kind of collaboration, communication, political, and otherwise struggles that we might face before you could make this happen? To discuss this, I have with me, Nicholas Colisto, Vice President and Chief Information Officer with Avery Dennison.

Sanjog Aul [00:01:49]:
I also have Kevin Jones, who’s the Chief Information Officer with Indiana Department of Child Services.

Sanjog Aul [00:02:02]:
So, Nick, let’s start with you. So whenever we speak about digital transformation, it’s truly about a fundamental change that you wanna bring about in the way organization is designed and operates even down to the very business model, but then you talk about agility, which is more about how you were to make anything better, like, more collaborative, faster, flexible, and even self organizing. So both of them, if you look at individual initiatives, are very involved. They are also going to be, could be at times tedious or resource consuming. So would you say that since both all come almost every company can say we can use both. Should they even try to do both of them together or first do one and make that as a platform for the next to get the best outcome?

Define the digital ambition first 3:02

Nicholas Colisto [00:03:02]:
Yeah. My short answer is that the two journeys are really interrelated, and I think they should be done at least in parallel, but if I were given a choice, I would implement agile and agility practices first while helping the company to take a step back and define their digital ambition, and because I think agile is more of a means to an end. Right? So I would define that digital ambition first, and I think it might be helpful to pull a step back a bit and just kinda clarify some terms that we will probably be tossing around during this call. You mentioned digital transformation, and then to me it’s a, and I think just as we all know, it’s this type of journey that has the ambition of pursuing new net revenue streams, new products and services, which is different from digital business optimization. I’m kinda pointing this out because at Avery Dennison, we’re doing both as most companies are doing, but we have different practices in place to attack these, and with optimization, it’s about improving existing business models through productivity and revenue generation of existing products and services, the customer experience, those sort of things, even employee engagement. Agile leadership is about building teams that use agile principles in their processes to deliver these outcomes, whether it be optimization or transformation. Right? So it involves a clear vision, a culture of learning, shifting from a know it all culture to a learning culture, experiment lots of experimentation, adaptability, multidisciplinary teams, and I would even say a pioneering experience. So putting it all together, my recommendation would be for companies to step back, define their digital aspiration. Right? And you can do that by conducting workshops, which we’re doing a lot of these workshops around the world, as we continue to further our digital ambition, and at the same time, you can develop agile software development practices and employ it and apply those practices to smaller efforts, lower risk efforts, proof of concept experiments, and build some muscle memory. So you can exploit these capabilities across the teams as you take on the bigger challenge of transformation.

Sanjog Aul [00:05:13]:
Kevin, what have you seen? I’m sure in your work that you do at Indiana Department of Child Services or any other place where you worked in the past. What is more important or more so let me take a step back. So based on what Nick said, he said, okay, we have to have a transformational effort that should go in because it’s at the business level. We should dream that up and have a strategy in place, and when you try to execute, then you bring agile, but would you say, isn’t it too late? Because by that time, people are hard to try to go after digital, but they are not gonna be agile in the way they work or their agile muscle may not have been built. Would that in any way be counterproductive?

Agile driven by the digital mandate 6:02

Kevin Jones [00:06:02]:
I kinda agree with what Nick mentioned. I think that for us, our agile transformation was motivated by a requirement to do a digital transformation. So that motivation to do your overall transformation was there, and what we quickly understood and discovered was that, when you’re doing agile, and building systems, you also have the understanding of how do you get inputs from the business, and grabbing the inputs from the business requires that agility, and then also reconditioning the business to understand that the outputs are gonna come different than what they’ve come in the past. So it also requires a business unit to understand how agile products are delivered to them. So I think it does require this, a parallel type of process of implementing, and for us, what we had to do was to get our business to do that. They had to define that they were going to become a lean organization, and lean being our continuous improvement model, which is the agile perspective, and then getting us to align our people, process, and then our technology digital transformation together. So we did start with the people and process transformation of agile and then bringing in, at the same time, that digital transformation and a digital road map of collecting data and inputs and then delivering outputs to the business unit. So I do think that there is a chicken before the egg, and I do believe that you have to at least get the business ready mentally to consume and to provide agile inputs and outputs.

Sanjog Aul [00:07:47]:
So, Nick, you know, when you talk about business, and especially in digital transformation, the context or the business case that people try to put out there is, you know what? It’s gonna transform your business for good. You’re gonna generate new revenue streams. You might be able to shave some costs or whatever that’s gonna be money coming to the business, and everybody’s eyes open up and say, yeah. Let’s do that, and that journey could start, as soon as it’s possible, but then when you say to someone, well, whatever you’re doing, whether digital or not, we just want you to do things faster as if they did not have enough on their plate already. What’s the motivation for anyone to think about agile? And even if there seems to be a business case, a theoretical business case that you do something faster, that means your time to value is reduced, and your cost may be less, or people become more productive, but who wants to adopt it? Who wants to embrace speed, which will just make things worse for them as the day goes by? They have to get 20 things done versus 10.

The case for agile over waterfall 8:53

Nicholas Colisto [00:08:53]:
Yeah. I think it’s a great question because I think as you contemplate taking on digital business transformation, there is an incredible amount of risk that you’re taking on. Right? These are capital intensive programs for the most part. They’re very time consuming, require many resources across the organization, lots of coalition, cultural changes, third party providers. So think about all the risk you’re bringing on. Right? And then when you’re faced with those kind of challenges, Sanjog, your natural tendency might be to go with what you know. Go with the traditional waterfall project management. For traditional project management teams, they create these contracts where teams deliver exact requirements on a detailed schedule, where deliverables will generate a level of cost savings and incremental revenue, and once that project is funded, no one wants to admit, or talk about if any of those things aren’t happening perfectly. So there are many benefits to doing it differently with business transformation projects using agile. To make the case for agile with business transformation, I look at a couple of things. One is work is made easier to manage by breaking it into smaller chunks. You have these minimal viable products, and that reduces the big risky and costly failures that you can experience with waterfall on a large capital intensive business transformation project. Right? You also get measurable value sooner with Agile. Agile means that the costs are actually predictable. There’s more stakeholder engagement with Agile, and therefore, there’s more continued support across the sprints from other functions, and you can learn, you have time to learn and adapt to the changing conditions that are going on. The business doesn’t stand still while you’re doing these projects. So if you take on this waterfall approach, the business is changing along the way and you’re stuck. With Agile, you have these minimal viable products, you’re delivering through sprints, with the scrum teams, but you can adapt to changing conditions, and so with Agile, rather than having a fixed scope, budget, and timeline, Agile protects your having fixed capacity. If you have fixed capacity, you can only do so much with Agile. So that forces your stakeholders to really prioritize. So I think those are some of the benefits that I think of as I’m building a case for agile and using it more and more through the company. Those are the things that my team and I think about.

Sanjog Aul [00:11:33]:
So, Kevin, is there a law of diminishing returns when you start thinking agile and use that as a way into doing innovation in the context of digital transformation? Because once you’ve kinda squeezed the penny a little bit, how much more can you go?

Minimum viable product and failing early 11:50

Kevin Jones [00:11:50]:
I think Nick actually identified the term that actually addresses the diminishing return, which is the minimum viable product, and I think that is always the key for us. In my space, we have certifications, so we do have a minimum amount of requirements that we have to satisfy in order to call this solution ready for our production and our system of record. So identifying that minimal viable product to understand that at least this has to be done gives you the opportunity to say, hey. I’m gonna go from a 5 year DDI to this thing is 90 to 100% perfect to where I’m going to go to a 2 year DDI and a 2 year period in which I can have and consume that product, that shorter span that he mentioned to be able to say that I have a product ready and it meets and it supports my current continuity of business. And, oh, by the way, I can start using this system and apply my agile, my lean principles from a business practice perspective and continuously improve that thing to exactly what I want and not wait 3 additional years to get something that may not be what I need, and then get a level of understanding so that even if one of the things that you experience in many cases is over 5 years, your business practice changes. The market changes. The needs change. So you develop to this 5 year window, and you’ve had 3 to 4 years worth of change that you now have to go back and add additional capital and investment and opportunity cost to consume. Whereas you get that 2 year window, and those 3 years of continuous improvement are not only investment that you’re actually using, you’re improving the execution of your business and your business continuity, and for us, the other aspect that really came into play is failure early. That failure early enables you in large capital investment projects and DDI projects to understand where some of your assumptions were wrong, and you can quickly course correct those things and pivot points earlier in the project because you’re starting to see results. Even if you’re not seeing the full solution, you see results early. Like, at the end of every sprint, you have something to evaluate and say, yes. This is good, and no, it’s not. So that failure early, those quick pivot points, the minimal viable product that says that at least this is done and my consummated business satisfied, those are critical, and I do agree 100% with Nick on that.

Sanjog Aul [00:14:15]:
Let’s talk about the type of muscle an organization needs for agile transformation and digital transformation. They’re seemingly different, but then could there be an overlap, or could these people be going to the same gym, while building different muscles, but bring some common denominator so you are not keeping these two activities in silos with total overdependence on two different teams? How do you make that happen? How do you get these people to continue to cross train or continue to develop their muscles in such a way so that they can be interchangeable versus you having to have two teams for these two seemingly same project, but coming from different direction?

Sanjog Aul [00:16:56]:
So Nick, you talk about strategy or the type of team you need, or the different execution related consideration and criteria. What you need for digital transformation is not always, or maybe in most cases would be a little different than what you would do for agile transformation. It’s like two different sets of people building two different sets of muscles, but our goal is to bring them together. So could there be one gym? Could these people be cross training? Could we be building some of the common muscles so that we can get the best of both worlds and make it an agile digital transformation effort?

Shared operating model and frameworks 17:33

Nicholas Colisto [00:17:33]:
Yeah. I think there’s a strong connection, Sanjog, between what I would refer to as the operating model for digital transformation and the operating model for agile, and I think they share a lot of similarities or common denominators. If you think about transformation, you’re often thinking about products. Right? Agile was born out of software development and building products. There’s this adaptive business engagement when you think about agile, and when you think about business transformation and you’re weighing different aspects of transformation, again, always focus on trying to build out revenue. There’s lots of different ways of getting at that revenue. Business engagement is certainly key in helping to influence the minimal viable products you’re trying to achieve with agile. Continuous delivery is another core tenet of agile, and transformations don’t happen overnight. They’re not sprints in some cases, but they do take time to deliver the full suite of capabilities that you want as an organization. We have a number of businesses within Avery Dennison that are going through digital transformations. In some cases, we’re building products and we’re connecting products using our RFID technology as a good example. Other businesses, we’re tracking brand authentication to make sure that when someone buys a particular brand, that product is authentic, and that’s its own use case. It’s a product that we build and sell. That’s part of our transformation. So customer centric design, or in other words, design thinking, is something that’s really key within agile, but it’s also very important if you’re looking at it from a digital customer experience point of view with digital transformation. Design thinking is a fantastic tool. Application building blocks or platforms, another key tenet. So I think it’s important what’s also important is picking the right agile framework that matches your business digital transformation. I’m not really an expert in this. Maybe Kevin can add more, but I think that there’s differences between these different agile methodologies, these frameworks, and some don’t really work as well with the transformation you’re trying to bring on within your organization. I’ll give you an example. There’s one called SAFe, and they’re really designed for large scale projects, 50 to 125 members, based on these lean principles that Kevin referenced earlier, the systems thinking in there, building incremental value, minimal viable products, decentralizing decision thinking, organizing around the value, which is very different from the LeSS framework. We leverage LeSS in pockets within Avery Dennison. We don’t have one. We use a few, and as the name implies, it’s a scaled down version of the one-team scrum method, and it focuses the team members on one product at a time. So I think the key is that both business transformation and agile organize around developing products and services that deliver incremental business outcomes. With traditional IT, it’s really an all or nothing approach. That’s how I think about the two.

Sanjog Aul [00:21:03]:
So Kevin, when you are looking at the different frameworks that Nick mentioned, and at the same time, even though you get different frameworks, or maybe you find a common denominator among the frameworks, one for digital transformation, another for agile, but we are still dealing with humans here. Right? How well does a framework commonality translate into these people being able to wear two hats at one time or half of this and half of that?

ADKAR and changing how people think 21:36

Kevin Jones [00:21:36]:
Yes, Sanjog. I think you hit exactly where I was gonna go. I was waiting for you to get to that point, and I think you called it out. I being a classically trained complex systems engineer, I don’t look at agile as anything other than what Nick mentioned earlier. It is the tool. So the challenge with the transformation in general, just speaking from a digital and business transformation, we use a separate methodology, and what I used was the ADKAR model for transformation because people are the common denominator in a scenario. It doesn’t matter whether you’re engineer, whether you’re a business practitioner, or you’re developer. I have to transform your mind from thinking waterfall to this new way, and it means something different to each stakeholder. They have a different level of ownership and outcome that they’re looking for. So using the ADKAR model where the A is awareness, D is the desire to change, K is the knowledge that you need to change, A is the ability and the lack thereof to change, and R is the ability to reinforce and ensure one of the terms I know you like to use that stickiness that what is going to be there is gonna be retained, and it is sustainable. Those were the things that I focused in on to ensure that once I got my organization as a whole, not just my dev teams, but my organization as a whole, to overcome that level of effort and awareness, then we could implement the agility. We use SAFe on large projects. I have 2 major projects, 8 different scrum teams running together, and then we use a different methodology or model for our maintenance and operation and our continuous improvement on smaller business cases. So for us, the agile perspective was less of the hurdle, more so just getting us to the point where we’re ready to consume the digital transformation. Marrying the digital transformation, the operational change management, and the continuous improvement aspects of both of these things coming together was critical, and I think ADKAR helped us overcome that so we could get to what methodology and framework we would use in the agile perspective.

Sanjog Aul [00:23:52]:
So, Nick, what if people and leaders who are in some way connected to either of these initiatives move in and out, and that’s bound to happen, right? I mean, life goes on, and people leave in and out. Which of these initiatives are more resilient, or in other words, how do we bring resilience so that this flux that happens among people, and frankly, all these transformations are people driven, your process which has certain value frameworks which have certain value, but people are the ones who are embracing it, people are the one who are running with it. Which one should we focus on to make it more resilient so it carries the weight of the other, and it does not go under a sine curve as a transformation because people are going in and out of those groups or organizations?

Locking in teams for resilience 24:39

Nicholas Colisto [00:24:39]:
Yeah. With agile, you really want to lock up those resources. That’s part of the principles of agile: you have a dedicated team for a period of time to build out that work product, and I think that’s a real key part of agile. With transformation, we look at digital business and we group it. It might be important for me to kind of spell this out. I know you’re focusing more on transformation, but we also have digital optimization. So we have 4 digital experiences. I won’t go too long on this, I just want to give you a flavor. We have digital customer experience, which shouldn’t surprise anyone. These are the platforms that leverage a host of AI-based technologies and software as a service to help drive, improve our relationships with our customers and drive satisfaction. We have an employee engagement experience program, a factory experience program, and a product experience program. So all these are really important, and if I go across my business units, Sanjog, what I’ll find is there’s different people involved in these 4 experiences helping to drive value in each of these experiences. I have a COE where I have tower leaders across all 4, but the input that we get, the intake of work, and the thoughts on transformation and optimization come at us from all these different aspects of the organization. We did digital ideation sessions this past summer, and we had 419 ideas and had to add value across all 4 experiences, and then we’re driving that with digital transformation and optimization. I think in those categories, it’s okay to have different people coming in and out and giving thoughts. You certainly want to have a strategy. The strategy is important, but once that strategy is built out, those initiatives that power that strategy can come from different parts of the organization. You can’t control that. With agile, I think you have to have resilience in that when you lock and load on a project, maybe Kevin thinks differently, but when I lock and load on a project, I try to keep those people locked in, IT and non-IT people locked in that project to be part of those sprints. You can do 4 sprints, and then you do a 5th sprint and bring different people in, but I don’t like to change up the people too early on. I hope that answers what you were looking for there.

Sanjog Aul [00:27:05]:
No. Absolutely, and so, Kevin, what have you seen? What are the best way to keep these transformation projects not go under or not kind of go on a sine curve or a roller coaster ride because people are going in and out?

Kevin Jones [00:27:21]:
I agree with Nick 100%. I think continuity of business is consistent. You don’t want to ever have a perspective that’s driving to what your minimal viable product is gonna be changed, and you go in a completely different direction. One of the things we really focused on, and I know Nick mentioned this earlier as well, is really focusing on who has the bandwidth because these are long term projects and really understanding who’s gonna be there, and then you always have that risk associated with employee turnover and having that level of consistency. One of the things we’ve tried to do is really look at having that framework of critical thought, looking at the who, what, where, when, why, and how, and then looking at where’s our largest level of effort or the biggest gaps in those spaces that we need to capture, and drilling down in and capturing that information and making sure that we have that consistency, and then engaging. When you build your scrum teams, you have that consistency. One of the things I started to see is individuals start to learn each other. They learn how each other thinks. They can almost at the end of some of these projects and some of that trauma you go through with dealing with building and transformation, they can almost complete each other’s thoughts. So it gets to a point where having that level of consistency builds a consistent product and you know what to expect. So I think it’s very critical to ensure that those teams, when they start together, they finish together as best possible.

Sanjog Aul [00:28:50]:
Kevin, I would like to, again, come back to you and talk about a little bit of frustration and burnout, because, frankly, we are assuming that everyone who was there in the company, whether in IT or in business, they signed up for this roller coaster. Perhaps they did not, and then the people who always stay enthusiastic, want to learn new things, I’m not saying people don’t like to learn new things, but if it gets overbearing, or if it continually disrupts the way they do things, it could result in frustration and burnout. So we’ve got to take an average worker as well and not only the heroes. How do you prevent the frustration and burnout from happening when you’re trying to, on one hand, fundamentally shift the business because you want to do digital transformation, and then you tell the folks, we gotta do the same thing 2x or 3x time faster.

Sanjog Aul [00:31:33]:
So Kevin, move somebody from a cushy chair to a roller coaster chair and say it’s not gonna stop. How are you gonna handle frustration, burnout, and people totally losing it?

Retraining a mainframe team for agile 31:47

Kevin Jones [00:31:47]:
The challenge I had, and we experienced this, was we had systems that were 23 years old on mainframe, going from green screen technology to a Salesforce cloud based agile technology. Initially, when we put our team through the training, they were super excited about the concept, but taking that train concept and then putting it into applied knowledge and experience are two different things. One of the things I’ve experienced and continue to was with those individuals who had these trains of thought that they’ve honed and developed over 23 years. They’re used to having a deep dive in minutiae details. I had to retrain them to understand that the outcome is what you look at. You look at velocity. You don’t always look at what we would say, earned value management from work plan versus earn per se. You look at the velocity of the work plan versus what was earned, and then you look at what the end result of your minimum viable product is, and that gets you to the formula, that mathematics of is it good enough for who it’s for? Really helping them understand that you don’t have to micromanage those details as you would in waterfall. Why? Because you’re gonna have a pivot point. You’re gonna have a touch point where you can see it work. So if I can see it fail early, I don’t have to worry about every single detail because I won’t see it for 5 years. Once my teams got a chance to see everything that I taught them and everything that I told them work, in 1 month, they got to see the work that they planned, and they got to see the work executed, and then life goes on. You go to the next. So that experience is always that first hurdle. That first few road bumps is one of those things that they have to experience. So I don’t think there’s any magical training that you can give anyone outside of them taking it and applying it and experiencing it. You get that experience very early, so the risk is lower than it would be if you were in a waterfall environment.

Sanjog Aul [00:33:53]:
What have you done, Nick? Because, if you look at those folks who came there for a journey and they are not those heroes, do you think you can be pied piper for them who don’t want to follow you?

Nicholas Colisto [00:34:09]:
Yeah. I think there are a number of tactics you can employ to really avoid this sort of burnout with agile, many of which Kevin addressed. I think key is listening to the team and understanding, having huddles to find out what’s working well, what’s not working well, and then really invite them to help you solve it with them. I think it’s really important that you have that empathy, and you care deeply about what they’re experiencing, and you live it with them. Another thing I found is don’t plan capacity at 100%. Plan at 80%. The waterfall methodology, we’ve all used it for many years, we typically try to plan at 100%. With agile, we’re very purposeful in planning at 80% capacity. It’s also important to take breaks. There are so many releases with agile. Maybe have people work on some other assignments, then come back and work on the next sprint. That helps avoid burnout. I’m a big fan of Patrick Lencioni and he has some new work out there called the 6 Types of Working Genius. If you come across that or not, it’s fantastic. He has a podcast called At the Table. It’s just good practical advice for leaders and managers and everyone really. Why I bring that up in an agile conversation is it helps you figure out there’s a little aptitude test that you can take with your team. It helps you figure out for each person what each person is good at. It helps with self reflection and then applying them where they can really use those muscles on the project. That also helps avoid burnout. It brings some fun into the team. If your team is not laughing, we were laughing; I was working with my team this morning, we were joking. I had a background on Zoom with Bernie Sanders behind me. I couldn’t resist. It was a real kick out of it. I think it’s important to have fun and enjoy what you’re doing. I think it also helps to avoid that burnout, but it’s also important to look for indicators of burnout. There are indicators you should look out for, which we can come to, Sanjog, but there’s things to watch out for that might lead to burnout.

Sanjog Aul [00:36:45]:
So let’s talk about the security and business risks, which, of course, are inherent to any digital transformation because you’re fundamentally shifting to something new, but then, Nick, if you were to slap on agility on top, so you’re saying you’re going to create those holes into otherwise a secure fort, and you’re gonna do it much faster. So it’s just a suicidal approach when you look at it from a security and a business risk lens. How do you prevent that?

Separating security and quality teams 37:15

Nicholas Colisto [00:37:15]:
Yeah. I think it’s important to separate your security team from the Agile project team. They’re an extension of the team, but they’re not managed by the project manager. Same should be said around the quality control team as a separate team that’s assigned to the project but managed separately. In agile development, testing needs to happen early and also happens often. As Kevin said earlier, you’re gonna want to learn fast and fail fast. So you’re doing a lot of testing. Instead of waiting for development to be done before testing begins, you really want to test continuously through. I include security test where you want to test for security vulnerabilities as well as defects early on, unit, integration testing, and you’re also looking for vulnerabilities. Very important, and again, for transformation, typically you’re dealing with new products, things that you have not built before. Your company doesn’t have a lot of muscle on that. You’re also looking at some compliance like SOC 2 compliance. You might be building a digital product that requires SOC 2 compliance from your customers, that requires a lot of testing and a lot of documentation. So I think the last thing I would say on this is to avoid a lot of functional complexity, because functional complexity usually brings on security issues, so you want to focus on one feature at a time and just try to keep it as simple as possible, and again, bring in that security team, bring in that quality team very, very early and have good source code control.

Sanjog Aul [00:38:51]:
So, Kevin, Nick’s response is spot on when it comes to, you know, when you’re doing agile projects and how do you ensure security and digital like any other type of agile projects, but now if you were to put it in the digital transformation context, something entirely new, something in a totally different domain or rather something no one in the organization truly may have tried before. It’s almost like an innovation project. So the security and the business risk constraints are also not fully known, and there could be many other facets which we will uncover. They will reveal themselves, and then you’re trying to also introduce agility in there. What guardrails would you put so even though you’re going on that digital transformation, even though you try to push people or you try to push agility into that transformation effort, you would not derail yourself from a security and a business risk standpoint?

Kevin Jones [00:39:53]:
I think what I did and preached to my team was self-awareness. You have to be true with who you are. You also have to be true to who you are not. That led us to look at outsourcing to expertise who have done this type of work before, who can come in with a plan, with a product, with a roadmap and consume our architecture, our roadmap, and our plan, bridge the gap, and then bring my team in as a part of their DDI team. So we get that ingrained experience both hands on and working with that group, and then making sure that that knowledge transfer path is there. At the same time, separating the power, separating my quality control group, my PMO group, and my security group, and ensuring that they have the appropriate level of access and power. One of the things I did was also identify the gap and separate quality assurance and quality control, really separating that power so that my quality control can identify, is there a problem? Is there an issue? And then my quality assurance can do the evaluation and impact analysis to truly understand where there are challenges if there are challenges, even if there are circumstances that we didn’t plan for, the unknown unknowns. We understand what that unknown unknown has as an impact, and at the same time, my team is ensuring that they’re getting a chance during the capital investment so that when we get to an operational investment, the risk is low because we had that level of expertise brought in. My team is already sufficient in maintaining systems for 20 years. They get the ability to start to maintain these systems that they had a hand in developing. So basically, reducing our risk by bringing in expertise that we may not have and understanding that we don’t have it and being comfortable with consuming that and building that relationship so that we know what we’re doing and we know what we’re getting long term. It’s not just someone dropping a product off. We were there to understand and experience it.

Sanjog Aul [00:42:04]:
KPIs. Agile transformation or digital transformation, both could have their own respective KPIs if they were being kept as two separate projects, but here, we are dreaming an agile digital transformation. What would some of the KPIs look like, Nick, which would form a solid foundation for someone to use as benchmarks? Because what we improve or what we measure is what we improve, and what we improve is what gets us to the success milestone.

KPIs for value, speed, and quality 42:33

Nicholas Colisto [00:42:33]:
Yeah. I think it’s helpful to categorize metrics, and I can simplify by thinking of really two categories relative to agile and digital transformation. First, what are the things to measure with stakeholders? The answer in my mind is value delivery. That would be the first bucket of metrics. The other bucket of metrics would be around what are the key things to measure about teams. This is where you’re getting at agile, which is speed and quality. Those are the buckets I think about when I think about metrics relative to this question. Value delivery metrics are around the % of revenue from new digital sources. This is all about transformation. The % of net margin from new digital sources, the % of interactions that are digital, the marketing spend that’s now digital. The speed to market, these are really critical business impact metrics, business satisfaction, the customer NPS score, and internal satisfaction as well, particularly with optimization. For teams, we think about speed and quality: the % of projects delivered on time, average release time, delivering on scope, delivering on budget, reciprocity from stakeholders. Are they giving you what you need to be successful with them? We measure our partnership with surveys to measure how well we perform with our stakeholders and how well they perform with us, and of course, number of defects around quality, average time of defect resolution. Those are things that come to mind around measuring digital transformation and measuring agile.

Sanjog Aul [00:44:38]:
One last question for you, Kevin. If you had to build brand new leadership muscle, which would make you even more effective than what you have been so far in dealing with digital transformation and agile transformation, so that you can deliver an agile digital transformation? What would those muscles be?

Leadership muscle the CIO must build 45:00

Kevin Jones [00:45:00]:
Those muscles for me primarily focus around understanding the business, understanding the need, and echoing some of the things that Nick just mentioned, the continuity of the business and being able to understand the impact that you have on the organization. It requires one of the things I think is real critical and key, and Nick mentioned earlier as well, empathy. Being able to put yourself in the situation of the business so that when you’re in the conversation and you’re driving and you’re on behalf of some business units, you’re making those decisions because you’re in a rapid development, rapid deployment solution. You have to be able to understand the business. So for our CIO, it requires you to step out of that technical space, become water, and enter into the space of being the business practitioner, being your COO, understanding what his challenges are, understanding what every decision, every impact, every change, every situational awareness information that you can consume, how it impacts the outcome of your organization. I think it is critical. So you have to transition from being a technical person to a business person, to a financial leader, to an operational leader, and really look at, am I increasing the time to produce, or am I reducing the time to produce? For me, it was critical for me as a CIO to come in, and I learned how to be a practitioner for child welfare, how to be a practitioner for child support, and what that means to the business and how my systems impact. That was really critical for me to even think about how I can produce a successful digital transformation that impacts my overall organization.

Contributors

Nicholas Colisto

Nicholas Colisto, Vice President and Chief Information Officer, Avery Dennison

In his role, Mr. Colisto is responsible for driving and executing an enterprise IT strategy for the company, including shepherding the overall company strategy with respect to information technology trends, driving efficiencies across the o... More   View all posts
Kevin Jones

Kevin Jones, Chief Information Officer, Indiana Department of Child Services

Kevin serves as Chief Information Officer and is responsible for providing innovative and transformative solutions to all business process needs, divisional leadership and managing both CAPEX AND OPEX for the divisions of Production, PMO, I... More   View all posts

Advertisement

TECHM - GENAI - MPU04 - 300x300
Nicholas Colisto