Agile Project Management

Project management is a combination of planning, organizing and managing resources in order to produce defined objectives. Whether you are initiating a new venture, expanding an existing one, or responding to an urgent need running your own personal projects can be stressful.  Some refer to this as ‘The Blackberry Effect’. From the sample activities that I have seen this series cover many of the skills that we need in order to lead a productive and successful project. As outlined on a good apmg agile pm course.

In this fourth Activity, we are going to look into project management using a technology where we’ll be exploring the concepts of time management, project architecture and how to create an effective project standard

While you read this excerpt you should keep in mind that the methods and processes you are about to implement need to be accepted and practiced by your clients/customers.

The project manager’s day typically begins with theGfour – Plan:

1. Surround yourself with a well developed plan

2. Delegate the reporting to a consultant

3. Define the customer specifications

4. Understand and apply the eight components of project management

The plan would consist of the following sections.


You should phrase your purpose clearly and succinctly in the introduction of your organization’s project.  Try to state the purpose in as few words as possible yet provide the most useful as possible.

2. Objective

Only include objectives that represent the visionary view of your organization, and do not task because failure to include objectives could lead to more ineffective communication to all the parties involved.

3. Organization

Organize the information involving the prospective project in a way that lists all the individuals throughout the project as well as their respective titles/positions (if applicable). Prioritized folders in a 3-D, chronological order would be the most effective way to organize the information.

4. Work breakdown structure

Break the project down into individual workstations, or each separate workstation should have its own set of files.  For example, the workstations of each of the different executives should have files covering the person’s role.

5. Project scope

Ensure that you and your client define the scope of the project, and make sure that the scope is clear to everyone involved. In general, the scope will include the objectives, program goals, and deliverables.

6. Project planning

Project planning the overall plan for the project from start to finish. These could be classified as high level, medium level and low level activities.  High level activities may include major milestones that have to be completed, actions that should take place, regular review intervals, independent suppliers, monitoring items and different funding options.

7. Project Schedule

Counsel the plan as it relates to schedule. Be sure that everyone signs a wishy washy plan to ensure that everyone is on the same page.

8. Control

Manage and control all aspects of the plan efficiently.  Begin with defining the project for each project team member/team leader.  Revise as needed for individuals working out in the field, and on an ad-hoc basis according to each task/related activity.

After each activity, you will need to document it in your project documents and update your team.

You should document

This would include steps as well as duties that may be performed, and a word or two regarding why and how it fits within the overall complexity of your plan.

Writing Down

When you are done writing up, review the document frequently for variations or options, and keep a copy as your projects permanent record.

In the chronological nature of aspects of your project, project documentation will only mean the document version, therefore update and proof your document annually.

Remember to transfer the documentation to your company in the proper format so that you can easily share it with other project professionals in the same team.

When you are finished with your documents, share them with yourMALaya BAD ANDSgotten to 160 minutes attendision periods

Writing expectations into your project documents will increase the likelihood and effectiveness of you reaching your objectives

Variancethe actual application tasks and report their achievement in a schedule and associated timeline

Place a feedback form for your client’s project teams

Ensure that your customer understands your team’s solution

Reintroduce the project in a joint team meeting that ideally is in person

Reintroduce the project in a status report to your respective business

Reintroduce the project in an in-person team meeting that ideally is in online a when possible

Reintroduce the project in on-line report that integrates with your customer’s report system

Reintroduce the project in an on-line handout that is updated on-line with your customer’s team status

Reintroduce the project in a draft report that must first be reviewed and approved by all team members if not already in use.