Now you finally here, this is the stage where all of your planning will be put to the test. Some people like to think of this as the end after this stage is complete but really you are only half way through the first cycle of the SDLC.
Now you and your team can put into action the plans that you laid out. Using your designs that you have created using models and other such tools you will be able to create a plan of action. Creating a list of targets is a good idea, work that should be carried out during the day by each member of the team. You could separate this into functionality; this could be anything within the project, such as ensuring that data is persisted to storage, or login authentication for secure sections of the program.
A vast amount of planning should be done before entering this stage of the SDLC; this will enable a smooth development process. A good idea is to have daily meeting within you team each day before work starts, this will enable your team to communicate any issues that they having with the development process, this session could also include any suggestion about the project, these items are called change and they should be kept track of. Having a change log is something that could really help; a change log would consist of items that have been change from the original scope of the project. Feeding suggestion back to the stakeholders’ should be done through a hierarchy, and the changes that have been suggested by the development team should not be jumped into, the real crucial thing about developing software today is ensuring that it does the job that it is supposed to. Projects can fail because a development team has including lots of ‘neat’ functionality and left the project lacking lots of key features which could lead to the project not being fit for its purpose.
Creating flow charts may seem like they do not belong in this situation but they are a tool that can be used to create pathways of work. Such as creating functionality, here is an example of a flow chart, in a very simple form that can show the activities and the order that they could be carried out during the implementation.
You are able to get an idea here on how it would work. Working down through the flow chart will give you the ability to assess progress and set target for you team. This is very simple and could be classed as very high level; of course you could definitely go into more detail at each section. Such an example would be creating the structure of the HTML page then adding the styling, and so on.
On from creating the flow charts and other method that you could use to judge performance and progression throughout the project, it is also a good idea to keep a record of the work that has been completed. Such a record could be a spread sheet listing; the task completed, by who and time taken to complete the task.
Recording any issue that arises within the development of the project is also a tool that can be used to inform stakeholders and others about the problem encountered. It would then be possible to arrange solutions to the problem.
Check out Part Four where we discuss Testing