httpwebimpressionsnetwpcontentuploads201610MIS521HubbleCaseB

http://web-impressions.net/wp-content/uploads/2016/10/MIS521_Hubble-Case-B.pdf using this pdf answer

What are the the lessons learned by your group in the process of analyzing this case. ?

Solution

Agile is relatively easy to implement for a 200 person day project, but nearly impossible for projects as big as 3000 person days. In agile, programmers work closely with users to prioritize which needs to address. Delivery in agile can be done in short cycles, but managing expectations can be tricky.

It is difficult to implement agile with a firm price offer for a project. In such case, one ca agree the number of development units in that price and deliver fixed units every cycle. The client has to decide what to prioritize and what to put aside.

Agile development should be carried out by face-to-face interaction between users and developers, but a reliable contact at the client\'s place can also be used. It is essential to be a skilled negotiator and be able to guide the client through a myriad of choices. Sometimes, tough decisions may have to be made.

Implementing agile for a remote project may inrease the frequency of travel.

In this situation, considering the size of the project and the remote location, implementing agile is risky. Not all risks can be covered and it would be better to stick to the traditional approach. Also, since everything here is new, including the development team, introducing agile is highly risky and the chance of failure is also high.