![Your own footer Your Logo ,[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Casro Presentation Project And Change Management 1st June 2011
Similar to Casro Presentation Project And Change Management 1st June 2011 (20)
Recently uploaded
Recently uploaded (20)
Casro Presentation Project And Change Management 1st June 2011
- 1. Project and Change Management Presented by – Brendan Light, BuzzBack Sameer Inamdar, Datamatics
- 3. What is needed beyond processes and technology tools to make it work
- 4. Our experience, and what worked for us
- 5. Summary of our learning's that can help in getting the best of a virtual team Introduction Objectives of this presentation
- 6. Traditional methodologies, new technologies Perpetual dilemma of make vs. buy Significant struggles to integrate bespoke applications with off-the-shelf platforms BuzzBack
- 7. 4 ANATIDAEPHOBIA The fear that somewhere, somehow, a duck is watching you.
- 10. 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.
- 13. It’s all about communication.
- 14. Coders are just a different creature. Even if you speak the same language, you don’t.
- 16. Good chemistry is part of the magic. What’s Unique Here
- 17. Sales Research Find the appropriate role for each supplier. BuzzBack Operations NPD Sample App Dev
- 18. Humanize your teams. Rishi Mukund Pravin Sandeep Arvind Velnati Amitabha Anshu
- 19. Commitment to evolving communications and processes.
- 20. Moved from centralized command and control to…
- 21. Decentralized and distributed engagements.
- 22. Created a hybrid PM methodology
- 23. So, how does it work!
- 25. Works only if the end objective is well specked
- 26. There is enough time for development
- 28. Works well and more flexible if the end objective is a moving target
- 29. The team adapts to changing requirements
- 31. Extended Team Model Team composition Core team BuzzBack & Datamatics On-request Resources Flash Resources QA Team .Net Resources
- 32. Extended Team Model Responsibilities Traditional Model Extended Model Datamatics BuzzBack Datamatics BuzzBack 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
- 33. Extended Team Model Execution Execution Your own footer Your Logo
- 34. How do we manage change?
- 35. Change Management The Process Identification Changes are identified and entered in online tools Changes are identified and entered in online tools
- 36. Change Management The Process Identification Feasibilty and Estimation The extended team discusses feasibility and estimates the time and impact
- 37. Change Management The Process Identification Feasibilty and Estimation Joint Decision & Execution Decision taken by the team and changes implemented
- 38. Change Management Tool Screenshots
- 39. Change Management Tool Screenshots
- 40. Change Management Tool Screenshots
- 41. 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
- 42. THANK YOU! Your Logo
Editor's Notes
- People are not rational. We are all increasingly aware through piling of evidence. But we still ask rationally based surveys. BuzzBack doesn’t think that’s the best approach.
- We have offices in NYC and London, but have remote workers wired in from all over. So, an overseas team is not an infrastructure issue. Concerns are about time zones, cultures,
- Communication problems are related to bad documentation, bad systems for tracking, and developers not feeling empowered to speak up.
- Ted Williams is arguably the greatest batter ever but only got hits 4 times out of 10. We need a much higher success rate.
- We’ve played with a lot of the PM methodologies, and they all have pros and cons but only experience will teach you which works for you.
- It’s all about communication. Phone, email, video conferencing, shared desktops, PM websites for project tracking, issue tracking, task tracking, as well as good documentation in word, ppt, visio, etc.Communication even drives process.
- We simply approach our work in fundamentally different ways. Our minds work differently. It’s crucial to find middle-ground. The better you can communicate what you want in the first place, the fewer revisions are necessary. It takes a while to get a rhythm and a process. Experiment, and be ready to fail…a lot.
- To be honest, there’s a bit of magic in finding the right team to work with.
- Vendors, ourselves included, love to say that “we don’t want to just be your vendor, we want to be your partner.” Which is often true. But in application development it MUST go beyond being a partner to being a team.
- Humanize your team
- We’re all committed to adapting and evolving.
- In the end we have a chimera approach, a custom project management methodology that both sides buy in to and adhere to.