Agile Principles Flashcards

1
Q

Scope bloat definition

A

Development of features not used by users (over perform)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

TPM transformation into Agile PM

A

Modularization of the outcome

  • Open to changes and turbulence
  • Finance itself with small and frequent deliverables
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Hybrid Project Management

A

Use of some values and principals from Agile adapted to TPM, specially if facing too much uncertainty and turbulence

Even if not an IT project, it can take advantage of agile to become more effective.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Agile Manifesto

A

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Respond to change over following a plan

  • Ask for flexibility
  • “While there is value on the item on the right, we value the left more”
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Explain “individuals and interactions over processes and tools”

A

Allow people to contribute with their unique value

Simple and direct conversations solve many problems in short time
-Indirect conversations cause ambiguity and consumes time (e-mail)

Dealing with robust processes and tools reduces productivity and generates conformity

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Explain “working software over comprehensive documentation”

A

True performance -> done deliverable
-Definition of done: developed, tested, integrated and documented

Documents should be barely sufficient
-only the enough needed to achieve the goal

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Explain “customer collaboration over contract negotiation”

A

Collaboration rather than confrontation
-discovery, questioning, learning and adjusting during project

TPM customer involvement: project start, scope change, project end
-risk of adversarial relationship

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Explain “respond to change over following a plan”

A

Systematic inclusion of change inside the methodology

  • Changes are predictable and manageable
  • Foster flexibility
  • New items added are opportunities
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Groups of concepts Agile Principles

A

Customer Satisfaction

Quality

Teamwork

Project Management

Resisting Formality

Visualizing rather than writing

Think and act as a team

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Explain Agile Principle Group “Customer Satisfaction”

A

Include Product Owner

Iterative: short project cycles

Incremental: frequent delivery
-Total value grows incrementally

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Explain Agile Principle Group “Quality”

A

Product demonstration every iteration

Each new feature is validated by PO

Ongoing testing

Continuous integration

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Explain Agile Principle Group “Teamwork”

A

Task force organizational structure

Self-govern team

Constant pace of work

Face to face conversation

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Explain Agile Principle Group “Project Management”

A

Accomplish only what is most important to the client

Avoid overwork at the end of the project

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Explain Agile Principle Group “Resisting formalities”

A

Reduce hierarchy whenever possible
-eliminate titles within the team

Avoid aesthetic investments
-Presentations, minutes

Educate customers and other stakeholders

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Explain Agile Principle Group “Visualizing rather than writing”

A

Use visuals to communicate and report

  • easily available visual and drawing tools in the team environment
  • charts, graphs, dashboards, prototypes
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Explain Agile Principle Group “Think and act as a team”

A

Team-level only reports and performance

Develop in pairs and switch often

17
Q

What changes of attitude Agile approaches bring?

A

Change in attitude toward

  • Project Management Processes
  • Change
  • Team’s ways of working