casro presentation project and change management 1st june 2011

Presented by –Brendan Light, BuzzBackSameer Inamdar, Datamatics

Project and Change Management

Your own footer Your Logo

• Explore how market researchers and developers can co-exist – no seriously!

• What is needed beyond processes and technology tools to make it work

• Our experience, and what worked for us• Summary of our learning's that can help in getting the

best of a virtual team

IntroductionObjectives of this presentation

• Traditional methodologies, new technologies• Perpetual dilemma of make vs. buy• Significant struggles to integrate bespoke applications

with off-the-shelf platforms

BuzzBack

4

ANATIDAEPHOBIAThe fear that somewhere, somehow, a duck is watching you.

We have issues…

7

• 10+ years of experimentation/collaboration with developers

• More success than failures, but failures are very costly

• Most failures are the result of poor communication, rarely the result of poor skill set.

It’s all about communication.

Coders are just a different creature.

Even if you speak the same language, you don’t.

We have solutions…

What’s Unique HereGood chemistry is part of the magic.

BuzzBack

Sales

Operations

Research

Sample

NPD

App Dev

Find the appropriate role for each

supplier.

Pravin Sandeep

Rishi

Velnati

Humanize your teams.

Anshu

Arvind

Amitabha

Mukund

Commitment to evolving

communications and processes.

Moved from centralized command and control to…

Decentralized and distributed engagements.

Created a hybrid PM methodology

So, how does it work!

Traditional Model

• Mostly Waterfall methodology used

• Works only if the end objective is well specked

• There is enough time for development

• The requirements do not change significantly during life of the development

Extended team model

• A mix of different methodologies depending on the end objective

• Works well and more flexible if the end objective is a moving target

• The team adapts to changing requirements

• Develop - Review - Adapt

Extended Team Model

Extended Team ModelTeam composition

Core team BuzzBack & Datamatics

Flash Resources

.Net Resources

QA Team

On-request Resources

Extended Team ModelResponsibilities

Traditional Model Extended ModelRequirements

Production Deployment

Technical DesignDevelopmentIntegrationTesting

Staging DeploymentReviewsUpdations

Maintenance

ArchitectureFunctional Design

Requirements

Production Deployment

Technical DesignDevelopmentIntegrationTesting

Staging DeploymentReviewsUpdations

Maintenance

ArchitectureFunctional Design

BuzzBackDatamatics BuzzBackDatamatics

Extended Team ModelExecution

Your own footer Your Logo

Execution

How do we manage change?

Change ManagementThe Process

Identification

Changes are identified and entered in online toolsChanges are identified and entered in online tools

Change ManagementThe Process

Identification

Feasibilty and Estimation

The extended team discusses feasibility and estimates the time and impact

Change ManagementThe Process

Identification

Joint Decision&

Execution

Feasibilty and Estimation

Decision taken by the team and changes implemented

Change Management Tool Screenshots

Change Management Tool Screenshots

Change Management Tool Screenshots

• The working model will depend on end objectives of the development

• A flexible agile approach is more suited for market research

• The extended team model ensures joint responsibility of success/failure and it has worked well for us

• Change management is a joint responsibility with well defined success criteria for both sides

To Summarize

THANK YOU!

Your Logo