300 likes | 430 Views
Fostering Ad-Hoc Collaboration Between Marketing and R&D Departments. (Concurrency Corporation). Contents. Executive Summary Current State Analysis Future State Analysis Business Case Adoption & Implementation Planning Next Steps. 2. Background.
E N D
Fostering Ad-Hoc Collaboration Between Marketing and R&D Departments (Concurrency Corporation)
Contents • Executive Summary • Current State Analysis • Future State Analysis • Business Case • Adoption & Implementation Planning • Next Steps 2
Background • A consumer product development company, faces a number of challenges related to interdepartmental collaboration between the Marketing and R&D departments, including: • Inefficient communication and collaboration between departments • Long cycle times to address critical issues along the product development lifecycle • Lack of cross-visibility between the departments, leading to divergent directions in product development that must be laboriously reconciled later • Labor intensive preparation for weekly sync meetings between R&D and Marketing stakeholders to address trivial problems • Critical issues are often not identified until late in the product development process • The net result of these challenges is increased time to market, increased product development cost, and lower product profitability 3
Background • Due to lack of frequent collaboration between marketing and R&D teams, teams working on the same project often diverge and require time consuming and costly realignment during the product development process: Marketing Path Converge Converge R&D Path Product Launch Project Kickoff Mid-course Realignment Meeting
Executive Summary • Concurrency proposes expanding upon your current Office System deployment to incorporate Ad-Hoc Collaboration capabilities • Implementing the proposed Ad-Hoc Collaboration solution will provide you with: • Real-time collaboration between product development stakeholders within the departments • 25% decrease in time to market, from 8 months to 6 months • 25% increase in sales due to better, more feature rich products • 30% reduction in product development labor time and cost • Anticipated annual benefit to (Contoso) of $250,000 6
Executive Summary • By promoting constant Ad-Hoc Collaboration between the Marketing and R&D teams, you can ensure proper alignment between the efforts of the two teams • The teams function more as one unit, rather than two separate units • More marketing and engineering data is available earlier in the design process, which ensures better, more marketable products • Ultimately, this alignment reduces the time, effort, and cost to get products to market, and increases product revenues: Marketing Path R&D Path Project Kickoff Product Launch Ad-Hoc Collaboration
Contents • Executive Summary • Current State Analysis • Future State Analysis • Business Case • Adoption & Implementation Planning • Next Steps 10
Current State Process Analysis Product Development Process – Analysis Summary 11
Contents • Executive Summary • Current State Analysis • Future State Analysis • Business Case • Adoption & Implementation Planning • Next Steps 15
Future State Process Analysis Product Development Process – Analysis Summary – Analysis Summary 16
Prioritized Process Solutions High 5 • Deploy SharePoint Server 2010 • (SharePoint Server 2010 ) • Deploy Office CommunicationServer 2007 R2 • (Office Communication Server 2007 R2 ) Level Of Complexity 3 • Enable advanced SharePoint Features: • Blogs, Wikis, Expertise Search, Presence • (Office Communication Server 2007 R2, • SharePoint Server 2010 ) Low 1 5 1 3 High Low Value to Business 17
Contents • Executive Summary • Current State Analysis • Future State Analysis • Business Case • Adoption & Implementation Planning • Next Steps 20
Contents • Executive Summary • Current State Analysis • Future State Analysis • Business Case • Adoption & Implementation Planning • Next Steps 24
Project Plan 26
Contents • Executive Summary • Current State Analysis • Future State Analysis • Business Case • Adoption & Implementation Planning • Next Steps 29
Next Steps • Review presentation and proposal with decision maker(s) and stakeholders for approval • Consider a SharePoint Deployment Planning Services (SDPS) follow-up engagement • Execute work order for project • Schedule kick off meeting for week of _____ and weekly status meetings • Propose schedule: • A) Deadlines for initial milestones, or • B) Date to finalize initial milestones 30