- 720p
- 540p
- 360p
- 0.50x
- 0.75x
- 1.00x
- 1.25x
- 1.50x
- 1.75x
- 2.00x
We hope you enjoyed this lesson.
Cool lesson, huh? Share it with your friends
About this lesson
Agile is a set of principles. There are many project management methodologies that are incorporating these principles. Scrum is currently the most popular.
Exercise files
Download this lesson’s related exercise files.
Agile Approaches60.8 KB Agile Approaches - Solution
60.7 KB
Quick reference
Agile Approaches
Agile is a set of principles. There are many project management methodologies that are incorporating these principles. Scrum is currently the most popular.
When to Use Agile Approaches
Different Agile approaches are tailored for different types of projects. Many of the Agile principles are sound business management principles and should always be followed. Others are unique to specific situation.
Instructions
The Agile principles are spelled out in the Agile Manifesto. This document was prepared at a software development conference in 2001. It has been used as an impetus for the development of a number of project management techniques – most of them are focused on software development. The Agile Manifesto states:
“We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
Individuals and interactions … over processes and tools,
Working software … over comprehensive documentation,
Customer collaboration … over contract negotiation,
Responding to change … over following a plan.
That is, while there is value in the items on the right, we value the items on the left more.”
The Agile Manifesto was written in reaction to the frustration that many people had with the prevailing project management methodologies. However, the principles of Agile are not new. They characterize project work prior to the 1900’s. It was done by small groups of people, often with close collaboration with the customers, and high levels of flexibility to find something that worked. However, the advent of scientific management, made popular by Fredrick Taylor, advocated for standard processes and technical expertise.
This reduced uncertainty and improved the overall quality of project results; but it led to bureaucratic processes that are not closely tied to the rapid changing customer requirements of the software industry. By the 1990’s, new project management methodologies were being introduced. The outcome of this effort was the Agile Manifesto.
Since the Manifesto was issued, many Agile methodologies have been developed. Some of these are narrowly focused on software development. Others are applicable more broadly.
- Extreme Programming (XP) is a software development methodology based upon rapid releases.
- Personal Software Process (PSP)/Team Software Process (TSP) is a software development methodology relying heavily on data and personal responsibility.
- Test Driven Development (TDD) is a software development methodology that starts with a test requirements and then writes code to meet that requirement.
- Dynamic System Development Method (DSDM) is a methodology with broad business applicability that is based upon rapid iterations using time and money constraints.
- Kanban is a methodology that has borrowed an inventory management name from Lean manufacturing. It is an approach with broad business applicability and relies on visual control, pull scheduling and capacity planning. It is particularly well suited for upgrade or refurbishment projects.
- Scrum is a methodology with broad business applicability that is based upon rapid iterations and reprioritization of customer needs.
While some of the elements of this course will apply to many of the Agile approaches, this course will specifically focus on Scrum.
Hints and Tips
- When adopting an Agile methodology for projects that are not software development, a little creativity may be required to apply the elements to non-software related tasks and activities.
- 00:04 Hi, this is Ray Sheen.
- 00:05 I'd now like to look closer at the development of Agile Thinking and
- 00:09 some of the Agile approaches.
- 00:12 >> This movement started with the publication of the Agile Manifesto.
- 00:16 The manifesto was created by attendees at a software development conference in 2001.
- 00:21 It states, we are uncovering better ways of developing software by doing it and
- 00:26 helping others do it.
- 00:28 Through this work, we have come to value individuals and interactions over
- 00:32 processes and tools, working software over comprehensive documentation,
- 00:37 customer collaboration over contract negotiation, and
- 00:41 responding to change over following a plan.
- 00:45 That is while there is value to the items on the right,
- 00:48 we value the items on the left more.
- 00:51 You can see that it's essentially saying bureaucratic project management tools
- 00:55 that are heavy on documentation are being rejected in favor of collaboration and
- 01:00 attitude of just do it.
- 01:02 So how did we get into this situation?
- 01:05 Well first, you need to know the project manager wasn't always process tools and
- 01:09 documentation intensive.
- 01:11 Over 100 years ago, projects were often very flexible and
- 01:14 based upon individual initiative and that often lead to a erratic and
- 01:17 unpredictable project performance.
- 01:20 Then along came Fredric Winslow Taylor in Scientific Management.
- 01:24 This led to the incorporation of standard practices and process excellence in
- 01:27 every business management discipline including project management.
- 01:32 This did improve the predictability and the quality of the project results.
- 01:36 By the 1990's software development industry was reacting to the perceived
- 01:40 bureaucracy, and the lack of flexibility in the project management approaches.
- 01:45 Lightweight project management methodologies were being developed
- 01:48 to speed up software development and bring the team closer to the customer.
- 01:52 This led to the Agile Manifesto written in a software development conference in 2001
- 01:56 that was held in Utah in the United States.
- 02:00 While Agile had a start in the software industry, several of the Agile
- 02:04 methodologies are now being applied to projects that are far from software.
- 02:08 Agile thinking is spreading.
- 02:10 So let's look at some of the more prevalent Agile approaches.
- 02:14 Some of the approaches are specifically applied to software projects.
- 02:17 The first one to mention is Extreme Programming.
- 02:20 This approach relies on rapid software iterations and a high level of change.
- 02:25 Next is another software application called personal software process and
- 02:29 has grown into the team software process.
- 02:32 This technique relies heavily on data, data analysis, and
- 02:35 personal responsibility.
- 02:38 And next is test driven development.
- 02:40 This approach is also used in software.
- 02:42 Now, I have heard that some companies are using it with hardware projects, but
- 02:45 I haven't seen any of those yet.
- 02:47 This approach starts with a test requirement,
- 02:50 the software is written to then pass that test.
- 02:53 The most widely used Agile methodology that extends beyond just software
- 02:57 is Scrum.
- 02:59 This is an iterative approach that relies on regular re-prioritization
- 03:02 of the requirements.
- 03:04 Another method that has business-wide applicability,
- 03:07 is the dynamic systems development model.
- 03:09 Another iterative approach, but this one is focused on time and money.
- 03:14 Recently a technique has been growing that is called Kanban.
- 03:17 Now the term Kanban is actually an inventory Management technique within
- 03:21 the lean manufacturing methodology.
- 03:23 Its value is it is a visual scheduling approach that focuses on
- 03:26 optimized resource utilization.
- 03:29 The technique is particularly well suited for upgrade or
- 03:32 refurbishment projects, because it does require that the project activity is being
- 03:36 known when the project starts.
- 03:38 This course will focus on the scrum methodology.
- 03:41 However if you are taking the course to prepare for
- 03:43 the project management institutes, Agile Certified Practitioner Exam,
- 03:47 you need to be aware of the other methods.
- 03:48 The exam will address Agile principles in general not just the Scrum application
- 03:53 of Agile.
- 03:56 >> Agile is the reaction to the rise of overly bureaucratic project management
- 04:00 methodologies.
- 04:02 Agile principles can be applied in many ways and
- 04:05 we will focus on the Scrum approach in this course.
Lesson notes are only available for subscribers.
PMI, PMP, CAPM and PMBOK are registered marks of the Project Management Institute, Inc.