This presentation will showcase the hows and whys of project prioritization, planning and management.
The goal of this process is to: Analyze Objectively examine, discover and/or explore your project on a deep level Optimize Use your aforementioned analysis to; Streamline your project, process, pipelines and more Improve your Human Capital and productivity Manage your project and workload
Prioritize Use your optimization discoveries to; Min/Max your project Complete low cost, high reward tasks first Effectively lead self-managing teams Effectively manage & complete tasks, deadlines, milestones and roadmaps Dominate Roll all these processes together to become a highly functional, cohesive and in demand team and/or individual
Using a project management tool is a must! Using a software tool for project management IS a must There are a lot of great options out there, but the two best I have found are; Psyberfire http://psyberfire.com/ Trello https://trello.com/ Others There are others too. I would suggest you do your own research into what fits your needs as an individual/team best and make an objective decision
In order, the following are the levels of hierarchy when using this system Project Level Super Epic Epic Feature Task Chore
Overall project/vision/goal If you are building software, this would be your full suite If you are building a game, this would be your game If you are using this system to plan your life, then this could be your “2016 year of life” How you define your project is dependant on what you are using this system for Highest overall level This level is the hierarchical highest level possible in this system There is no higher level
Highest breakdown level This is the highest level at which you can begin breaking down your project Largest component(s) of your project These are your largest hierarchical components of your project If you are building a role playing game, this could be your entire RPG system If you are using this for your “2016 life planning” this could be planning to attend/return to school Typically unachievable by a meta In a team setting, super Epics are usually not achievable by a single meta alone Too many meta teams work needs to go into this to make it happen. Using the RPG example, the following will need to go into this Super Epic to make it work Designing out each function aspect of the RPG system i.e., character stats, perks, leveling, NPC interactions, items, etc…. Designing the UI/UX for these systems Creating sound effects for said systems Creating the actual tech behind aforementioned system Creating the art elements for the above etc, etc...
Second highest breakdown level This is the second highest level at which you can begin breaking down your project Second largest component(s) of your project These are your second largest hierarchical components of your project
May be achievable by a single meta
Why and how we effectively prioritize
● Highest breakdown level
● Largest component(s) of your project
● Typically unachievable by a meta
● Second highest breakdown level
● Second largest component(s) of your project
● May be achievable by a single meta
● Third highest breakdown level
● Third largest component(s) of your project
● Will be achievable by a single meta
● Second smallest breakdown level
● Second smallest component(s) of your project
● May be achievable by a single individual
● Smallest breakdown level
● Smallest component(s) of your project
● Will be achievable by a single individual
● Poker planning/Planning Poker
● Prioritization method
● Typically uses fibonacci sequence, but not required
● Analyze Effort, Doubt and Complexity
● Must have consensus if in a team setting
● Start with your Super Epic(s) and begin your Poker Planning
● How much Effort will this item take?
● Do you doubt completion of this item?
● Can it be done on time or at all?
● Do you doubt the skill level(s) of member(s) involved?
● Do you doubt that the necessary resources are available?
● How complex is the task?
● Difficulty level?
● Barrier to entry?
● Hardships encountered?
● Each item analyzed;
● Combine the numbers for Effort, Doubt and Complexity
● If the value is that of a feature or above, break it down further!
● If not, assign create a card in your chosen software and move on
● Rinse and repeat until your project is fully mapped out
● Prioritize based off of the value
● What is a sprint?
● Sprint duration?
● Task/Chore Management
● Acceptance Criteria