ðHgeocities.com/dasmz/tada1.htmlgeocities.com/dasmz/tada1.htmldelayedxspÔJÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÈÀ%£e)OKtext/htmlP¯õKe)ÿÿÿÿb‰.HTue, 28 Jan 2003 20:28:03 GMTNMozilla/4.5 (compatible; HTTrack 3.0x; Windows 98)en, *qpÔJe) Assignment
Assignment #2

Fig 1

Question

 

Answer

 

 

 

 

With reference to Fig 1, answer the questions below:

  What do you think are the advantages of having such an evolutionary team structure for software development?

    Advantages are:

  • Evolution captures change in team structure during software development life-cycle

  • Each stage in the evolution is characterised by a major set of activities in that phase, clearly defined

  • Employment of appropriate people at  the right time during the life cycle can be overseen.

  • Everybody within the team can take part in the project activities in ach stage given the capabilities

  • Structure depicted is more suited for simple and small organizations developing simple program applications.

 

 

 

What are the inherent problems in such a structure? 

  • Difficult for each phase to complete its objective within the time-period of the phase because of the sequential nature; the problems in the future phases might not be fully known
  •  Even though that’s the basic development cycle, there might be more complicated roles in each phase. Where the following factors have to be considered such as size of development team, nature of project, etc.
Question

Answer

 

 

 

 

 

Question

 

Answer

 

 

 

 

 

Modify the diagram and show how you would improve the team structure

Structure depicted is more suited for simple and small organizations developing simple program applications.

However, for complicated software development processes, the above model for team structure would have to be modified according to the needs of the project. More iterations, probably in a spiral will have to be added, in each respective phase of the project, depending on when they are needed. For example in the transition phase, if minor changes have to be made, they have to go through minor evolution of the whole software process itself, with different percentages of involvement in each iteration.