Agile Principles Flashcards
Scope bloat definition
Development of features not used by users (over perform)
TPM transformation into Agile PM
Modularization of the outcome
- Open to changes and turbulence
- Finance itself with small and frequent deliverables
Hybrid Project Management
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.
Agile Manifesto
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”
Explain “individuals and interactions over processes and tools”
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
Explain “working software over comprehensive documentation”
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
Explain “customer collaboration over contract negotiation”
Collaboration rather than confrontation
-discovery, questioning, learning and adjusting during project
TPM customer involvement: project start, scope change, project end
-risk of adversarial relationship
Explain “respond to change over following a plan”
Systematic inclusion of change inside the methodology
- Changes are predictable and manageable
- Foster flexibility
- New items added are opportunities
Groups of concepts Agile Principles
Customer Satisfaction
Quality
Teamwork
Project Management
Resisting Formality
Visualizing rather than writing
Think and act as a team
Explain Agile Principle Group “Customer Satisfaction”
Include Product Owner
Iterative: short project cycles
Incremental: frequent delivery
-Total value grows incrementally
Explain Agile Principle Group “Quality”
Product demonstration every iteration
Each new feature is validated by PO
Ongoing testing
Continuous integration
Explain Agile Principle Group “Teamwork”
Task force organizational structure
Self-govern team
Constant pace of work
Face to face conversation
Explain Agile Principle Group “Project Management”
Accomplish only what is most important to the client
Avoid overwork at the end of the project
Explain Agile Principle Group “Resisting formalities”
Reduce hierarchy whenever possible
-eliminate titles within the team
Avoid aesthetic investments
-Presentations, minutes
Educate customers and other stakeholders
Explain Agile Principle Group “Visualizing rather than writing”
Use visuals to communicate and report
- easily available visual and drawing tools in the team environment
- charts, graphs, dashboards, prototypes
