Sorry, no proposals found under this section.
  • Ravi Krishnan
    Ravi Krishnan
    schedule 3 years ago
    Sold Out!
    45 mins
    Experience Report

    Organizations which have diverse functional units and technology portfolios (BI, Mobile, Web Application development, Web Design etc) following different methods cannot make an overnight or a sudden transformation to following a mature model of Agile method.

    These teams need to come up with a structured approach towards Agile adoption and transformation enabling the different teams to make a gradual progression towards the adoption of Agile in their projects and teams.

    We at Aditi Technologies realized this and came up with a Aditi Agile Transformation Maturity Model which provides guidance to the different project teams and functional groups on the transformation journey within their engagement. The salient points of the Maturity model include:

    * Agile Project Planning and Management Maturity Model - Traditional teams are used to tradition planning methods plan around the typical 3 constraints of Scope, Cost and Time. A transformation to a model where emphasis is on delivering the highest priority items is arguably one of the more difficult lifecycle areas of the transformation. The Agile Project Planning and Management maturity model provides guidance to such teams on moving from a managed team services model to a self directed and self managing teams services model.

    * Collaboration Maturity Model - Moving from a SLA driven environment to a collaborative environment is again a massive cultural mindset change for the different teams. The collaboration maturity model at Aditi for Agile engagements provides a framework for teams to start collaborating better in a gradual manner. Starting with a well defined collaboration model within the Agile sprints between the QA and Development teams leading to an end to end collaborative lifecycle involving the different stakeholders is the overall approach we have adopted at Aditi to improve the Collaboration within the lifecycle in a phase wise manner.

    * Agile Requirements Engineering Maturity Model - The Aditi AREMM provides the business and product ownership teams with a gradual migration approach from the traditional Business Requirements Document based Requirements Management approach to an Agile approach towards the same incorporating basic principles like story card based requirements engineering to a more collaborative and leaner approach incorporating starting principles such as Product Backlog and Story Cards and moving to more advanced models such as executable specification models prescribed by BDD.

    * Engineering Maturity Model - While there are well prescribed best practices and models within the Engineering phase for Agile teams, adopting an all at once approach can be fraught with danger for the teams especially given the constraints of a global delivery model such as staffing pyramid (practitioners at different levels of capability including graduate hire resources), the Engineering maturity model provides teams with a prescriptive model around adoption starting with relatively basic principles like refactoring to adoption of more advanced practices like TDD, BDD etc.  

    * Metrics - Based on the level of the maturity of the Agile adoption, Aditi has come up with prescription around metrics the teams could adopt. These are classified into different buckets using the MoSCoW prioritization principles.

    * Tooling - Aditi has come up with a well prescribed guideline for Agile teams in the adoption of tools across the lifecycle (Ex: for Collaborative lifecycle management, Continuous Integration, Build management, Code quality management etc) and has come up with bootstrap assets which teams can leverage to run with when they start the transformation.

    * Organization readiness - For an organization to embrace Agile, many of the current internal practices (Recruitment, Sales etc) and current infrastructure (Ex: Collaboration platforms, infrastructure) needs to scale up as well. A well defined maturity model towards transformation allows organizations to adopt a more phase wise approach towards these areas of transformation and helps the different business units to also scale up at a sustainable pace.

Sorry, no proposals found under this section.