Speed Indicators-Project Management on Steroids (Scope/Planning)

Scope the Project

So the business/stakeholder has defined the scope of the project, the scope of the project is the set of objectives for the project that will be undertaken. All of the business goals will be derived from the requirements put forth by the business, and the objectives are derived from the requirements. Goals of the business)-Requirements gathered from the business)-Objectives (of the project). That’s why the project was kicked off initially to meet the objectives of the business/stakeholders.
As the project plan comes together you are going to have to break down the scope of the project into smaller pieces all the way down to the individual task level. When you share the scope of the project completely with your team you will need to give them the full insight into the development the project. Bring everyone together to detail the scope from inception to completion and try to use some kind of media (power-point, visio, and white-boards) to convey the new application. I find using media from beginning to end of the project life-cycle will help the team in seeing the big picture, basically what this project is intended to accomplish for the business. I use power-point to convey ideas and examples but try to not to create huge presentations I use the application more to facilitate communication, ideas, brainstorming for projects; here are some of my presentations.


Plan the Project

Once the team has seen the complete scope of the project you will need to indentify the skill sets that will be needed to complete the project. Try not to add all team members to all planning sessions because in my experience it is a receipt for things going awry. All of your team members have to be involved in at least one of more of the meetings so they feel they are contributing to the overall success of the project.
Schedule your meeting for no more than an hour, planning for a project is specialized focused and has objectives. Once completed you should have some deliverables defined in the scope. Try to detail each team session, what is the outcome? The outcome from these sessions will fit into your project plan, and documentation from the sessions, (activities, tasks, time estimates) can be added. Don’t forget to perform risk analysis for each task you come up with, there is no better time to perform risk analysis often and early in the project.
One last thing try to look for a leader amongst you team that in the future will be able to lead future sessions. Just coach them on how, what, where, you want the sessions to be run. Also keep the sessions on a schedule and focused on pieces of or one objective for the meeting, this way you will not need to include team members who do not have the skill set and you can keep the project moving forward. Attend, but don’t try to attend EVERY session, share insights and successes that other sessions have achieved and this will keep your team informed. Face-To Face communication is vital for a successful project.
You can then bring the whole team together when all sessions are completed and have the leaders present there overview of their objectives and how they are going to complete them. Multiple Individual Plans=Full Scope, now you have plans that will be needed to meet all of the projects objectives.

Popular posts from this blog

Burn Down vs. Gantt Chart

Agile/Scrum- Communication Plans

Cost Control Agile/Traditional