This course is designed to help you discover foundational project management terminology and gain a deeper understanding of the roles and responsibilities of a project manager and team members.
·
This is a 16-hour course offered on Saturdays from 12-4 pm over 4 weeks. For a more specialized and personalized course, contact Ms. Johnnetta Hines or reach out on your Contact Page.
Our services focus on: Read More Below
Initiating – authorizing the project or phase.
Planning – defining and refining objectives, setting a course of action.
Executing – integrating resources to carry out the approved plan.
Monitoring and Controlling – identifying and managing variances, taking corrective action.
Closing – formalizing acceptance and bringing a phase or a project to an orderly completion and transition.
Project Management Body of Knowledge (PMBOK) Areas
Our services focus on: Read More Below
A Brief Description of the Project Management Knowledge Areas
Integration – Coordination and bringing all the pieces together.
Scope Management – Determining what work must be done. Setting clearly defined project objectives. Creating the WBS.
Time Management – Activity definition, sequencing, duration estimating, and schedule development.
Cost Management – estimating costs, budgeting costs over time, and controlling costs through the project life cycle.
Quality Management – establishing a quality policy, developing quality assurance processes and controlling the quality of all project deliverables.
Human Resources Management – Identifying project stakeholders, developing the project team, motivating the team, management styles, and organizational structure.
Communications Management – Distributing information correctly and to the appropriate stakeholders, performance reporting, managing stakeholders.
Risk Management – risk identification, qualitative analysis, quantitative analysis, response planning and risk monitoring and control.
Procurement Management – planning purchases and acquisitions, contracting, selecting sellers, contract administration, project closure.
12 Clarifying Principles Flow Down from the Manifesto
The principles are: Read More Below
Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
Welcome changing requirements, even late in development. Agile processes harness change for the competitive advantage.
Deliver working software frequently, from a couple of weeks to couple of months, with a preference to the shorter timescale.
Businesspeople and developers must work together daily throughout the project.
Build projects around motivated individuals. Give them the environment and support the need, and trust them to get the job done.
The most efficient and effective methods of conveying information to and within a development team is face-to-face conversations.
Working software is the primary measure of progress.
Agile processes promote sustainable development. The sponsors, developers and user should've able to maintain a constant pace and indefinitely.
Continuous attention to technical excellence and good design enhances agility.
Simplicity - the art of maximizing the amount of work not done - is essential.
The best architectures, requirements, and designs emerge from self-organizing trams.
At regular intervals, the team reflects on how to become ore effective, then tunes and adjusts its behavior accordigly.