Rating: | ★★★★ |
Category: | Other |
Tip 1: Analysis
The first step for an IT project involves analyzing your requirements for a solution. To do this, you need to analyze your business environment, processes, systems, people and organizational structure, to help you set out exactly what it is that the new IT solution must deliver. Typically, companies write a "Requirements Specification" which sets out their business requirements formally, so that at the end of the project, they have a formal stake in the ground, against which the solution can be measured.
Tip 2: Design
When you know what it is that you want, the next step is to design a solution for meeting those needs. In the design phase, you will design all of the components of the solution, including the; hardware, software, user interface, security and integration with other systems. The Project Manager will often get a "prototype" built, so that the customer can see roughly what the solution will look and feel like, before the development phase begins.
Tip 3: Develop
The longest and most time consuming phase is always the development of the system. This involves writing software code, constructing hardware, building the database, writing the user interface and fitting together each of the components into a complete solution for the customer. It's during this phase that most delays are experienced, and they are typically due to insufficient analysis and design being completed.
Tip 4: Test
When the solution has been built, it's time to test that it performs as expected. A smart tester will have already agreed with the customer what it is that should be tested and what the outcome should be. If this is done, then testing is more of a formality and there should be "no surprises" during the testing process. There are various types of testing, including system / load / performance / security / user interface testing.
Tip 5: Implement
After comprehensive testing, you're ready to "Go Live". You do this by installing the hardware at the customers site, installing the sotware, and migrating the data over from the existing system to the new system. Some final "checks and balances" are performed to ensure that the data is accurate and the system is performing as expected, and then you're finished.
SDLC?
ReplyDeleteHi Wingcom
ReplyDeleteNope, this is not SDLC but more on project management. SDLC should be subset in phase 3, development phase.
General project management overview?
ReplyDeleteYes. Have a details at http://www.method123.com/
ReplyDelete