Thanks to visit codestin.com
Credit goes to www.scribd.com

0% found this document useful (0 votes)
82 views52 pages

Week 4

This document discusses and compares various project management methodologies: 1. It introduces 8 methodologies - Adaptive Project Framework, Agile Software Development, Crystal Methods, Dynamic Systems Development Model, Extreme Programming, Feature Driven Development, Information Technology Infrastructure Library, and Joint Application Development. 2. For each methodology, it provides a brief overview of its key aspects, principles, and phases. 3. It compares the strengths and weaknesses of some methodologies to help understand how they differ and which problems they best address.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
82 views52 pages

Week 4

This document discusses and compares various project management methodologies: 1. It introduces 8 methodologies - Adaptive Project Framework, Agile Software Development, Crystal Methods, Dynamic Systems Development Model, Extreme Programming, Feature Driven Development, Information Technology Infrastructure Library, and Joint Application Development. 2. For each methodology, it provides a brief overview of its key aspects, principles, and phases. 3. It compares the strengths and weaknesses of some methodologies to help understand how they differ and which problems they best address.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 52

Week 04:

Project Management Methodologies


This course is designed to introduce and explore the basic concepts and practices of project management and help students understand how to plan and
manage IS projects successfully. Throughout the course, students will be asked to utilize course concepts, methodologies, and tools while utilizing technology
applications and addressing real-world problems. Students will learn the skills necessary to define project scope, create workable project plans, and manage
projects with quality, budget, and schedule in mind. The course is structured around the key phases of project lifecycle, including initiating a project,
developing project plans, executing and managing a project, and closing out a project. In addition, students will be taught how to identify and address the
change management and political issues associated with project management.
Week 04: Project Management Methodologies

Course Learning Outcomes:

1. Understand the different methodologies of project


management
2. Compare the different methodologies of project management
by its weaknesses, strengths, principles and phases.
3. Appreciate the functions of each methodologies in the project
management that cater the needs of different projects across
different business domains
Week 04: Project Management Methodologies

INTRODUCTION
• In order to achieve goals and planned results within a defined
schedule and a budget, a manager uses a project.
• A methodology is a model, which project managers employ
for the design, planning, implementation and achievement of
their project objectives.
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
1. Adaptive Project Framework

Figure 4.1 The Adaptive Project Framework


(Photo taken from: https://newline.tech/blog/adaptive-project-framework-as-a-method-of-non-traditional-project-management/)
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
1. Adaptive Project Framework
• The project scope is a variable
• Time and the cost are constants for the project.
• The purpose of this method is to harmonize processes
and ongoing changes in the project, business climate and
markets.
• It does not involve templates and a list of pre-prepared
decisions.
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
1. Adaptive Project Framework
Seven independent factors that affect the project:
• Characteristics of the environment in which the project will
be implemented
• Characteristics of the project itself
• The life cycle of a business process
• Life cycle of project management
• Competence of the project team
• Customer Vision
• Quality of equipment or software
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
2. Agile Software Development

Figure 4.2 The Agile Software Development Cycle


(Photo taken from: https://medium.com/@jowits/agile-software-development-3adc00c81a8)
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
2. Agile Software Development
• It is for a project that needs extreme agility in requirements.
• The key features of agile are its short-termed delivery cycles
(sprints), agile requirements, dynamic team culture, less
restrictive project control and emphasis on real-time
communication.
• Refers to software development methodologies centered round
the idea of iterative development, where requirements and
solutions evolve through collaboration between self-organizing
cross-functional teams.
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
2. Agile Software Development
• The ultimate value in Agile development is that it enables
teams to deliver value faster, with greater quality and
predictability, and greater aptitude to respond to change.
• Scrum and Kanban are two of the most widely used Agile
methodologies.
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
3. Crystal Methods.

Figure 4.3 The Crystal Method


(Photo taken from: https://activecollab.com/blog/project-management/crystal-methods)
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
3. Crystal Methods.
• This method focuses more on team communication, team
member skills, people and interaction.
• It is an agile software development approach that focuses
primarily on people and their interactions when working on
a project rather than on processes and tools.
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
3. Crystal Methods.
• Generally, they are characterized by colors, according to the
number of people involved in the project:
• Clear - for teams of 8 or fewer people
• Yellow - for teams of 10-20 people
• Orange - for teams of 20-50 people
• Red - for teams of 50-100 people
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
4. Dynamic Systems Development Model (DSDM)

Figure 4.4 Dynamic Systems Development Method (DSDM)


(Photo taken from: https://airbrake.io/blog/software-development/dynamic-systems-development-method-agile)
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
4. Dynamic Systems Development Model (DSDM)
• This method emphasizes more on the active user
involvement during the project life cycle.
• It is an agile project delivery framework, primarily used as a
software development method.
• The DSDM framework can be implemented for agile and
traditional development processes.
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
5. Extreme Programming (XP)

Figure 4.5 The Extreme Programming


(Photo taken from: https://www.infoq.com/articles/implementing-xp-methodology/)
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
5. Extreme Programming (XP)
• XP emphasizes on fine scale feedback, continuous process,
shared understanding and programmer welfare.
• There is no detailed requirements specification or software
architecture built.
• It is an agile software development framework that aims to
produce higher quality software, and higher quality of life
for the development team.
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
6. Feature Driven Development (FDD)

Figure 4.6 The Feature Driven Development (FDD)


(Photo taken from: https://aist.global/en/use-a-feature-driven-development)
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
6. Feature Driven Development (FDD)
• Focused on simple and well-defined processes, short
iterative and feature driven delivery cycles.
• It is an agile framework that, as its name suggests, organizes
software development around making progress on features.
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
6. Feature Driven Development (FDD)
FDD’s strengths include:
• Simple five-step process allows for more rapid development
• Allows larger teams to move products forward with continuous
success
• Leverages pre-defined development standards, so teams are able to
move quickly
FDD’s weaknesses include:
• Does not work efficiently for smaller projects
• Less written documentation, which can lead to confusion
• Highly dependent on lead developers or programmers
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
7. Information Technology Infrastructure Library (ITIL)

Figure 4.7 The Information Technology Infrastructure Library (ITIL) Framework


(Photo taken from: https://managementmania.com/en/itil-information-technology-infrustructure-library)
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
7. Information Technology Infrastructure Library (ITIL)
• ITIL covers a broad aspect of project management which starts from
the organizational management level.
• It is a framework designed to standardize the selection, planning,
delivery and maintenance of IT services within a business.
• The goal is to improve efficiency and achieve predictable service
delivery.
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
7. Information Technology Infrastructure Library (ITIL)
• ITIL covers a broad aspect of project management which starts from
the organizational management level.
• It is a framework designed to standardize the selection, planning,
delivery and maintenance of IT services within a business.
• The goal is to improve efficiency and achieve predictable service
delivery.
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
8. Joint Application Development (JAD)

Figure 4.8 The Phases of Joint Application Development


(Photo taken from: https://study.com/academy/lesson/joint-application-development-definition-phases-methodology.html)
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
8. Joint Application Development (JAD)
• It is a software development approach which engages the client
and/or the end users for designing and developing the system.
• Phases of JAD
a. Define Specific Objectives
b. Session Preparation
c. Session Conduct
d. Documentation
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
8. Joint Application Development (JAD)
• Benefits of Using JAD Model
a. Improved Delivery Time
b. Cost Reduction
c. Better Understanding
d. Improved Quality
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
9. Lean Development (LD)

Figure 4.9 The Lean Development (LD)


(Photo taken from: https://cdn.outsource2india.com/software/mobile-applications/images/lean-development-methodology.jpg)
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
9. Lean Development (LD)
• Lean development focuses on developing change-tolerance
software.
• It is an agile framework based on optimizing development time and
resources, eliminating waste, and ultimately delivering only what
the product needs.
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
9. Lean Development (LD)
LSD’s strengths include:
• Streamlined approach allows more functionality to be delivered in less time
• Eliminates unnecessary activity, and as a result can reduce costs
• Empowers the development team to make decisions, which can also boost
morale
LSD’s weaknesses include:
• Heavily depends on the team involved, making it not as scalable as other
frameworks
• Depends on strong documentation, and failure to do so can result in
development mistakes
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
10. PRINCE2

Figure 4.10 The Prince 2 Methodology


(Photo taken from: https://www.axelos.com/best-practice-solutions/prince2/what-is-prince2)
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
10.PRINCE2
• This methodology is based on eight high-level processes.
• Projects in Controlled Environments (more commonly known as
PRINCE2) is the most widely practiced project management
methodology worldwide, used by teams in over 150 countries.
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
10.PRINCE2
• The PRINCE2 method is built on the following 7 principles:
1. Projects must have business justification.
2. Teams should learn from every stage.
3. Roles and responsibilities are clearly defined.
4. Work is planned in stages.
5. Project boards "manage by exception."
6. Teams keep a constant focus on quality.
7. The approach is tailored for each project.
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
11. Rapid Application Development (RAD)

Figure 4.11 The Rapid Application Development Model


(Photo taken from: https://www.wavemaker.com/rapid-application-development-vs-traditional-sdlc/)
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
11.Rapid Application Development (RAD)
• This methodology focuses on developing products faster with
higher quality.
• Prototyping is used for getting clear requirements and re-use the
software components to accelerate the development timelines.
• The process of writing the software itself involves the planning
required for developing the product.
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
11.Rapid Application Development (RAD)
• The advantages of the RAD Model are as follows:
• 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.
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
11.Rapid Application Development (RAD)
• The disadvantages of the RAD Model are as follows:
• 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.
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
12. Rational Unified Process (RUP)

Figure 4.12 The Rational Unified Process (RUP) Model


(Photo taken from: http://www.objektum-modernization.com/modernization_planning.php)
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
12.Rational Unified Process (RUP)
• This is one of the first project management methodologies that
suggested an iterative approach to software development.
• It divides the development process into four distinct phases that
each involve business modeling, analysis and design,
implementation, testing, and deployment. The four phases are:
a. Inception
b. Elaboration
c. Construction
d. Transition
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
13. Scrum

Figure 4.13 The Scrum Methodology


(Photo taken from: https://zaynabzahrablog.wordpress.com/2017/10/07/scrum-methodology/)
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
13.Scrum
• The main goal of this methodology is to improve team productivity
dramatically by removing every possible burden.
• It is a lightweight process framework for agile development, and the
most widely-used one.
• An agile Scrum process benefits the organization by helping it to
• Increase the quality of the deliverables
• Cope better with change (and expect the changes)
• Provide better estimates while spending less time creating them
• Be more in control of the project schedule and state
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
14. Spiral

Figure 4.14 The Spiral Methodology


(Photo taken from: https://www.tutorialspoint.com/sdlc/sdlc_spiral_model.htm/)
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
14.Spiral
• Spiral methodology is the extended waterfall model with
prototyping.
• This method is used instead of using the waterfall model for large
projects.
• The spiral model combines the idea of iterative development with
the systematic, controlled aspects of the waterfall model.
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
14.Spiral
• The advantages of the Spiral SDLC Model are as follows:
• Changing requirements can be accommodated.
• Allows extensive use of prototypes.
• Requirements can be captured more accurately.
• Users see the system early.
• Development can be divided into smaller parts and the risky
parts can be developed earlier which helps in better risk
management.
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
14.Spiral
• The disadvantages of the Spiral SDLC Model are as follows
• Management is more complex.
• End of the project may not be known early.
• Not suitable for small or low risk projects and could be expensive
for small projects.
• Process is complex
• Spiral may go on indefinitely.
• Large number of intermediate stages requires excessive
documentation.
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
15.Systems Development Life Cycle (SDLC)

Figure 4.15 SDLC Model


(Photo taken from: https://www.tutorialspoint.com/sdlc/sdlc_overview.htm)
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
15.Systems Development Life Cycle (SDLC)
• This is a conceptual model used in software development projects.
• In this method, there is a possibility of combining two or more
project management methodologies for the best outcome.
• SDLC is a process followed for a software project, within a software
organization.
• It consists of a detailed plan describing how to develop, maintain,
replace and alter or enhance specific software.
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
15.Systems Development Life Cycle (SDLC)
• A typical Software Development Life Cycle consists of the following
stages:
Stage 1: Planning and Requirement Analysis
Stage 2: Defining Requirements
Stage 3: Designing the Product Architecture
Stage 4: Building or Developing the Product
Stage 5: Testing the Product
Stage 6: Deployment in the Market and Maintenance
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
15.Systems Development Life Cycle (SDLC)

SDLC MODELS
The following are the most important and popular SDLC models
followed in the industry:
• Waterfall Model
• Iterative Model
• Spiral Model
• V-Model
• Big Bang Model
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
16. Waterfall (Traditional)

Figure 4.16 Waterfall Model


(Photo taken from: https://www.tutorialspoint.com/sdlc/sdlc_overview.htm)
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
16.Waterfall (Traditional)
• Development lifecycle has fixed phases and linear timelines.
• This model is not capable of addressing the challenges in the
modern software development domain.
• It is also referred to as a linear-sequential life cycle model. It is very
simple to understand and use.
• In a waterfall model, each phase must be completed before the next
phase can begin and there is no overlapping in the phases.
Week 04: Project Management Methodologies

PROJECT METHODOLOGIES
16.Waterfall (Traditional)
• The sequential phases in Waterfall model are:
• Requirement Gathering and analysis
• System Design
• Implementation
• Integration and Testing
• Deployment of system
• Maintenance
Week 04: Project Management Methodologies

References and Supplementary Materials


1. Denise Canty; 2016; Agile for Project Managers
2. Kathy Schwalbe; 2015; Information Technology Project
Management
3. Margot Note; 2015; Project Management for Information
Professionals
4. Shang Gao & Lazar Rusu; 2015; Modern Techniques for
Successful IT Project Management
5. Paul Williams; 2015; Visual Project Management
Week 04: Project Management Methodologies

Online Supplementary Reading Materials


1. Project Management Methodologies, https://www.tutorialspoint.com/management_concepts/project_management_methodologies.htm,
April 22, 2020
2. Adaptive Project Framework As A Method Of Non-Traditional Project Management https://newline.tech/blog/adaptive-project-framework-
as-a-method-of-non-traditional-project-management/, April 22, 2020
3. What is agile? What is scrum? https://www.cprime.com/resources/what-is-agile-what-is-scrum/, April 22, 2020
4. Crystal Methods , https://activecollab.com/blog/project-management/crystal-methods, April 22, 2020
5. Dynamic Systems Development Method (DSDM), http://dsdmofagilemethodology.wikidot.com/, April 22, 2020
6. Extreme Programming,
https://www.agilealliance.org/glossary/xp/#q=~(infinite~false~filters~(postType~(~'post~'aa_book~'aa_event_session~'aa_experience_report~'aa
_glossary~'aa_research_paper~'aa_video)~tags~(~'xp))~searchTerm~'~sort~false~sortDirection~'asc~page~1), April 22, 2020
7. Feature Driven Development (FDD), https://www.productplan.com/glossary/feature-driven-development/, April 22, 2020
8. DEFINITION
9. ITIL (Information Technology Infrastructure Library), https://searchdatacenter.techtarget.com/definition/ITIL
10. SDLC JAD Model, https://www.w3schools.in/sdlc-tutorial/jad-model/, April 22, 2020
11. Lean Software Development, https://www.productplan.com/glossary/lean-software-development/, April 22, 2020
12. PRINCE2: The Reigning Project Management Methodology, https://www.wrike.com/blog/project-management-basics-prince2-explained/,
April 22, 2020
13. SDLC - RAD Model, https://www.tutorialspoint.com/sdlc/sdlc_rad_model.htm, April 22, 2020
14. RUP, https://techterms.com/definition/rup, April 22, 2020
15. SDLC - Spiral Model , https://www.tutorialspoint.com/sdlc/sdlc_spiral_model.htm, April 22, 2020
16. SDLC Tutorial, https://www.tutorialspoint.com/sdlc/index.htm, April 22, 2020
17. SDLC - Waterfall Model, https://www.tutorialspoint.com/sdlc/sdlc_waterfall_model.htm, April 22, 2020

You might also like