A Presentation on Solutions for Project Managers such as useful tools that can help you in the process of human resource allocation, as well as an example of Scrum framework to the rescue.
Strategies for Unlocking Knowledge Management in Microsoft 365 in the Copilot...
A presentation on Agile Methodology for Project Managers
1. A Presentation on Solutions to
Stated Tasks
Presented By Adeolu Adeleye
2. TASK 1
One of the core responsibilities of a PM Officer is to assign employees to the most
suitable projects. Fortunately, there are many useful tools that can help you in the
process of human resource allocation.
1. Please choose one tool which you find most helpful. Explain why it is useful and
describe the specific criteria which you used to evaluate it.
2. Prepare a step by step description of how you would organize a process based
on this tool.
3. The one tool I have chosen.
One tool I have found the Agile Methodology very helpful.
4. The Agile Methodology has proven
useful over the years because;
The Agile Methodology has its basis from a set of ideals which modified and
tailored to overcome the shortfalls of the traditional project management.
The ideas have been analyzed, modified and evaluated over the years with
considerations from academic studies combined with the real-world
experiences.
Research from the Harvard Business School found that it was not possible to
plan extremely large projects, and that it was impossible to make changes to
the project in the later stages. This can be seen in many governments’ IT
projects where the implemented system is over budget, years late and does
not fulfil the original needs. The Agile movement came into being to address
these flaws.
5. The specific criteria I have used
to evaluate this methodology.
The level of Skill required,
The timeline for delivery,
The flexibility
The opportunity of seamless and possible changes
In an Agile Project, the project teams are often small but highly skilled, the
timelines are very short with delivery of projects within very short
timeframes, allows for flexibility in requirements and changes to the original
requirements are dealt with quickly.
6. Preparation of a step by step
description of how I would organize a
process based on this tool.
Step 1: Planning
• Gather information about and related to the project,
• Break the projects into tasks as smaller projects,
• Prepare plan, time and cost to carry out the work
Step 2: Analysis
• Define budget,
• Define iteration span time
Step 3: Design
• Break down a task,
• Test scenario preparation for each task,
• Regression automation framework
7. Preparation of a step by step
description of how I would organize a
process based on this tool (Cont’d)
Step 4: Execution
• Coding,
• Testing,
• Mid iteration review,
• End of iteration review
Step 5: Wrapping
• Small releases,
• Demos and reviews,
• Develop outputs based on customer need,
• Process improvement on an end of an iteration.
8. Preparation of a step by step
description of how I would organize a
process based on this tool (Cont’d)
Step 6: Closure
• Pilot launch to test the product,
• Give training,
• Product launch,
• Production support
9. TASK 2
Our client needs a front-end developer for a new project. You have
suggested that John Doe (profile is included here) would be the best man for
the job. However, the customer has some doubts about this candidate. From
the client’s point of view there are a few problematic issues:
John doesn’t have any technical education,
John doesn’t have enough programming experience,
John’s English skills are not up to the client’s expectations,
The client generally feels that John is not a good fit for the project
How would you encourage the client to accept this candidate, given that he is
not fully convinced.
10. With regards to the project and its clearly stated identified flaws, I would employ the
Scrum framework. Instead of having a formulated project management methodology
where roles are specifically defined and the process rigidly applied, this framework would
help John Doe and I, make decisions as a team and have the project under my
supervision throughout the timeline.
The three defined roles we would adopt for this project are listed and explained below;
• Product Owner – this person would decide on what product has to be delivered in the
stated timeline. With the vision to get the team to build the right product.
• Development team – this is John, as he will build the product and demonstrate the
product to the product owner.
• Scrum master – this is me, who will oversee the processes, ensure that the process is
working and improve the process if required.
With John Doe’s profile portraying skills including: Technology stack of HTML, CSS,
jQuery, Photoshop, WordPress, PHP, Kanban, Extreme Programming and Adaptive
Project Framework, implementing the project would not be difficult and this would be
explained to the product owner as this are the required skills for front-end developer.
11. The Scrum Events, which is an event that will give the development team and
the product owner the opportunity to share information so that there is on-
going communication and continual project update where the product owner
would experience John Doe’s improvement.