WEBVTT

1
00:00:03.672 --> 00:00:08.548
In this video we’ll talk about Adaptive Project Management or Agile.

2
00:00:08.728 --> 00:00:12.050
The origin of adaptive management can be traced back to ideas

3
00:00:12.051 --> 00:00:16.720
of scientific management pioneered by Frederick Taylor in the early 1900s.

4
00:00:17.197 --> 00:00:21.303
Adaptive management is an iterative decision-making process

5
00:00:21.499 --> 00:00:25.316
especially useful in rapidly changing and uncertain conditions.

6
00:00:25.866 --> 00:00:29.528
Adaptive project management uses a feedback process

7
00:00:29.542 --> 00:00:31.625
to reduce uncertainty in the future,

8
00:00:31.811 --> 00:00:37.663
thereby embracing risk and uncertainty as tools to further understand the environment.

9
00:00:37.718 --> 00:00:41.112
Adaptive project management presents a group of product

10
00:00:41.133 --> 00:00:43.612
and service development techniques using

11
00:00:43.600 --> 00:00:48.506
an iterative and incremental approach in which solutions are delivered in stages.

12
00:00:48.807 --> 00:00:52.721
These promote adaptive planning to develop product in iterations,

13
00:00:52.847 --> 00:00:57.131
thereby lending a greater flexibility to change during the development process

14
00:00:57.211 --> 00:00:59.900
while reducing the extent of long-term planning.

15
00:01:00.039 --> 00:01:05.067
This minimizes the risk involved with changes in the long-term vision of a project.

16
00:01:05.500 --> 00:01:09.818
Work is completed in short, iterative time frames by Agile teams. 

17
00:01:10.248 --> 00:01:14.223
Agile emphasizes face-to-face communication among team members

18
00:01:14.272 --> 00:01:16.528
if they are present at the same location.

19
00:01:16.689 --> 00:01:19.300
If teams are geographically distributed,

20
00:01:19.356 --> 00:01:23.056
then Agile recommends daily communication between teams

21
00:01:23.058 --> 00:01:26.073
via videoconferencing and other such technologies.

22
00:01:26.484 --> 00:01:29.783
Now let’s look at some of the popular Agile techniques.

23
00:01:30.234 --> 00:01:34.222
The Crystal family of methodologies focuses on efficiency,

24
00:01:34.382 --> 00:01:37.143
osmotic communication between team members,

25
00:01:37.184 --> 00:01:40.525
and feedback-based learning for future operations.

26
00:01:40.638 --> 00:01:45.177
But the most popularly adopted agile methodology is Scrum.

27
00:01:45.431 --> 00:01:49.746
It focuses on getting work done in time-boxed intervals called Sprints.

28
00:01:50.108 --> 00:01:54.516
Besides the Sprint, Scrum has a series of meetings on regular intervals

29
00:01:54.720 --> 00:01:59.480
(in addition to a daily meeting) to help stakeholders track project progress.

30
00:01:59.522 --> 00:02:03.885
Another technique is Dynamic Systems Development Method.

31
00:02:04.110 --> 00:02:06.304
It is an agile framework that embraces

32
00:02:06.354 --> 00:02:09.172
dynamic customer involvement in project delivery.

33
00:02:09.580 --> 00:02:14.555
DSDM focuses on projects with tight schedules and budgets.

34
00:02:14.871 --> 00:02:18.563
DSDM subscribes to the Atern philosophy

35
00:02:18.589 --> 00:02:23.127
and uses these principles to direct the team in the delivery process.

36
00:02:23.379 --> 00:02:25.608
Then there is Extreme Programming,

37
00:02:25.773 --> 00:02:28.890
a methodology designed to improve software quality

38
00:02:28.896 --> 00:02:32.389
and responsiveness to changing customer requirements. 

39
00:02:32.584 --> 00:02:36.311
Extreme Programming promotes a flat management structure.

40
00:02:36.479 --> 00:02:40.355
It has a few definitive features such as pair programming,

41
00:02:40.644 --> 00:02:44.093
unit testing of all code, and frequent communication

42
00:02:44.096 --> 00:02:46.188
with customers and programmers.

43
00:02:46.404 --> 00:02:48.869
Another popular technique is Kanban.

44
00:02:49.095 --> 00:02:53.998
It emphasizes just-in-time delivery for developing products and processes.

45
00:02:54.175 --> 00:03:00.022
Work is queued according to the desired priority to ensure relevant incremental delivery.

46
00:03:00.454 --> 00:03:03.865
The entire process of work completion is made transparent

47
00:03:03.911 --> 00:03:07.201
to help stakeholders track project progress.

48
00:03:07.596 --> 00:03:10.345
And that brings us to the end of this module.

49
00:03:10.466 --> 00:03:12.466
Thank you for learning with us!