Lessons learned and improvements

This page is a place holder for lessons learned.

What we need to do for each tool/component is match it to a defined set of users and see what their requirements and commitments are (rather than accepting that they expect us to work this out ourselves -
- This is typically where we have struggled in the past. Little interest combined with a loss the interest from the user -i.e. network engineers- because we didn't isolate them enough from SW developments and because we were not providing new features fast enough.
The set-up of an activity and of a task is taking 6-12 months, the beginning of GN3 should be pre-empted so that people get working as fast as possible. Setting up the activity organisation and the task organisation is a project in itself.
Conclusion from GN2 should be drawn, leveraging on the January meeting.
Define what is common accross the activities, what is common accross the tasks of an activity, what is proper to a task
Use best-practices, give a framework to the people involved.
Identify roles and give them some process to define.
Have need a clear strategy and have a "marketing" function to identify the directions to identify the service that should be added tot he portfolio.
Once a product is developed, we need to ensure its follow-up. People will want it to evolve and we need to look for the user if it works appropriatedly.