In this session we were introduced to two different management structures for our groups to consider using. Waterfall and Agile.
Agile
Here you can see a 10 minute break-down video were given to watch during the lesson, this covers an adaptation of the Agile method that adds on daily 'scrum' meetings for quick updates on progress and problems and generally to keep up communication between teams.
Agile seems like a really clever way to make any project a lot less daunting by breaking everything down into smaller components, and by creating a release backlog that project managers are certain can be achieved for an initial release, it saves a lot of wasted effort on features that can't be implemented in time. It also ensures through the sprint stages that every feature is fully tested and useable by the end of the cycle.
Waterfall
Waterfall, unlike Agile, is a very rigid design progress in which changes made in later stages of development are very undesirable, and potentially costly, so everything is planned out in advance. It see's progress as a steady transfer of work down through a series of stages, the diagram below shows some of these stages.
This method, though inflexible, allows everyone to work from pre specified plans, meaning that predictions for when the project will be completed can be made very accurately, provided said project has been thoroughly planned in advance.
In my opinion, i think that Agile would suite our group more, especially as in most cases it is our first major project, so anything that can make the next few months seem less daunting would be a boon. The flexibility that Agile allows would also be useful as we can all assume that mistakes will be made as we adapt to this new way of working.
No comments:
Post a Comment