Speaker: Ryan
As the pressure to deliver value in an ever changing landscape continues to accelerate, IT organizations and in particular software engineers are being ask to do more/different work than ever before.
And whether your organization delivers as the speed of a rabbit, a horse, or an elephant, you can drive an agile transformation to build a team that is capable of rising to the occasion.
Speaker: Ryan
At Accenture we typical group applications in to one of three large buckets, rabbits, horses and elephants. These applications are grouped by both their deployment cadence, but also the amount of tech debt, type of people and business value.
Each type of application has a different release cycle, each one has the ability to apply agile concepts.
Speaker: Ryan
Many enterprises have undertaken an agile transformation journey, with full internalizing the benefits that agile hopes to drive. They are doing agile because everyone else is doing agile. By keep the benefits of agile in mind, this can ensure that you are driving the right behavior
Speaker: Ryan
Speaker: Ryan
Speaker: Ryan
Speaker: Chida
Notes: Make sure you add in your real life examples
Circle of Control is very important especially for the ‘Teams’ as they stay motivated and engaged. In our Columbus Innovation Hub we are following this religiously where the team members are focused on TDD, upskilling themselves consistently. Our Product Managers are putting together smaller stories, leaner product and emphasizing the befits of these to client to seek rapid feedback.
I’ve seen the change first hand. For example in my last engagement, we had little to no automation except CI, our stories were big as the PMs were not focused on leaner product. It led to very little motivation in the team towards delivery. People were focused on getting things done rather than delivering value. And now in my current engagement where the client is big-time ‘Waterfall’ Enterprise, we as a ‘Team’ are focused on what we can do to deliver value consistently. We have smaller stories that would be built and functionally tested on average in a day following TDD, BDD practices and show the results every week to all the stakeholders even though the broader organization still follows waterfall.
Speaker: Chida
Notes: Make sure you add in your real life examples
As we have smaller stories Product Owners can gauge the value better and we’re able to change client’s point of view to look at the product delivery. They get a sense of product and are able course-correct their asks. This has led to build trust in the team. The team has more confidence as we focus more on Continuous Integration and Deployment. Team members are owning development, unit test, automated functional tests for their assigned stories. They are becoming better software engineers rather than ‘Developers’ or ‘Testers’. Team members are pairing so we have collective ownership of the product and in turn save time on code reviews.
Speaker: Ryan
Notes: Make sure you add in your real life examples
Speaker: Both
Notes: Make sure you add in your real life examples