Description of Project Methodologies

Running head: DESCRIPTION OF PROJECT METHODOLOGIES
DESCRIPTION OF PROJECT METHODOLOGIES
Name of the Student
Name of the University
Author Note

1
DESCRIPTION OF PROJECT METHODOLOGIES
1. Brief description of Agile
Agile is a modern method for project planning. It divides projects into modules and for
completion of each of the modules, schedule is planned accordingly. The modules in which
project is divided are associated with various aspects of projects and these include project
planning, project design, project execution and project closure. In this methodology, each of
the task defined in the project module is completed in sequence. If a task is not completed in
the sequence, the next activity in the sequence is not initiated and this helps in organizing
project activities efficiently. This helps in ensuring that each activities in the project schedule
is executed with highest quality, which ensues project success. Identification of stakeholder
requirements and allowing stakeholders review to be integrated with project execution is an
important requirement of ensuring that delivery of project is according to stakeholder
requirements and thus ensures project success.
2. Selection of at least three Agile branches
Three agile branches considered in this report are:
 Scrum: It is a project management framework that involves execution of project
activities in iterative way and according to sequence in activity included in the project
planning
 Kanban: It delivers products while emphasis is made on continual delivery and thus
reducing burden on project delivery team
 Lean: It increases efficiency of project process and reduces waste on time and
resources of the project
3. List advantages and disadvantages, and characteristics of each branch

2
DESCRIPTION OF PROJECT METHODOLOGIES
Agile
branch
Advantages Disadvantages Characteristics
Scrum  Appropriate
management of time
and budget of project
 Project is divided into
sprints that are easy to
manage
 Project development
are reviewed along
with sprint review
 Allows to integrate
customer feedback
within project
 Possibility of scope creep due
to too much flexibility in
project schedule
 Requires commitment for
each and every team without
which project is most likely
to be failure
 Not suitable for large team
 Implementing quality is
challenging as it requires
aggressive project testing
 Project schedule
is flexible
 Execute project in
sprints which
divides the entire
project into
smaller project
modules
 Complex to
implement in
project in large
project team
 Quality depends
on aggressive
testing
 Stakeholders are
involved right
from the
beginning of the
project
Kanban  Increases project  if Kanban board is not  visual extensive