Project and Change Management

Project and Change Management
Presented by –
Brendan Light, BuzzBack
Sameer Inamdar, Datamatics
Introduction
Objectives of this presentation
• 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
Your own footer
Your Logo
BuzzBack
• Traditional methodologies, new technologies
• Perpetual dilemma of make vs. buy
• Significant struggles to integrate bespoke applications
with off-the-shelf platforms
4
ANATIDAEPHOBIA
The fear that somewhere, somehow, a duck is watching you.
We have issues…
• 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.
7
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
Good chemistry is
part
of the magic.
Unique
Here
Sales
Research
Find the
appropriate role
for each supplier.
BuzzBack
Operations
NPD
App
Dev
Sample
Humanize your teams.
Rishi
Mukund
Pravin
Sandeep
Arvind
Velnati
Amitabha
Anshu
Moved from
centralized
command and
control to…
Decentralized
and distributed
engagements.
Commitment to
evolving
communications
and processes.
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 Model
Team composition
Core team BuzzBack & Datamatics
On-request
Resources
Flash Resources
QA Team
.Net Resources
Extended Team Model
Responsibilities
Traditional Model
BuzzBack Datamatics
Extended Model
Requirements
Requirements
Functional Design
Functional Design
Architecture
Architecture
Technical Design
Technical Design
Development
Development
Integration
Integration
Testing
Testing
Staging Deployment
Staging Deployment
Reviews
Reviews
Updations
Updations
Production Deployment
Production Deployment
Maintenance
Maintenance
BuzzBack Datamatics
Extended Team Model
Execution
Execution
Your own footer
Your Logo
How do we manage change?
Change Management
The Process
Identification
Changes are identified and
entered in online tools
Change Management
The Process
Identification
Feasibilty and
Estimation
The extended team discusses
feasibility and estimates the
time and impact
Change Management
The Process
Identification
Feasibilty and
Estimation
Joint Decision
&
Execution
Decision taken by the team
and changes implemented
Change Management
Tool Screenshots
Change Management
Tool Screenshots
Change Management
Tool Screenshots
To Summarize
• 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
THANK YOU!
Your Logo