Disadvantages Of Code And Fix

818 Words 4 Pages
What are the benefits of code & Fix

There is a few advantages to the code and fix methodology, these may be no overheads, documentation and QA processes. Generally speaking and important to note it is used in short term, simple projects that require little man-hours to complete. It is also useful for simple projects in need of proof-of concept and finally it can be advantageous for short lived demos and/or throwaway prototypes.
What are the disadvantages of code & Fix?

There is a great risk involved in doing code in this fashion due to it being somewhat headfirst with no real planning involved. If you find yourself close to the end result and it is ultimately flawed you will have to restart the project again from scratch. Also in this type
…show more content…
Hence the physical design and specifications are generated simultaneously. Whereas the other main prototyping method is more structured and does not allow for this, following a rigid model where the plans are set and then followed throughout the development …show more content…
An example of this would be what I did yesterday? What’s on the agenda for today and are there any impending issues that are hindering me from completing my tasks?

What is the difference between a product backlog and a sprint backlog?
The product back log is essentially a detailed analysis documentation, outlining every requirement for a project, product or system, whereas a sprint backlog is a list of tasks strung together by the scrum team to be completed during the scrum sprint, this is usually done in a spring planning meeting.
What is the difference between a scrum master and a producer?
First off the scrum producer is more concerned with the release dates of the game/games, in turn they liaise more with the stakeholders and manage feedback given to those who fund the project. They accept and reject results produced by the team members as a final say with their stakeholders needs in mind. Whereas a scrum master is more engaged with the team itself the developers facilitating the team and supporting the process and taking care of the management protocols all the while preventing any interruptions of the development

Related Documents