c2b_default

PMI-ACP

PMI-ACP: My final knowledge lacks

PMI-ACP: My final knowledge lacks

12
0.0 (0)
S. S.
Study
S. S.
This flashcard set delves into the principles and values of agile project management, tailored for university-level students. It covers key concepts like the Agile Manifesto, emphasizing customer collaboration, working software, and responding to change over rigid plans. The set also explores practical aspects such as contract types, budget management, and the importance of feedback and communication. Ideal for aspiring project managers and software developers, this flashcard set provides a comprehensive overview of agile methodologies and their application in real-world scenarios.
Flashcards
12
Students
8
Language
English
Category
Computer Science
Level
University
Created / Updated
10.05.2015 / 18.06.2024
  • 1  / 12

Flashcards

Agile Manifesto Values:

Individuals and interactions over processes and tools

  • Projects are done by people.
  • But: Tools & processes may be helpful, so far they support to people interactions.

Agile Manifesto Values:

Working Software over comprehensive documentation

  • Reason for doing software projects: write valuable software
  • documentation without valuable, high quality software is worthless
  • software without documentation is problematic
  • document the software just in a barely sufficient extent
  • if concurrency occurs between writing software or documentation, work in favor to the software development

Agile Manifesto Values:

Customer Collaboration over contract negotiation

  • Customers also learn just along the project
  • Requirements therefore may change
  • don't get stucked on outdated, but initially specified requirements
  • instead work toward the actual goal
  • work together in a trustful manner
  • change 4 free & money 4 nothing adress this

Agile Manifesto Values:

Responding to change over following a plan

  • Along the project all participants learn more about it
  • Requirements will change
  • Plans are needed any more, but should be regarded as preliminary versions of the final plan, which is gained just at the end, and therefore not available throughout the runtime
  • make short plans for iterations instead of a major plan for the complete project
  • plan roughly for the longer view and add more detail only for the iterations coming up next
  • make decisions in the last responsible moment before they are needed to proceed

Money 4 nothing

Fix price contract, which could be terminated by customer at any time

Customer might have gotten enough value

Seller gets 20% of the left budget without work to compensate the immediately loss of revenue

Change 4 free

  • Fix price contract allows to perform any change of scope
  • New scope substitutes a similar amount of former scope now priorised lower
  • Scope, which doesn't fit into the fixed price, will not delivered (without increased budget)

Guiding Principles:

Prio 1: Satisfy customer through...

  • early delivery
  • continuous delivery
  • VALUABLE software (done done, MMF)

Guiding Principles:
Embrace change

  • welcome changing requirements, even late
  • agile harnesses change -> competitive advantage 4 customer
  • change != derivation of plan -> change 4 free

Guiding Principles:

Feedback

  • continuous integration
  • TDD
  • frequent delivery 2 get feedback from customer
  • demos 2 get feedback from customer

Guiding Principles:

Working together daily

  • Customer & developer work together DAILY
  • face 2 face
  • avoid misunderstandings arise over time
  • demos
  • at least working with customer proxy

Guiding Principles:

Motivated individuals

  • motivated people are more effective than processes
  • 10:1
  • empower team
  • autonomy for day2day decisions
  • no micromanagement

Guiding Principles:

Face 2 face communication

  • face 2 face better than videocall
  • videocall better than videochat
  • videochat better than normal chat
  • normal chat better than email
  • video better than graphics
  • graphics better than written

Study