
First of all, to start a project; there should be a project to be started. By that I mean there should be a requirement for a project. 'Requirement' is a very important term which goes with the term 'Project'. A project in my prospective, is the way of obtaining an outcome which satisfy the requirements.
Requirements alone does not make any sense. When we talk about requirements, there are people who have requirements and want a solution. These people are the Clients. And it is the job of an undergraduate to talk with the clients and gather requirements. But this is not a very easy task. The clients might have a good understanding of what they want and how they want you to do it. They might have a good understanding of the IT field as well. But that is the best case scenario. There can be clients who have no idea about IT. And in the worst case, have no specific idea what they want and how they want it.
There are several follow up ways with the methodology that we will be following to do the project.
1 - Adaptive Project Framework
2 - Agile Software Development
3 - Crystal Methods
4 - Dynamic Systems Development Model (DSDM)
5 - Extreme Programming (XP)
6 - Feature Driven Development (FDD)
7 - Information Technology Infrastructure Library (ITIL)
8 - Joint Application Development (JAD)
9 - Lean Development (LD)
10 - PRINCE2
11 - Rapid Application Development (RAD)
12 - Rational Unified Process (RUP)
13 - Scrum
14 - Spiral
15 - Systems Development Life Cycle (SDLC)
16 - Waterfall (Traditional)
Above mentioned are some of those aspects. For more details click here to view full details.
This is how a project is started, I will be writing on the method that we used to do the project and will be writing about it in the next post.
0 comments:
Post a Comment