Task 1
Within this task i was to research and try to prove that IT personnel isn’t of people who spend their time sitting alone at a work station writing obscure commands and that they spend jus as much time in meetings as they do behind a computer work station. With doing research on a typical programmer 9 – 5 day job, I have discovered that a programmer actually spends less than three hours on actual programming. This shows that the programmers have a huge role in the development within systems. For the development part of the programmers work, programmers would spend roughly more than three hours in meetings. This clearly shows that a typical programmer jus doesn’t spend their full working day behind a computer workstation.
Systems analysts would spend very little, if any, times in meetings as they are sorely dependant on checking that the projects are worth wile. They are always trying to find ways to see if the system could be updated or even improved and because of this they would never really be seen at meetings and therefore would be stuck behind a computer workstation unlike computer programmers. The analysts have a high responsibility on reporting how the system works and therefore they need to make sure they are providing appropriate material in meetings when they get the chance to attend them.
Task 2
Post implementation review (PIR) is the review at the end of the project. The overall aim of the post implementation review is to understand whether the purpose of the project was achieved and if it wasn’t then what more needs to be dun to achieve this aim. PIR is only performed when there is time to show the benefits that it can have on a project. Without PIR it is difficult to understand whether the project can be a success or not, and whether the improvements that could be made could significantly help the project. The Project Owner is responsible for the PIR. The Post Implementation Review should be carried out near the start of the project as this allows the company to adapt to changes quickly. Not only should the PIR be performed at the earliest stage of the company it should also be carried out by most of the company members. This allows the members to share their points so that everything is taken into consideration for the benefit of the company.
Structured Walkthrough is the method of checking a computer system, repairing it, and also entails a systematic review which checks for errors within the system.
Before A Structured Walkthrough – The Systems Co-ordinator is informed of meeting and it is his responsibility to update everyone that there is a meeting and that they should bring the required materials. The other members of the company need to prepare the meeting so that they have a debate to talk about. They require that the members take one positive and negative outcome to the meeting.
During The Structured Walkthrough – the members need to remember that they should accept the procedures that are agreed on and that they should follow these procedures. They should also be wary that they review the product which has been discussed. The structured walk through is to outline the company’s and how these can be improved upon and not to let these errors happen in the future. During the walkthrough meetings the members will agree to accept these errors that have been established in the company or else to improve upon these errors and not let them become a factor. These structured walkthrough meetings are very time consuming and tiring on the members.
After The Structured Walkthrough – once the meetings are completed the co-ordinator makes a summary using the secretary’s notes. This summary will then be given to all those who require it. It is from this that the producer is to fix any errors that are fixable within the project. If there are any errors which the producer cannot fix they have to provide a valid reason as to why these errors could not be fixed.
Scrum Meeting is the management of the software development projects. Scrum meetings can operate software maintenance teams, or the general project management approach. “Scrum is a “process skeleton,” which contains sets of practices and predefined roles. The main roles in Scrum are:
- the “ScrumMaster”, who maintains the processes (typically in lieu of a project manager);
- the “Product Owner”, who represents the stakeholders;
- the “Team”, a cross-functional group of about 7 people who do the actual analysis, design, implementation, testing” (http://en.wikipedia.org/wiki/Scrum_%28development%29#.E2.80.9CPig.E2.80.9D_roles)
Chicken Roles – The chicken roles are vitally important even thought they are not actually part of the SCRUM. These are the customers, vendors or management which the software is produced for.
Pig Roles – These are all those who are included within the SCRUM process. These may include project owner, SCRUM master and the project team which creates the project.
