Agile Vendor Management Manifesto

Want to discuss and share the Manifesto which a group of coaches including myself have written.

Please refer to www.vendormanagementmanifesto.org for details

1.1 The Governance
The delivery team is governed by contracts. There are 2 types of contract we will be considering
•The Master Contract : This is a contract signed between the Customer and Supplier Management teams and governs the entire set of Scrum projects being executed.
•The individual work order level contracts: This is a contract which will govern the detailed work to be done by teams.

This manifesto will take into account both the type of contract

1.2 The Roles
The roles covered under this Manifesto are as follows
The Customer Management This is the management team of the customer
The Vendor Management Team Vendor Management team will work on behalf of the Customer Management team in preparing the contract and negotiating the same with the Supplier’s management
The Team The team will consist of multiple Scrum teams working on the projects governed under the Master Contract. They will end up working under the individual Work Orders signed up with the customer.
The Supplier Management The Supplier Management team will negotiate the terms and conditions of the Master Contract of the contract along with the The Customer Management team (and the Vendor Management team).

1.3 The Objective of this Manifesto

The Objective of this Manifesto is to define guiding principles around the Customer-Supplier working environment with regards to working on Scrum projects. The assumptions made are
•The environment is customer-supplier (i.e. an outsourced environment)
•The environment is distributed and may not be co-located
•The environment involves multiple vendors

The Customers and Suppliers are integrated elements of a working environment in a project. The Customers and Suppliers will work together with a common goal and that is “Producing Value for the End Customer”. This manifesto supports the Agile Manifesto Value “Customer Collaboration over Contract Negotiation”.

There are 12 principles which will support the Agile Value and are presented below in a format of Left over Right. The items on the left are valued more than the ones on the right.

 
5 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

3 The Twelve Principles

3.1 Risk Sharing over Risk Transfer

The Customer Management and Supplier Management should own the risk collectively to create a joint ownership.

3.2 Featured Based Payments over Milestone Based

Payments are based on Business value i.e. payments are made when features are completed or released or when Business Value is delivered).

3.3 Outcome Based Productivity over Utilization Based

Productivity should be measured in the Scrum Projects. However, the contract should propose productivity measures based on the business value generated vs the utilization of the resources.

3.4 Team Based Ownership over Management Based

Commitments in a contract should be endorsed by the teams. The contracts should support the endorsement of teams for the work to be executed by the teams.

3.5 One Team over Partnership

Culture of one team one vision will lead to a long-lasting relationship and create a win-win for the Customer and Supplier.

3.6 Long Term Relationships over Fungible Contracts

Considering Profit, Stability and Business Value as 3 pillars for a Customer-Supplier relationship to provide business value, it is important to have long-term commitments that leads to more ownerships and alignment to the vision of the Customer.

3.7 End to End Contracts over Horizontal Contracts

Contracts should be made based on Products/Feature Based Deliverables (Vertical Slice or end-to-end) over activity/skill-based based contract (Horizontal slice e.g. Development, Testing, Acceptance etc)

Customer Management mindset must facilitate cross-functional (Vertical Slice) contracts.

3.8 Focus on Products over Activities

Focus on product delivery rather than on delivering activities.

3.9 Business KPI over Operational KPI (Key Performance Indicators)

Focus on Business KPI over Operational KPI will give opportunity to bring down the cost of correction thus increasing the value yielded by the organization.

3.10 Transparency over Bureaucracy

Transparent Culture between Customer and Supplier will facilitate collaboration and reduction in escalation and bureaucracy.

3.11 Respond over React

Contracts Governance should enable alignment between customer and Supplier Management so that potential escalations are responded at the earliest.

3.12 Contingency in Scope over Contingency in Time and Cost

Contracts should enable high-priority changes to be incorporated even late in the delivery cycle without increasing the time and cost of the project.

Please refer to http://www.vendormanagementmanifesto.org/

Learning Outcome

Mindset required when thinking of contracts with vendors

Target Audience

executives, Managers Leaders who are working in a Vendor -Customer environment

Prerequisite

working in an environment where contracts are made for service engagement in IT

schedule Submitted 2 weeks ago

Comments Subscribe to Comments

comment Comment on this Proposal

  • 20 Mins
    Talk
    Intermediate

    Story is a profoundly important device to unite design teams around a shared product vision. This powerful communication tool helps us retain information and empathize with others. As companies scale and teams sprint through product iterations, it’s easy to lose sight of how your product should fit into the lives of your customers. The best way to keep everyone pointed in the right direction is with a clear, compelling story—a story that will unite and guide teams towards success.

    But how do we fold storytelling into our design practice? Aarron Walter uses real-world stories of product teams at Disney, Apple, Airbnb, Twitter, and more to show how storytelling improves team communications and elevates design practice.

  • Liked Suresh Konduru
    keyboard_arrow_down

    Suresh Konduru - How Agile is your legacy financial organisation?

    45 Mins
    Case Study
    Beginner

    Legacy financial organisations (viz. BFSI – Banking, Financial Services and Insurance enterprises) operate in a regulatory and high-risk environment. This session discusses some of the organisational dysfunctions such companies experience during their Agile transformational journey.

    The session will help you understand and empathize with such dysfunctions and some possible mitigation patterns. Sample dysfunctions below:

    • There are multiple middle management layers which are redundant and mostly resistant to change.
    • Huge upfront planning and big-bang delivery model is practiced.
    • Rewards and Recognition of individual performances still exists.
    • Command and Control mode of working still exists. For example, Scrum teams do not have the liberty to conduct Retrospectives.
    • Business teams are not aligned with IT teams.

    The speakers’ experience is accumulated over the years while working with multiple and large financial organisations across the globe.

  • Liked Gaurav Rastogi
    keyboard_arrow_down

    Gaurav Rastogi - Beingh Hi-Touch in Hi-Tech World

    45 Mins
    Tutorial
    Beginner

    It is very unfortunate that we are becoming Hi-Tech every single day at the cost of Being Hi-Touch.

    Recently i took a photograph of my family sitting in a room and not talking to each other but busy with their gadgets,This Paper is to help propagate the Agile Manifesto value "Individuals & Interactions over Process & Tools"

    to provide techniques and Help Leaders, Coaches, Change Agents, Team members to understand people better in their teams and work with them more effectively. This talk is based on the DISC human behaviour model.

    As a saying is It's not what you say It's what they listen and understand Matters.

  • Liked Suresh Konduru
    keyboard_arrow_down

    Suresh Konduru / Gaurav Rastogi - Exepedia - Enabling Business Agility of your leaders

    45 Mins
    Workshop
    Intermediate

    Exepedia is an Agile coaching model that was innovated during the Agile coaches retreat in India during Feb'17.

    In an organisational Agile transformation, one of the biggest reasons for failure is lack of alignment by various departments and their leaders. In many cases, engineering teams are Agile while leaders are still catching up.

    By leveraging this model, Agile coaches and Scrum Masters can help business leaders to co-create a shared transformation vision; and a collaborative plan for organisational alignment. Scrum Masters and Coaches can leverage this model to coach executives, senior leaders and managers. The model consists of a set of workshops (a mix of collaborative group workshops, one-one discussions, questionnaires etc.).

    It perceives organisational transformation in three stages - Know, Believe and Achieve - and conceptualizes the various activities during the three stages.

    The proposed session helps you experience Exepedia, in a workshop style.

  • Liked Atulya Mahajan
    keyboard_arrow_down

    Atulya Mahajan / Kiran Chhabra - Parenting Lessons for Agile Transformations

    45 Mins
    Talk
    Intermediate

    Agile transformations are no child's play. There is inertia, restlessness, impatience and the constant desire to run away. Traits that anyone who has been a parent to little kids has encountered, and learnt in their own way how to handle.

    This session looks at parallels between parenting and trying to influence teams through an agile transformation. We look at some of the things that successful parents do that can be done by leaders trying to take their teams through a transformation.

    Because if teams sometimes behave like children, the leader needs to be a parent too!

  • Liked Henny portman
    keyboard_arrow_down

    Henny portman - Will the project manager and PMO disappear in the agile world

    Henny portman
    Henny portman
    Partner
    HWP Consulting
    schedule 1 month ago
    Sold Out!
    45 Mins
    Talk
    Beginner

    I will focus on a possible transition of organizations who are introducing the agile way of working. Starting with a traditional project setup using permanent PMO (portfolio level) and a temporary PMO (project level). What will happen if the keep the team together as an agile team. What does that mean for the project manager. I will continue my story by adding an agile team. Coordination between the teams can be managed by a scrum of scrum. Still no need for a project organization with a project manager and a project board and no need for a temporary PMO. I add more teams and the coordination asks for a project manager. What dos this mean for a PMO? We can continue and institutionalize the coordination by using frameworks like Nexus, S@S, SAFe et cetera and has an Integration Manager, a Roadmap Manager or a Release Train Engineer and Product managers and Product Owners. I will add some new to be created teams (aks for a Project Manager to organise) et cetera. I will end with an overview and positioning of different agile frameworks and the role of the permanent PMO (focus portfolio management and Center of Excellence) in an agile world.

  • Liked Sathya Jayapaul
    keyboard_arrow_down

    Sathya Jayapaul / Vikas Goel - New Ways of Working for Legacy Mainframes Systems : A journey

    20 Mins
    Experience Report
    Intermediate

    This presentation is on the journey of Agile and DevOps transformation within the Core Banking & Payments division in RBS. This division forms the heart of the banking and Payments technology of RBS. The division has around 25 platforms supporting 150+ applications with most of their technology base being IBM mainframes.

    These are critical platforms as 1 in 4 of all payments in the UK are processed by RBS' payment systems, with the total value of RBS UK & International payments in 2016 being around GBP 55 trillion.

    RBS has embarked on an audacious journey to change their way of working through the adoption of Agile and DevOps in their legacy mainframe applications.