The goal of any high-performing Agile organization is to constantly be improving their practices thru feedback and iteration.  The practices and behaviors recommended to achieve better Agile maturity are well understood—short cycles, feedback loops, product ownership, cross functional teams, co-location, test-driven development, Continuous Integration and Deployment, pair programming, and more.

In reality, however, we often wonder how well our teams are doing to implement these practices that we’re promoting so loudly. Exclaiming that automated deployments are a must, or that acceptance testing is required for “definition-of-done” to be achieved, is great, but when push comes to shove and deadlines are looming, what really happens?

In this session, we will introduce the Agile Maturity Model, an analytical method for capturing, analyzing, and presenting the vast amount of dark data that exist in our everyday SDLC tools.  Dark data is defined as “information assets that organizations collect…in the course of their regular business activity, but generally fail to use for other purposes.” (Gartner).  Our session will present:

  • The motivation behind and value derived from the Agile Maturity Model
  • How it was rolled out, and what challenges our teams had to overcome
  • Benefits achieved (so far), and path forward

With the Agile Maturity Model, Agile teams get a scaled view across any number of projects to predict how they are delivering vs. their goals, how performance is trending over time, and where teams might benefit from coaching.  With this model, Agile teams create a real-time feedback loop that helps them self-correct and tune performance at the team level, while also providing senior management with the information they need to govern the full portfolio of projects.

Any organization using standard SDLC tools for story tracking, test and defect management, build automation, deployments, code analysis, etc., can benefit from this model to help them track and improve their Agile performance.

 
 

Outline/Structure of the Experience Report

  • What is driving the need for Agile Maturity Model in IT organizations
  • How did we create the model
  • How it was rolled out
  • What challenges were faced
  • How teams overcame those challenges
  • What tangible benefits were achieved 
  • What is the path forward

Learning Outcome

Managers who attend this session will gain a better understand of how they could implement an Agile Maturity Model in their organizations

Target Audience

Technology Managers, Product Managers, Project Managers

schedule Submitted 4 years ago

Public Feedback


    • Scott Ambler
      keyboard_arrow_down

      Scott Ambler - The Disciplined Agile Enterprise: Harmonizing Agile and Lean

      45 Mins
      Keynote
      Advanced

      An agile enterprise increases value through effective execution and delivery in a timely and reactive manner. Such organizations do this by streamlining the flow of information, ideas, decision making, and work throughout the overall business process all the while improving the quality of the process and business outcomes.   This talk describes, step-by-step, how to evolve from today’s vision of agile software development to a truly disciplined agile enterprise. It argues for the need for a more disciplined approach to agile delivery that provides a solid foundation from which to scale. It then explores what it means to scale disciplined agile strategies tactically at the project/product level and strategically across your IT organization as a whole. Your disciplined agile IT strategy, along with a lean business strategy, are key enablers of a full-fledged disciplined agile enterprise. 

    • 480 Mins
      Workshop
      Beginner

      Disciplined Agile (DA) is an IT process decision framework for delivering sophisticated agile solutions in the enterprise. It builds on the existing proven practices from agile methods such as Scrum, Extreme Programming (XP), Lean software development, Unified Process, and Agile Modeling to include other aspects necessary for success in the enterprise. DA fills in the gaps left by mainstream methods by providing guidance on how to effectively plan and kickstart complex projects as well as how to apply a full lifecycle approach, with lightweight milestones, effective metrics, and agile governance.

      The one-day workshop is not technical and is suitable for all team members. Many group exercises reinforce the principles learned. The workshop is also valuable for management tasked with moving from traditional approaches to agile.

    • Pavel Dabrytski
      keyboard_arrow_down

      Pavel Dabrytski - Agile Economics: Contracts, Budgets, Capitalization

      Pavel Dabrytski
      Pavel Dabrytski
      Agile Coach
      Think Agile
      schedule 5 years ago
      Sold Out!
      45 Mins
      Talk
      Advanced

      How much does one story point cost? Is Sprint 0 an expense or an asset? Can you run Scrum with a fixed-cost contract? Agile challenges the existing approach to financial aspects of running projects: i.e. budgeting, forecasting, financial planning and vendor contracts.

      Applying new financial models becomes increasingly important for larger organisations adopting Agile. While they are going through an Agile transformation, they also need to maintain transparent financial governance and reporting. Shareholders would not be too excited about messy Annual Financial Statements.

      Join me if you would like to know more about Agile Economics. No financial degree is required and all the content explained in plain English with plenty of pictures!

    • Siraj Sirajuddin
      Siraj Sirajuddin
      Founder
      Temenos+Agility
      schedule 5 years ago
      Sold Out!
      45 Mins
      Workshop
      Advanced

      Enterprise Agile Transformation initiatives are BIG. Change at this scale of thousands is tough. 

      The Leaders and Executives involved in these initiatives are going through their own personal transformation. Change at this scale of one is equally tough. 

      Siraj Sirajuddin (SPCT) has worked with hundreds of executives leading enterprise agile transformation initiatives. These are their stories of personal growth and individuation. We will hear how transformation at a personal level is the leverage for transformation at a collective level. We will also learn of unique methods that activate personal transformation for leaders who are ready to step into their leader persona but are unable to get that from traditional leadership training and coaching methods.

    • Raji Bhamidipati
      keyboard_arrow_down

      Raji Bhamidipati - Remote working in an agile world

      45 Mins
      Talk
      Intermediate

      Remote working in an Agile world

       

      My experience of being a remote tester in an agile team

       

      Main statement:

      What does it mean to you/your colleagues/your company if you are a remote worker? How is it different to being an ‘office worker’? Let’s find out!

      Abstract

      Picture this!  – I landed a job with a company and team that I had wanted for a long time. Everything was going to plan until after about a year when I faced relocating to a far off land due to personal reasons. Imagine having to give up a job that you love and believe is going to be good for your career progression. Imagine working for a company that’s so awesome that, when I told them I had to move, they offered me the chance to become a full time remote worker!

      This was about 6 months ago and I have been a full time remote tester since then. I have learnt a lot during this time and want to share my experiences with you.

      Geographical limitations no longer stop people from working on awesome teams, or stop companies recruiting the right testers for the job. There are huge benefits for the remote worker and the company alike.  However, there are also drawbacks on both sides and remote working is not something to take lightly.

      At NewVoiceMedia we run a ‘Remote Working Community of Interest’ where we tackle some of the difficulties faced by remote workers as well as enjoy the benefits. To make remote working work there have to be changes made by the remote worker, the company and the colleagues who work in the office.  I want to present what these changes could be and could potentially mean to you, and your team.