Developers know that better than anyone … “If anything can go wrong, it will.”
You are getting ready for a demonstration in the most critical day of your career and… demo fails. How can you avoid to confirm Murphy’s law?
In eWALL we decided from the beginning to adopt Agile development practices, such as SCRUM. Unlike a ‘waterfall’ kind of development, we fragmented the software components into many pieces that have been constantly evaluated and prioritized, so that they can be implemented in the so-called “sprints”. Based on the nature of the project, we anticipated continuous changes and updates on the services and applications of eWALL and the “sprints” contributed significantly in minimizing the “technical debt”. That helped a lot to address Mr. Murphy, but that alone was still not enough. We introduced the role of “Integration Orchestrator”, a cross-WP activity to support the end2end integration of components, both HW and SW, and ensure the proper preparation of software releases.
These is the first part of our 2-cents with regards to integration in large scale projects. Stay tuned for part 2, with additional information from the pilots!