1 / 25

Navigating the Challenges of Distributed Mixed Projects: Insights from Experience

This text provides an overview of the author's practical experiences with distributed mixed projects over a 17+ year career in software sciences. It highlights both opportunities and challenges encountered in various initiatives, such as the ESPRIT and RACE programs. Key issues include unrealistic goals, inter-partner dynamics, and the impact of organizational chaos. The text emphasizes the importance of clear objectives, partner autonomy, and addressing intellectual property rights to enhance project success. Ultimately, it advocates for realistic ambitions and effective management in collaborative environments.

montana
Télécharger la présentation

Navigating the Challenges of Distributed Mixed Projects: Insights from Experience

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. Practical Experiences with Distributed Mixed Projects Albert Alderson

  2. Introduction • Distributed mixed projects offer a variety of opportunities and challenges • Share experiences – My perceptions • Offer some thoughts

  3. Background • 17+ years with Software Sciences • Alvey, Esprit & RACE • 6 years IPSYS Software • Esprit & RACE • 6 years Staffordshire University • EPSRC projects

  4. ATMOSPHERE • ESPRIT II – 5 years – 650 years effort • Harmonise the European IT industry • IPSE kit of parts • IPSEs for different industries

  5. ATMOSPHERE • 5 lead companies • Siemens, Bull, Nixdorf, Philips, GEC-Marconi • 2 Eureka projects • Countless sub-contractors

  6. ATMOSPHERE • Organisation was chaotic • In-fighting between the principles • GEC removed • Whole project died later

  7. ATMOSPHERE • Goals unrealistic • commercially and technically • Will to harmonise doubtful • IPR a root problem • A disaster

  8. ARISE • RACE 3 years • ~10 partners • UK, Eire, Greece, Spain, Sweden, ... • Specialist Management Partner

  9. ARISE • Telecomms IPSE • Clear technical objectives • Basic technology in place • Partner autonomy • Goodwill between partners • 2-3 day workshops 6 monthly

  10. ARISE • Papers aplenty • Improved individual tools • Commercially beneficial • No Telecomms ISPE • Long lasting relationships • A success?

  11. BOOST • RACE 3 years • ~12 partners • UK, Eire, Greece, Spain, France, Sweden, .. + major Telecomms org • Specialist Management Partner

  12. BOOST • Telecomms IPSE • Goals subverted by Telecomms org • Technology enforced by RACE • Four-monthly RACE workshops

  13. BOOST • Nothing worthwhile delivered • End of partnerships • Plagued by EU bureaucracy • Some ‘internal’ projects funded • A failure

  14. MACS • ESPRIT 3 years • 6 partners • UK, Italy, Spain, Germany, Greece • Lead fell to small UK company

  15. MACS • Maintenance of AI systems • Mix of AI and software eng. • Interesting idea no real goals • Lead knew nothing of AI • AI specialists no interest in software • Academics good at criticising

  16. MACS • A clash of technical cultures • A clash of national cultures • No tangible outcomes • A disaster

  17. COMPLEMENT • ESPRIT 3 years • ~12 partners • UK, France, Germany, Spain • Lead with a smaller partner

  18. COMPLEMENT • RTS methods review and dev • Harmonisation again • Objectives clear • Base technology ransom bid • Split into 3 national groups

  19. COMPLEMENT • A clash of national cultures • A clash of commercial interests • Worthy but unrealistic • Excellent analyses never published • A failure

  20. ECLIPSE • UK ALVEY 3 years • 6 partners • Software Sciences, CAP, LBMS Lancaster, Aberystwyth, Strathclyde • Lead with largest partner

  21. ECLIPSE • To build an IPSE • Partners realistic – previous prototypes • Manifesto – partner needs • Technical base - lead partner • Partner automony • 2-3 day workshops 3 monthly • Planned demonstrators

  22. ECLIPSE • Eurofighter HOOD toolset • base for metaCASE • new version of SSADM • useful tools and theory • Prof-ships, PhDs, career boosts • Papers, book • long term friendships

  23. Thoughts • Acknowledge partner goals • Deal with IPR • Place management sensibly • Realistic goals • Partner autonomy in context

  24. Thoughts • Safe base technology • Build 4 systems • Product, Development • Test, Management • Demonstrators • Working meetings not reporting • Take care of the social side

  25. I wish you all an Eclipse project

More Related