XP Values

Loading...

From the course by University of Minnesota

Agile Software Development

48 оценки

University of Minnesota

Agile Software Development

48 оценки

Course 2 of 4 in the Specialization Software Development Lifecycle

Software industry is going crazy on agile methods. It is rapidly becoming the choice for software development where requirements are unpredictable or is expected to change over time. This course will help you gain knowledge on what is agile? Why agile is better suited for these situations? We will also cover some of the most common agile frameworks like scrum and XP in depth. Prerequisite: You need basic knowledge of software development process and software development methodologies. After completing this course, you will be able to : 1) Demonstrate the ability to participate effectively in agile practices/process for software development. 2) Explain the purpose behind common agile practices. 3) Ability to apply agile principles and values to a given situation. 4) Ability to identify and address most common problems encountered in adopting Agile methods. Project: You will also be given opportunity to apply what you learn in this course. You will be given fictional case studies, where after studying the case study, you will have to exercise some of the practices, techniques, etc that team members of an agile team members are expected to know.

From the lesson

XP and Course Wrap-up

In this module, we will compare Scrum to XP and learn about some of the engineering practices from XP.

XP Overview3:05

XP Practices - Part 15:55

XP Practices - Part 26:30

XP Process Model3:20

Meet the Instructors

Praveen Mittal
Adjunct Professor
College of Science and Engineering

In this lecture, we are going to learn

about five values behind the XP practices and methods.

The values are simplicity,

communication, courage, feedback, and respect.

Let us learn about what each of these means.

Simplicity, the value of simplicity is all about

maximizing value by doing only what is necessary.

So basically, keeping things simple.

So Kent Beck uses the phrase,

"What is the simplest thing that could possibly work?"

Sometimes it results in controversy that everything cannot be solved by simple designs.

While it does not mean that every design has to be very, very simple,

it basically means the simplest design that could possibly work.

So don't try or engineer the solution.

So we can do that by taking smaller steps towards our goal and iterate.

The next value is communication.

The value of communication came from the realization that a lot of

issues could be resolved quickly if teams were effectively communicating.

For example, team member is stuck solving a problem,

and another team member knows the solution.

But since they are not communicating effectively or quickly enough,

issues can take longer to resolve or maybe resolved incorrectly.

So as per the XP value,

everyone is part of the team,

and they communicate face to face daily.

And team works together on everything from requirements to code.

Kent realized that effective communication is important

for creating a sense of team and effective cooperation.

The next value is courage.

The idea is about how team act in face of fear.

Are they honest in their approach and actions?

With that in mind,

here are some examples that will demonstrate this value.

We will tell the truth about the progress, so we won't hide.

We don't document excuses for failure because we plan to succeed.

And we will adapt to changes whenever they happen.

The next value is about feedback.

XP teams accept that they won't get a solution or their process right the first time.

They will need to iterate.

So to iterate and improve,

it is really important to get feedback.

So XP teams tries to generate

as much feedback as a team can handle as quickly as possible.

Now, very important thing to remember here is

that generate only the feedback the team can handle.

If they can't handle that feedback,

it is better to slow down the feedback.

Now feedback can come in many forms.

It could be the code, meaning,

are the test running?

Are they successful?

Is code solving the problem it's supposed to do?

Or it could be the feedback from the customer for the delivered software.

The last one is about respect.

It is the foundation of previous four values discussed.

If members of a team don't care about each other,

then XP won't work.

If team members don't care about the project,

nothing can save the project.

So every person whose life is touched by

software development has equal value as a human being.

No one is intrinsically worth more than anyone else.

For software development to simultaneously improve in humanity and productivity,

the contribution of each person on the team need to be respected.

So in a nutshell,

I'm important and so are you.

Ознакомьтесь с нашим каталогом

Присоединяйтесь бесплатно и получайте персонализированные рекомендации, обновления и предложения.

Coursera делает лучшее в мире образование доступным каждому, предлагая онлайн-курсы от ведущих университетов и организаций.

© Coursera Inc., 2018 Все права защищены.

Загрузить из App Store

Загрузить в Google Play