Producing a new computer game
Structure
To produce a new computer game, the company should use the methodology Agile. This approach
of completing a project does it in stages and is an ongoing cycle. The company first have a meeting,
plan what they’re doing, design the game, develop the game, test the game with players and then
they evaluate their progress. This process cycles until they have a functioning game which they can
add to in the future.
Characteristics of Agile
One characteristic of Agile is the scope of visibility. Agile is designed to create a shared vision of
outcomes which are clearly identified and to make it easy for developers to quickly understand
when a task needs to be done. This helps ensure every member of the team has an equal
opportunity to make decisions which are consistent with their vision and their team's goals.
Another characteristic of Agile is finding issues in the project quickly. When you start with a plan for
a project, you don't know how it will go until it's done. With Agile, it irons out any flaws that the
team missed to make the plan go as smoothly as possible.
And the final characteristic of Agile is it being enjoyable. This means in the long run it's easier to
deliver good products because everyone has a passion for what they’re all working on. This helps in
maintaining focus on what you want to achieve and the process of delivering the product.
Benefits to using Agile
A benefit to using Agile is it’s client friendly. This mean that the development process includes the
people the game is made for so they can add their own ideas to the development process. This
speeds up development because the team are working on aspect their audience want.
Another benefit to using Agile is it’s a mixture of methodologies. While the game is being developed,
the team can change which methodology they use. This provides flexibility towards the development
of the game and allows for a little leeway on their deadlines.
The final benefit to using Agile is it has clear outputs. With each iteration of the process, the team
will meet up to discuss what they have to do next. At the end of the meeting, they’ll have a goal to
achieve. This makes sure everyone knows what is being worked on and when it will be completed.
Implications to using Agile
An implication to using Agile is full commitment is required. The development team must be fully
committed to working on the game, otherwise aspect of it won’t be delivered on time. If this
happen, this will slow the development of the game down and possible extending the release date.
The next implication to using Agile is the need of teamwork from stakeholders. The company need
to be in constant contact with the client to ensure they’re happy with the progress they’re making. If
this doesn’t happen, the team could create the game the audience don’t find enjoyable.
The last implication to using Agile is the need for an experienced development team. The team need
to have experience from past projects to ensure they know how to approach the development and
to communicate to others effectively. If this doesn’t happen, people in the organisation won’t be
clear on where the game is at and be misled.
, Skills Needed
One skill that is needed to produce a computer game is resilience. There are going to be lots of
different ideas for the game and some won’t make it to the final version. Team members need to
make sure that if their idea isn’t chosen, they don’t take it personally as this could cause arguments.
Another skill that is needed to produce a computer game is passion. The Team need to be
emotionally invested into the development in the game, so they put a lot of effort into their tasks. If
the team working on the game are not interested in the project, this will show through and the
players will be able to tell.
Risks
A risk to producing a computer game is the lack of interest in the game. If the players are not
interested in the game, it will demotivate the team it. To avoid this, the organisation could look at
the audience’s expectations to add features into the game. This would make it more interesting and
lead to the players having more support in the game.
The next risk to producing a computer game is missing staff. If one staff member has graphical
design skills and they quit, it would halt the progress of the game until a replacement is found.
Another staff member could be put to the job however, they might not have the required skills and
would do a bad job. To avoid this, the organisation could hire multiple people with similar skill sets.
This would solve the problem because multiple staff would have skills in a range of areas and if one
leaves, another could take their place. Plus, they would produce quality work on the task.
Case Study
HealthCare.gov is a website to allow people in the USA to pay for health insurance. It was released in
2013 and is still operational today. However, it had many issues when it first came out. Many people
who went onto the website couldn’t send a query through. This frustrated users and they lost out of
getting health insurance. But the main issue was the lack of leadership. There were at least 20
consultants working on the project, but no one was the designated leader. If they were to work on a
project with this methodology, they need to decide on a leader to help decide where the project
heads towards.
https://openviewpartners.com/blog/agile-done-right-agile-gone-wrong/
https://en.wikipedia.org/wiki/HealthCare.gov#Concerns_about_the_website
Structure
To produce a new computer game, the company should use the methodology Agile. This approach
of completing a project does it in stages and is an ongoing cycle. The company first have a meeting,
plan what they’re doing, design the game, develop the game, test the game with players and then
they evaluate their progress. This process cycles until they have a functioning game which they can
add to in the future.
Characteristics of Agile
One characteristic of Agile is the scope of visibility. Agile is designed to create a shared vision of
outcomes which are clearly identified and to make it easy for developers to quickly understand
when a task needs to be done. This helps ensure every member of the team has an equal
opportunity to make decisions which are consistent with their vision and their team's goals.
Another characteristic of Agile is finding issues in the project quickly. When you start with a plan for
a project, you don't know how it will go until it's done. With Agile, it irons out any flaws that the
team missed to make the plan go as smoothly as possible.
And the final characteristic of Agile is it being enjoyable. This means in the long run it's easier to
deliver good products because everyone has a passion for what they’re all working on. This helps in
maintaining focus on what you want to achieve and the process of delivering the product.
Benefits to using Agile
A benefit to using Agile is it’s client friendly. This mean that the development process includes the
people the game is made for so they can add their own ideas to the development process. This
speeds up development because the team are working on aspect their audience want.
Another benefit to using Agile is it’s a mixture of methodologies. While the game is being developed,
the team can change which methodology they use. This provides flexibility towards the development
of the game and allows for a little leeway on their deadlines.
The final benefit to using Agile is it has clear outputs. With each iteration of the process, the team
will meet up to discuss what they have to do next. At the end of the meeting, they’ll have a goal to
achieve. This makes sure everyone knows what is being worked on and when it will be completed.
Implications to using Agile
An implication to using Agile is full commitment is required. The development team must be fully
committed to working on the game, otherwise aspect of it won’t be delivered on time. If this
happen, this will slow the development of the game down and possible extending the release date.
The next implication to using Agile is the need of teamwork from stakeholders. The company need
to be in constant contact with the client to ensure they’re happy with the progress they’re making. If
this doesn’t happen, the team could create the game the audience don’t find enjoyable.
The last implication to using Agile is the need for an experienced development team. The team need
to have experience from past projects to ensure they know how to approach the development and
to communicate to others effectively. If this doesn’t happen, people in the organisation won’t be
clear on where the game is at and be misled.
, Skills Needed
One skill that is needed to produce a computer game is resilience. There are going to be lots of
different ideas for the game and some won’t make it to the final version. Team members need to
make sure that if their idea isn’t chosen, they don’t take it personally as this could cause arguments.
Another skill that is needed to produce a computer game is passion. The Team need to be
emotionally invested into the development in the game, so they put a lot of effort into their tasks. If
the team working on the game are not interested in the project, this will show through and the
players will be able to tell.
Risks
A risk to producing a computer game is the lack of interest in the game. If the players are not
interested in the game, it will demotivate the team it. To avoid this, the organisation could look at
the audience’s expectations to add features into the game. This would make it more interesting and
lead to the players having more support in the game.
The next risk to producing a computer game is missing staff. If one staff member has graphical
design skills and they quit, it would halt the progress of the game until a replacement is found.
Another staff member could be put to the job however, they might not have the required skills and
would do a bad job. To avoid this, the organisation could hire multiple people with similar skill sets.
This would solve the problem because multiple staff would have skills in a range of areas and if one
leaves, another could take their place. Plus, they would produce quality work on the task.
Case Study
HealthCare.gov is a website to allow people in the USA to pay for health insurance. It was released in
2013 and is still operational today. However, it had many issues when it first came out. Many people
who went onto the website couldn’t send a query through. This frustrated users and they lost out of
getting health insurance. But the main issue was the lack of leadership. There were at least 20
consultants working on the project, but no one was the designated leader. If they were to work on a
project with this methodology, they need to decide on a leader to help decide where the project
heads towards.
https://openviewpartners.com/blog/agile-done-right-agile-gone-wrong/
https://en.wikipedia.org/wiki/HealthCare.gov#Concerns_about_the_website
