Project Management & Process in the Foundry
Posted: Sat Jun 13, 2009 12:47 pmProject Management & Process in the Foundry
Where I work we have a implemented a lot of process. I thought I would share my thoughts on process and the foundry just a bit. And my thoughts on stages of map development in comparison with how the project might be managed if there were a project manager assigned to it. This may be quite boring but you might find some information here that will help you if you are working on a map. Mind you this is just my thoughts on how these principles might be applied and I am not saying you should follow any of this. Process works differently for everyone and should be adapted to your personal style.
The RACI matrix
A Responsibility Assignment Matrix (RAM), (also known as RACI matrix or Linear Responsibility Chart (LRC)), describes the participation by various roles in completing tasks or deliverables for a project or business process. It is especially useful in clarifying roles and responsibilities in cross-functional/departmental projects and processes.
Responsible
Those who do the work to achieve the task. There is typically one role with a participation type of Responsible, although others can be delegated to assist in the work required... I see this as the person who submitted teh map idea and has taken the lead on the map's construction. This would also include people who assist such as a graphic artist or an XML expert.
Accountable (also Approver or final Approving authority)
Those who are ultimately accountable for the correct and thorough completion of the deliverable or task, and the one to whom Responsible is accountable. There must be only one Accountable specified for each task or deliverable... I see this as the foundry staff who decide when a map is ready to move from ideas, to drafts, to foundry, to final forge, and ultimately become quenched.
Consulted
Those whose opinions are sought; and with whom there is two-way communication... I see this as you, the players, mapmakers, and founder staff with who I communicate about the map and gameplay etc...
Informed
Those who are kept up-to-date on progress, often only on completion of the task or deliverable; and with whom there is just one-way communication... I see this as the people who have chosen to read this thread without commenting or receive updates on the map's progress through the newsletter.
Project Management
Initiate - This is the phase where a project begins. In foundry terms this would be when a mapmaker posts a map idea in the map ideas message board and seeks input.
Elaborate - This is the phase where a project takes shape and a set of plans are created so that the project can move on and work on it can happen. In the foundry this happens in the ideas forum and continues into the draft forum as a map idea takes shape.
Construct - In this phase the work of a project is begun. There is usually a Q&A overlap starting mid-phase. In founder terms this is when a map moves to the main foundry and the mapmaker puts together a working map as well as functional XML while seeking input from the foundry community and managers.
Stabilize - This is when feedback from Q&A is used to make the project complete. I see this as the tweaking of the map and gameplay so that it can advance to the final forge and begin beta testing.
Deliver - This is when a project is complete and can move into a maintenance cycle that has its own process. I see this as when a map as been quenched and the beta tag removed.
Hope this helps ... please ignore it if you think I am crazy =)
--D
.
Where I work we have a implemented a lot of process. I thought I would share my thoughts on process and the foundry just a bit. And my thoughts on stages of map development in comparison with how the project might be managed if there were a project manager assigned to it. This may be quite boring but you might find some information here that will help you if you are working on a map. Mind you this is just my thoughts on how these principles might be applied and I am not saying you should follow any of this. Process works differently for everyone and should be adapted to your personal style.
The RACI matrix
A Responsibility Assignment Matrix (RAM), (also known as RACI matrix or Linear Responsibility Chart (LRC)), describes the participation by various roles in completing tasks or deliverables for a project or business process. It is especially useful in clarifying roles and responsibilities in cross-functional/departmental projects and processes.
Responsible
Those who do the work to achieve the task. There is typically one role with a participation type of Responsible, although others can be delegated to assist in the work required... I see this as the person who submitted teh map idea and has taken the lead on the map's construction. This would also include people who assist such as a graphic artist or an XML expert.
Accountable (also Approver or final Approving authority)
Those who are ultimately accountable for the correct and thorough completion of the deliverable or task, and the one to whom Responsible is accountable. There must be only one Accountable specified for each task or deliverable... I see this as the foundry staff who decide when a map is ready to move from ideas, to drafts, to foundry, to final forge, and ultimately become quenched.
Consulted
Those whose opinions are sought; and with whom there is two-way communication... I see this as you, the players, mapmakers, and founder staff with who I communicate about the map and gameplay etc...
Informed
Those who are kept up-to-date on progress, often only on completion of the task or deliverable; and with whom there is just one-way communication... I see this as the people who have chosen to read this thread without commenting or receive updates on the map's progress through the newsletter.
Project Management
Initiate - This is the phase where a project begins. In foundry terms this would be when a mapmaker posts a map idea in the map ideas message board and seeks input.
Elaborate - This is the phase where a project takes shape and a set of plans are created so that the project can move on and work on it can happen. In the foundry this happens in the ideas forum and continues into the draft forum as a map idea takes shape.
Construct - In this phase the work of a project is begun. There is usually a Q&A overlap starting mid-phase. In founder terms this is when a map moves to the main foundry and the mapmaker puts together a working map as well as functional XML while seeking input from the foundry community and managers.
Stabilize - This is when feedback from Q&A is used to make the project complete. I see this as the tweaking of the map and gameplay so that it can advance to the final forge and begin beta testing.
Deliver - This is when a project is complete and can move into a maintenance cycle that has its own process. I see this as when a map as been quenched and the beta tag removed.
Hope this helps ... please ignore it if you think I am crazy =)
--D
.