Brainstorming Efficiency

1. PROCESS
1.1 new process models: extreme programming, incremental
process,... more appropriate?
1.2 how to deal with prototypes rapid prototyping separate
prototyping from development through away the prototype! How
to do it?? How to sell it?
1.3 spec freeze??? do we need it?? for samples?? on functional
level??
1.4 definition of a SW delivery
1.5 review approach???
1.6 metrics / efficiency measurement missing
1.7 no modification without clear spec / no excuse , do nothing
without payment from customer even under strong pressure of
SOP
1.8 process applied in an appropriate way
1.9 no validation for A sample
1.10 no test at all?
1.11 apply the Hyundai PIC approach to other projects
1.12 minimum process requirements

2. PROJECT MANAGEMENT & RELATED TOOLS

2.1 too many tools for planning & tracking (MSP; WPs; ASCOM;
Continuus; SAP; ....) Hourly writing (KSSE, hour tracking,....)
2.2 too many deliveries to the customer
2.3 double work?
2.4 distributed development control & tracking
2.5 time schedule too tight
2.6 work package template improvement automatisation for planning
& tracking
2.7 resource planning during acquisitions
2.8 effort estimations are always too optimistic (i.e. based on only
experienced engineers)
2.9 risk management missing
 2.10 additional SW tasks are not considered: CANAPE, EMC test SW,
EOL, flash reprogramming, S4 subjects,....
2.11 lack of planning / no systematics
2.12 time is incompressible
2.13 synchronisation HW / SW release planning
2.14 change management (allover!)
2.15 are the workpackages too small?

3. THE REST
3.1 not enough PR of SW to the outside nobody knows how we are
working
3.2 Outsourcing: can we outsource complete projects?
3.3 work environment too loud, space,...
3.4 what can we stop / not do

4. TRAINING & KNOWLEDGE MANAGEMENT

4.1 loss of technical competence
4.2 experts missing CAN, tools, ...
4.3 problem collection and redistribution not working
4.4 continuus usage / missing training
4.5 untrained developers

5. SW ARCHITECTURE & DESIGN

5.1 technical project management / also on the system side missing
5.2 define product architecture and interfaces instead of detailed
design
5.3 clear standard for SW design missing

6. ORGANISATION
6.1 size of the team must fit with the size of the projects
6.2 clear focus of responsibility for each location
6.3 no tasks to TSR but projects
6.4 stop growing in TSR
6.5 more senior SWPLs as a help for difficult projects
 6.6 discipline how to get it?
6.7 HW deliveries to TSR (shipping)
6.8 bring more technicaly knowledgable people to TSR
6.9 separation of generic & project specific development
6.10 do we need a central validation group?
6.11 do we need a reverse engineering activity?
6.12 question of critical mass of the generic functions: are the
functions not too small

7. ATTITUDE & WAY OF WORKING

7.1 we discuss something new with the customer instead of using
something known
7.2 reuse not done / reuse of unstable solutions
7.3 we do not play a proactive role proposing solutions
7.4 keep / increase motivation
7.5 shifting of responsibility
7.6 change of priorities stay with decisions taken
7.7 accept given standards (e.g. BSW interface,...)

8. TOOLS & METHODS

8.1 autocoding
8.2 test & validation strategy needed
8.3 test automatisation
8.4 improve methodology & tool support
8.5 continuus too heavy (release takes too long)
8.6 missing equipment / not appropriate
8.7 test bench environment set up
8.8 CM coordination for distributed environment
8.9 continuus DCM transfer too slow