Can agile development methodology be an alternative to the problem? The answer is yes and no.
Whenever I think of agile I see it as a development methodology where the documentation part is missing. May be I am entirely wrong here. It is perhaps my perception that the knowledge does not get documented anywhere. If a team successfully built a rocket and launched it and if a new team is asked to build it again, it becomes difficult if agile development was followed in the first place. According to my understanding, the knowledge that was built over time is not documented anywhere so that it can be used to do the task effectively the second time.
It is perceived that the agile methodology does not allow Bangaloring (a k a outsourcing). But my strong feeling is that it is possible to offshore work even while following agile methodology. There are tools available in the market that helps organisations and projects to have the best of both worlds (I mean agile and offshoring).
The best part is users can see the software getting built in front of their eyes and change the requirements on the fly. This means that the user gets what he/she wants. Does this somewhat resemble the construction engineering industry?
Yes. It does. But then why most software projects are behind schedule and do not meet user expectations?
The reason could be…
No comments:
Post a Comment