1 / 10

Collaborative Project Management in a Decentralized Environment

This paper discusses the design and prototypical implementation of a publish/subscribe model for collaborative project management in a decentralized environment. It explores the requirements of the automotive industry, the challenges of cross-company collaboration, and the user experience and implementation considerations in highly restricted environments. The research questions include identifying the elements that need to be shared among involved parties and designing a distributed project management system using an established model.

rodriguezh
Download Presentation

Collaborative Project Management in a Decentralized Environment

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. A Publish/Subscribe Model for Collaborative Project Management in a DecentralizedEnvironment- Design andPrototypicalImplementation Michael Rose, 05/11/2015

  2. Environment PROJECTMANAGEMENT • large projects, lots of stakeholders • high complexity • diverse responsibilities not manageable by a single person AUTOMOTIVE INDUSTRY • long-term vehicle development projects (5 – 7 years) • highly inter-dependent structure • involvement of numerous suppliers (Tier 1, …) 150511 Rose Master Thesis Kickoff

  3. Environment REQUIREMENTS FOR AUTOMOTIVE PM [1] • standardized approach • early incorporation of all suppliers • synchronize project plan at early stages • clear delegation of responsibilities • open and fast communication of changes Collaboration DECENTRALIZATION • in-house installations • cloud-based approaches not applicable • high confidentiality and security requirements • so far no data synchronization Supplier 1 Supplier 2 OEM [1] Hab, Gerhard, and Reinhard Wagner. Projektmanagement in der Automobilindustrie - Effizientes Management von Fahrzeugprojekten entlang der Wertschöpfungskette. Wiesbaden: Gabler, 2010 150511 Rose Master Thesis Kickoff

  4. Motivation OEM • overall planning • internal separation for departments • maintain and update status • delegate responsibilities exchange by email, meetings, … Supplier Milestone DSC • internal planning • track status • manage external dependencies ECU DSC 150511 Rose Master Thesis Kickoff

  5. Motivation OEM CROSS COMPANY COLLABORATION • delegate responsibilities across systems publish artifacts • track relevant assets across systems subscribe to artifacts • synchronize changes • maintain security Supplier 150511 Rose Master Thesis Kickoff

  6. Research Questions 1 Which elements of the collaborative project management process need tobe shared among the involved parties? • milestones • tasks • documents • dependencies • … 2 How to design a distributed collaborative project management using an established model? • possible actions: publish (delegate), subscribe, revoke, … • ownership transfer • role handling • central system registry? 150511 Rose Master Thesis Kickoff

  7. Research Questions USER EXPERIENCE 3 How to implement a distributed collaborative project management system suitable for highly restricted environments? • visual representation kind (published / subscribed) synchronization errors • notifications, actions, … • Workflows DATA EXCHANGE • no / restricted internet access • firewall regulations • high security requirements – e.g. confidentiality INTEGRATION • PM software cPlace for prototypical implementation • data-model support, app integration, dependencies • compatibility – support for multiple protocol versions 150511 Rose Master Thesis Kickoff

  8. Status 1 2 3 • milestones • tasks • relations • complete plans • hierarchical parts • publish / delegate • communication over mail • asynchronous protocol • asymmetric encryption PKI? • subscribe Supplier Supplier OEM OEM 150511 Rose Master Thesis Kickoff

  9. Timeline START: 04/15 END: 10/15 Kickoff 07/15 Conceptual Phase Requirements Elicitation Existing Solutions Literature? UX Concepts Transport / Architecture Design 08/26 Prototyping UI Design Implementation 09/16 Evaluation Field Trials, Refinement 10/07 Writing 150511 Rose Master Thesis Kickoff

  10. Michael Rose rose@in.tum.de Thank you for your attention!

More Related