When is it appropriate to use agile project management apm
Agile Project Management (APM)
hello welcome to the session on agile
project management in continuation with
the previous context let us see the
learning outcome at the end of this
session students will be able to use and
adopt the iterative project management
lifecycle model an iterative PM LC model
consists of a number of process groups
that are repeated sequentially within an
iteration with the feedback loop after
each iteration is completed iterative
approaches are used when you have an
initial version of the solution but it
is known to fall short in terms of the
features and functions the iterative
cycles are designed to select and
integrate the missing pieces of the
solutions or to add the new features
think of the iterative PM LC model as a
variant of production prototyping the
intermediate solutions are production
ready but they might not be released by
the client to the end-user until the
final version is ready the intermediate
versions give the client something to
work with as they attempt to learn and
discover the additional needed features
the client would choose to release a
partial solution to the end-user in an
attempt to get input from them an
iteration consists of a planning
launching monitoring and controlling and
closing process groups closing and
iteration is not the same as the project
the iterative PM LC model requires a
solution that identifies the
requirements at the function level but
might be missing some of the details at
the feature level in other words the
functions are known and will be built
into the solution through a number of
iterations but the details that the
features are
not completely known at the beginning of
the project they treated PM LC model
embraces several types of iterations
iteration can be on requirement
functionality features design
development solutions and other
component of the solution next we will
see when to use the iterative model they
treated PM LC model kicks in when one of
the following occurs most but not all of
the solution is clearly known that is a
few features require a clarification or
not understood to the user and if you
have chosen the incremental PM LC model
but have a strong suspicions that there
will be more than a minimum number of
scope change requests then the last one
is if you have chosen the adoptive p.m.
LC model but are concerned about lack of
client environment so these are the
cases where we used a tray tube model
next we will see the scoping phase of an
8a to model so it takes on a bit more
complexity than the scoping phase of
linear or incremental plc models and it
requires a decisions that are not part
of linear or incremental PMSing models
that is implementation of the
intermediate solutions that is the work
products that can be a problematic and
final solutions that cannot be defined
at the start of the project planning is
done at two levels in an iterative
payment see model the complete plan for
building the known solution the first
iteration in this plan may be of long
duration in order to accommodate
building a production version of the
entire known solution if you feel that
this iteration will be too long then you
might consider using a tool to model the
solution instead the partial plan for
the high priority functions for this
approach you will begin the partial plan
by prioritizing the functions and
features in the
requirements there is a significant
difference between the project team for
traditional project management project
and project team for agile project
management project the table shows the
difference the first is that the size
characteristic where the it could be
very large the traditional project team
could be very large and in other project
management usually it is less than 15
and skin level is in traditional is all
levels and in agile project management
is mostly the skilled people and
location is a co-located or distributed
in traditional projecting in agile
project management it is a co-located
the experience level in traditional
based project team is a junior to senior
but in agile project management is a
skilled and senior people in the
traditional thus it requires a
supervisor to control the team but in
agile project management team
unsupervised monitor and control phase
monitors the phases and close the phases
or iteration and closes the project let
us see the characteristics the solution
is known but not to the expected depth
in simpler applications of iterative PLC
model features may not be clearly
defined and it offer uses iconic or
simulated prototypes to discover the
complete solution in more complex cases
that requires a solution discovery a
modeling approach that could be a quick
and efficient approach now we will see
the strengths the client reviews the
current partial solution for improvement
there is no substitute to experiencing
and using a partial solution for the
client
this continuous review by the client
that tends to keep the solutions aligned
with business needs and it can process
the scope changes between the iteration
although the simple iterative models can
receive and process the scope changes
requests between iterations if you try
to stay in control by presenting the
client with alternatives and ideas at
each iteration the projects are required
to adopt the changing business
conditions next we will see the
weaknesses it requires a more actively
involved client team than the
traditional project management team the
higher the likelihood of change the more
you need active client involvement to
make a good business decision regarding
the change it requires a co-located team
having the co-located team is usually
not possible and this placeis a high
change project at great risk final
solution cannot be defined at the start
of the project the final solution is a
variable the less you know about the
solution at the beginning the more
unexpected it may be at the end you may
have started out thinking you are going
to solve the entire problem but you
ended up solving only a part of it
because the time our budget Nano or
maybe the parts of the problem turn out
to be the intractable and you just have
to live with the best you can do so the
type of iterative PML see models are the
these are the main models prototyping
and rational unified process so we will
discuss in detail about the prototyping
model prototyping model that figure
shows requirements are gathered from the
client prototype is developed and
delivered to the customer after
delivering to the customer a feedback is
taken from the client and plan for the
next prototype is developed once the
iteration is completed deliver the final
solution for the project pause the video
for a while and think about what this
figure represents
yes the answer is three incremental PM
LC model so here the iterations are
incremented as one two million
iterations so answer is incremental PM
LC model now pause the video for while
and think about what this figure
represents yes the answer is iterative
and incremental model iterative and
incremental development is a combination
of both iterative design or iterative
method an incremental build model for
development during software development
more than one iteration of the software
development lifecycle may be in progress
at the same time and this process may be
described as an illusionary process or
incremental build approach these are the
references I refer thank you
