He manako te kōura i kore ai
Wishing for the crayfish won’t bring it.
Project management is to plan and manage a project to successfully complete its goals and deliverables.
It's main purpose is to increase efficiency and the quality of your outcome!
It improves communication and collaboration by breaking down the walls between individuals and teams.
Great project management means much more than keeping things in check, delivering on time, budget, and project scope.
It creates a vision for a successful project, and gets everyone on the same page of what’s needed to stay on track for success.
When projects are managed properly there’s a huge positive impact.
ensure what is being delivered, is right, and will deliver real value.
bring leadership and direction to projects as well as clear lines of accountability.
have a clear focus & objectives and how you will execute these.
have realistic planning with proper expectations around what can be delivered, by when, and for how much.
ensure the quality of whatever is being delivered, consistently hits the mark.
ensure risks are properly managed and mitigated to avoid becoming issues.
have an orderly process making sure the right people do the right things, at the right time
have a continuous oversight so that your project’s progress is tracked and reported properly.
have intelligent and informed conversations with clients, teams mates, stakeholders, and end users. Ensuring that as the project flows between different phases of work and nothing gets forgotten about or overlooked.
learn from the successes and failures of the past.
During the design and development of an outcome you will work through an Agile development.
It is a process originally developed for software development but has applications in a wide range of design industries. Each "sprint" is broken down into a number of components which feedback into each other.
Its counterpart is the Waterfall model which is a more linear process.
Trello
Trello is a free project management system
Freedcamp
HacknPlan
Examples of project management and version control tools and techniques include:
saving backup copies with a logical file naming system
using collaboration tools
using simple version control software applications
using tools or systems to plan tasks and milestones
adjusting key actions and tasks where appropriate
Requirements Gathering
The first step of a sprint is to set up the requirements for the sprint. It involves asking your customers and stakeholders what they want your system to do. At school we use the the design stage or end of sprint feedback to establish these requirements.
Design
This establishes what can be achieved with the skills of the developers. This normally establishes the plan for the sprint and what can be achieved.
Develop
This stage is all about making a part of your thing. You should have broken your project down into small manageable pieces so they can be tackled by a single developer.
Test
As each task is completed it is tested in isolation and in the whole process. This testing could include internal as well as external feedback and trialing.
Deploy
At the end of each sprint the product is released. In software engineering this is normally a patch or version.
You should start your project with headings for:
Future Checkpoints
To Do
Doing
Done
And then populate this with tasks.
As you work on and complete tasks you should move the task to the appropriate section.
It can also be helpful to colour code tasks for specific members or related tasks.
At the end of each sprint/checkpoint you should archive your tasks.
During each review you should screenshot your chosen project management tool and add it to the Development Log
During the first sprint you should finish the basic requirements of your project. The users should be able to give you feedback on how your project works and looks even if everything is not working 100%
During the second sprint it should be all about working up your product to make it as refined as possible. The core parts should be finished so that all the parts work well together.
During the last sprint it should be all about making your product as exciting as possible. Making sure it looks the best it can with all the bells and whistles.
Decomposing the outcome into smaller components
Organise your work into lots of bite sized pieces. Each task you should plan to just a few lessons/hours to complete. When you complete one of the tasks you need to collect some evidence in the form of a photo, screenshot or similar.
Examples of good tasks
Sketch up main character
3d model main character in Blender
Colour 3d main character
Rig 3d model
Basic walk animation
Examples of bad tasks
Make main character
Create action scene