GROUP THREE- PPDI

PRESENTATION II
THEORETICAL APPROACHES TO PROJECT
IMPLEMENTATION (PLANNING MODELS, ANALYSIS OF
PROJECT CYCLE, GHANT CHART, NETWORK PLANNING)

Group Members
1. Mr. Walter Ochanda (Ref:11035732020)
2. Mr. Moses Raymond Ndambuki (Ref:11093822021)
3. Mr. Ngitelejio Ekalale Danson (L83/57899/2021)
4. Mr. Noah Limo

25th April 2021

 Presentation Outline
 Definition of Project Implementation;
 Theoretical approaches to project
implementation and applicable principles
 Explore the Project implementation
process;
 Discuss merits and demerits of each
planning model
 Before drawing a conclusion.
 Project Design: A Definition
The Cambridge English Dictionary defines Implementation as “the
process of putting a plan into action or the process of starting to use
something”. The process of executing projects is quite complex and,
involves a unclear critical balance of a number of elements.

Implementation science

Is the scientific study of methods to promote the systematic uptake of

research findings and other Evidence Based Practices (EBPs) into
routine practice to improve the quality and effectiveness of health
services (EcclesMP, m et al, 2006:1), early implementation research
was largely based on observations and did not put into consideration
the theoretical underpinnings of implementation.
 THEORIES, MODELS AND FRAMEWORKS IN
IMPLEMENTATION SCIENCE
Theory: The oxford dictionary define theory as a supposition or a
system of ideas intended to explain something, especially one based
on general principles independent of the thing to be explained.
Frankfort-Nachmias et al., (1996), defined theory as a set of analytical
principles or statements designed to structure our observation,
understanding and explanation of the world.
Model: is a deliberate simplification of a phenomenon or a specific
aspect of a phenomenon. Models need not be completely accurate
representations of reality to have.
Framework: Sabatier A., (2007) advanced that a framework denotes a
structure, overview, outline, system or plan consisting of various
descriptive categories such as concepts, constructs or variables, and
the relations between them that are presumed to account for a
phenomenon.
Theoretical approaches implied in implementation science can be
delineated as below
 Implementation Theories
Normalization process theory
Implementation Theories Cont…
Absorptive capacity theory
An example of absorptive capacity model
COM-B (Capacity, Opportunity, Motivational
& Behavior)
 Implementation Theories Cont…
Implementation Climate theory
Theory of organizational readiness for change
Project Management Models
A framework is something that informs you how often you
can discuss progress, how to document results, how to
communicate and so on. There are several project
management models and a few will be discussed below.

The main and key project models include:

•Waterfall model
•The incremental build mode
•The Iterative model
•Prototyping model
•Agile model
•Rapid application development (RAD) model
WATERFALL MODEL
 Advantages of the Waterfall Model
• Simple and easy to understand and use
• Easy to manage due to the rigidity of the model. Each phase has specific deliverables and a review
process.
• Phases are processed and completed one at a time.
• Works well for smaller projects where requirements are very well understood.
• Clearly defined stages.
• Well understood milestones.
• Easy to arrange tasks.
• Process and results are well documented.

Disadvantages of Waterfall Model

• Disadvantages
• No working software is produced until late during the life cycle.
• High amounts of risk and uncertainty.
• Not a good model for complex and object-oriented projects.
• Poor model for long and ongoing projects.
• Not suitable for the projects where requirements are at a moderate to high risk of changing. So, risk
and uncertainty is high with this process model.
• It is difficult to measure progress within stages.
• Cannot accommodate changing requirements.
• Adjusting scope during the life cycle can end a project.
• Integration is done as a "big-bang. at the very end, which doesn't allow identifying any technological
or business bottleneck or challenges early.
THE INCREMENTAL BUILD MODEL
 THE INCREMENTAL BUILD MODEL
ADVANTAGES AND DISADVANTAGES

• Advantages
• After each iteration, regression testing should be conducted
• It is generally easier to test and debug than other methods of software
development because relatively smaller changes are made during each
iteration
• Customer can respond to features and review the product for any
needed or useful changes.
• Initial product delivery is faster and costs less
• Disadvantages
• Resulting cost may exceed the cost of the organization.
• As additional functionality is added to the product, problems may arise
related to system architecture which were not evident in earlier
prototypes.
ITERATIVE MODEL
ITERATIVE MODEL ADVANTAGES AND
DISADVANTAGES
Advantages
Some working functionality can be developed quickly and early in the life cycle
Results are obtained early and periodically
Parallel development can be planned
Progress can be measured
Less costly to change the scope/requirements
Testing and debugging during smaller iteration is easy
Easier to manage risk - High risk part is done first
Risk analysis is better
Disadvantages
More resources may be required
More management attention is required
System architecture or design issues may arise because not all requirements are
gathered in the beginning of the entire life cycle
Defining increments may require definition of the complete system
Not suitable for smaller projects
Management complexity is more
 
 PROTOTYPING MODEL
 PROTOTYPING MODEL ADVANTAGES AND
DISADVANTAGES
• Advantages
• Customers get a say in the product early on,
increasing customer satisfaction
• Missing functionality and errors are detected easily
• Prototypes can be reused in future, more complicated
projects
• It emphasizes team communication and flexible design
practices
• Users have a better understanding of how the product works
• Quicker customer feedback provides a better idea of
customer needs
• Disadvantages
• The model is more costly in terms of time and money when
compared to alternative development methods, such as the
spiral or waterfall
AGILE MODEL
AGILE MODEL ADVANTAGES AND DISADVANTAGES
Advantages
Is a very realistic approach to software development.
Promotes teamwork and cross training.
Functionality can be developed rapidly and demonstrated.
Resource requirements are minimum.
Suitable for fixed or changing requirements
Delivers early partial working solutions.
Good model for environments that change steadily.
Minimal rules, documentation easily employed.
Enables concurrent development and delivery within an overall planned context.
Little or no planning required.
Disadvantages
Not suitable for handling complex dependencies.
More risk of sustainability, maintainability and extensibility.
An overall plan, an agile leader and agile PM practice is a must without which it will not
work.
Strict delivery management dictates the scope, functionality to be delivered, and adjustments
to meet the deadlines.
Depends heavily on customer interaction, so if customer is not clear, team can be driven in
the wrong direction.
There is a very high individual dependency, since there is minimum documentation
generated.
Transfer of technology to new team members may be quite challenging due to lack of
documentation.
RAPID APPLICATION DEVELOPMENT(RAD) MODEL
 RAPID APPLICATION DEVELOPMENT(RAD) MODEL
ADVANTAGES AND DISADVANTAGES
Advantages of the RAD Model
•Changing requirements can be accommodated.
•Progress can be measured.
•Iteration time can be short with use of powerful RAD tools.
•Productivity with fewer people in a short time.
•Reduced development time.
•Increases reusability of components.
•Quick initial reviews occur.
•Encourages customer feedback.
•Integration from very beginning solves a lot of integration issues.
•disadvantages of the RAD Model
•Dependency on technically strong team members for identifying business requirements.
•Only system that can be modularized can be built using RAD.
•Requires highly skilled developers/designers.
•High dependency on modeling skills.
•Inapplicable to cheaper projects as cost of modeling and automated code generation is very high.
•Management complexity is more.
•Suitable for systems that are component based and scalable.
•Requires user involvement throughout the life cycle.
•Suitable for project requiring shorter development times
PRINCE2:
OTHER MODELS
•Is a framework for the development and support of Information
Technology systems through a structured project management
approach.
•Has very formalized roles, responsibilities and channels of
communication for each aspect of the project.
•It is ideal for breaking down large and complex projects.

Log Frames (Logical Frameworks)

•It was developed as a tool for strategic planning and it is used to
outline how projects goals, objectives, outputs, Activities & indicators
will be managed on the project
PROJECT LIFE CYCLE
 Execution Phase
The Execution Phase typically involves:
- Strategic planning
- Implementation planning
It is important to note that an implementation plan is created at this
level to guide the project execution process. Every implementation
plan comprises of some key components that need to be analyzed and
thought-through before communicating the plan with the project
team:
•Outline Goals/Objectives
•Assign Responsibilities
•Implementation Schedule
•Resource Allocation
•Define Metrics
•Contingency Plan
•Training Plan
•Communication plan
•Closure plan
 Methods of comparing planned and actual
performance
1. Units Completed
2. Incremental Milestone
3. Start/Finish
4. Supervisor Opinion
5. Cost Ratio
6. Weighted or Equivalent Units
Gantt Chart Evolution
 Why use a Gantt chart in project management?
• You will always know what’s going on in your projects provides a total
overview of the project from start to finish, the members involved in each
step, and all the tasks required to complete the project.
• Easily communicate the project plan with your team because everyone has
access to information on task dates and important milestones
• Prevent resource overload: you can delegate tasks to different people and
align team resources without overloading people in the process
• Track the progress of your project: you have the ability to check in and see
how the project is progressing
• Free up brain space: There’s no need to stress about remembering the next
steps, who's doing what, or what may have been forgotten
• Give your team more clarity and motivation
• Provide accountability and coaching
• Identify ways to reduce costs
• Complete projects ahead of schedule
 References
• Burton J., (1990). Conflict: Human Needs Theory, (ed.), St. Martin‘s Press, New York.
• Fondahl J., 1980. Network Techniques for Project Planning, Scheduling, and Control. In: Handbook of Construction Management and
Organization. Frein, Joseph P. (ed.). Van Nostrand Reinhold, New York.
• Fugate M. and Knapp J. (1998) The Development of Bodies of Knowledge in the Professions. Appendix B in: Project Management
Institute. 1999. The Future of Project Management. Newtown Square.
• Geert G., (1980), Motivation, Leadership and Organization: Do American Theories Apply Abroad?, Available Online at:
http://cultureready.org/sites/default/files/publications/Motivation%20Leadership%20and
%20Organization_Hofstede_1980%5B1%5D.pdf , Accessed on: April 23, 2021.
• Johnston B. & Brennan, M., (1996) Planning or Organizing: the Implications of Theories of Activity for Management of Operations.
Omega, Int. J. Mgmt. Sc., Vol. 24, No. 4, 367-384
• Kharbanda P and Pinto K., (1996)What Made Gertie Gallop: Learning from Project Failures? Van Nostrand Reinhold.
• Kosheka L. and Greg H., (2002), Theories of Project management theories: Explanation to novel Theories, Available online at:
https://iglcstorage.blob.core.windows.net/papers/attachment-8ef324db-750a-40c3-9c17-273db32b54e2.pdf , Accessed on: March 16,
2021.
• Loid, D., (1999) Limitations of the Project Monitoring Concept. Construction Economics and Organization. Proceedings of the Nordic
Seminar on Construction Economics and Organization, 12 – 13 April, Gothenburg. Department of Management of Construction and
Facilities, Chalmers University of Technology.
• Maslow’s theory of Needs, Available online at: http://www.eajournals.org/wp-content/uploads/Abraham-Maslow%E2%80%99s-
Hierarchy-of-Needs-and-Assessment-of-Needs-in-Community-Development.pdf , Accessed on: March 16, 2021.
• PMBOK, available online at: https://www.pmi.org/pmbok-guide-standards/foundational/pmbok , Accessed on: March 17, 2021
• Porter M. (1985) Competitive Advantage. The Free Press.
• Starr M., (1966) Evolving concepts in production management. In: Readings in production and operations management, Elwood S.
Buffa (ed.). John Wiley, New York.
• Whetten A. (1989) What Constitutes a Theoretical Contribution? Academy of Management Review, Vol. 14, No. 4, pp. 490 - 495
• Chambers, R. (1992). Rural Appraisal: Rapid, Relaxed and Participatory. Institute of Development Studies Discussion Paper 311.
Sussex: Help
• International Institute for Environment and Development, Sustainable Agriculture Program: (1991-Present). RRA Notes (Now titled
PLA Notes). United Kingdom.
• Thei J and Grady H. (1991). Participatory Rapid Appraisal for Community Development: London: Save the Children Fund.