Agile Cheat Sheet
Remember, Agile is not a one-size-fits-all approach, and it's essential to tailor its implementation to your organization's unique needs and
culture. Regularly evaluate and adapt your Agile practices to ensure continuous improvement and value delivery.
Agile Values: Agile Metrics:
▪ Individuals and interactions over processes and tools ▪ Velocity: Average number of story points completed in a sprint. Helps predict the
▪ Working software over comprehensive documentation team's capacity for future sprints.
▪ Customer collaboration over contract negotiation ▪ Lead Time: Time taken for a user story to move from the backlog to a Done state.
▪ Responding to change over following a plan Measures the overall efficiency of the development process.
▪ Cycle Time: Time taken to complete a user story from "In Progress" to "Done."
Agile Principles: Provides insights into how quickly work is progressing within a sprint.
▪ Our highest priority is to satisfy the customer through early and continuous ▪ Burnup Chart: Shows the total work completed (burnup) versus the total work
delivery of valuable software. planned (scope) over time. Helps track progress towards the release goal.
▪ Welcome changing requirements, even late in development. Agile processes ▪ Cumulative Flow Diagram (CFD): Visualizes the flow of work items through different
harness change for the customer’s competitive advantage. stages of the development process. Identifies bottlenecks and helps improve
▪ Deliver working software frequently, from a couple of weeks to a couple of efficiency.
months, with a preference to the shorter timescale. ▪ Defect Density: Number of defects identified per unit of work. Measures the quality
▪ Business people and developers must work together daily throughout the of deliverables.
project. ▪ Customer Satisfaction: Feedback or ratings provided by customers to gauge their
▪ Build projects around motivated individuals. Give them the environment and satisfaction with the delivered product.
support they need, and trust them to get the job done.
▪ The most efficient and effective method of conveying information to and within Agile Scaling Frameworks:
a development team is face-to-face conversation. ▪ SAFe (Scaled Agile Framework): For large enterprises, enables alignment,
▪ Working software is the primary measure of progress. collaboration, and delivery across multiple teams and departments.
▪ Agile processes promote sustainable development. The sponsors, developers, ▪ LeSS (Large-Scale Scrum): Scaling Scrum for multiple teams while maintaining the
and users should be able to maintain a constant pace indefinitely. core principles of simplicity and transparency.
▪ Continuous attention to technical excellence and good design enhances agility. ▪ Nexus: Framework to scale Scrum by defining additional roles, events, and artifacts
▪ Simplicity--the art of maximizing the amount of work not done--is essential. for large product development.
▪ The best architectures, requirements, and designs emerge from self-organizing ▪ Disciplined Agile (DA): A toolkit that provides process guidelines based on Agile and
teams. Lean principles, offering flexibility for various contexts.
▪ At regular intervals, the team reflects on how to become more effective, then
tunes and adjusts its behavior accordingly. Agile Anti-patterns:
▪ Waterfall Agile: Implementing Agile practices rigidly, like a sequential waterfall
Scrum: process, without adaptability.
Roles: Product Owner, Scrum Master, Development Team ▪ Cargo Cult Agile: Adopting Agile practices without understanding the underlying
Artifacts: Product Backlog, Sprint Backlog, Increment principles and values.
Iterative development with fixed-length Sprints (usually 1-4 weeks) ▪ Hero Culture: Relying heavily on a few individuals rather than promoting
collaborative teamwork.
Kanban: ▪ Micromanagement: Undermining team autonomy by excessive control and
Visualize workflow on a Kanban board interference.
Limit work in progress (WIP) to prevent overloading the team ▪ Ignoring Technical Debt: Neglecting to address code quality and design issues,
Continuous delivery with focus on flow efficiency leading to future challenges.
▪ Lack of Product Owner Empowerment: Product Owner lacks the authority to make
decisions, leading to delays and indecision.
User Stories:
A technique to capture user requirements in a concise, understandable format
Structure: "As a [user/role], I want [action] so that [benefit/outcome]." Agile Tools:
INVEST criteria: Independent, Negotiable, Valuable, Estimable, Small, Testable ▪ Project Management Tools: Jira, Trello, Asana, Azure DevOps, VersionOne.
▪ Kanban Boards: Trello, Kanbanize, LeanKit.
▪ Communication & Collaboration Tools: Slack, Microsoft Teams, Zoom, Google
Agile Estimation Techniques: Meet.
Planning Poker: Team members use a deck of cards to estimate effort (Story Points) for
▪ Version Control Systems: Git, Subversion (SVN).
user stories.
▪ Continuous Integration/Continuous Deployment (CI/CD) Tools: Jenkins, GitLab
T-Shirt Sizing: Rough sizing of user stories (e.g., XS, S, M, L, XL).
CI/CD, CircleCI.
Relative Sizing: Compare user stories to determine their relative complexity.
Agile Adoption and Transformation:
Product Backlog Refinement: ▪ Top-Down Support: Successful Agile adoption requires support and involvement
Regular activity to clarify and estimate user stories before they are included in a sprint.
from senior leadership.
Keeps the product backlog up-to-date and ensures the team understands upcoming
▪ Pilot Projects: Start with small pilot projects to test Agile practices and
work.
demonstrate benefits.
▪ Training and Coaching: Provide training and coaching to teams and stakeholders
Sprint Planning: to understand Agile principles and practices.
Establish what to accomplish this sprint and evaluate the bandwidth you have ▪ Culture Change: Foster a culture of collaboration, continuous learning, and
available. openness to change.
▪ Inspect and Adapt: Regularly review and adapt Agile practices based on feedback
Daily Stand-up (Daily Scrum): and experiences.
Daily meeting for the development team to synchronize activities and discuss progress,
blockers, and plans for the day. Agile / SCRUM Roles:
▪ Product Owner: Represents stakeholders, prioritizes the backlog, and ensures
Sprint Review: value delivery.
Meeting at the end of each sprint where the team demonstrates completed work to ▪ Scrum Master: Facilitates the Scrum process and supports the team.
stakeholders and receives feedback. ▪ Development Team: Self-organizing, cross-functional group responsible for
delivering the product.
Sprint Retrospective:
Meeting at the end of each sprint where the team reflects on their processes and Burndown Chart:
identifies improvements for the next sprint. ▪ Visualizes the progress of work in a sprint or project, showing the remaining effort
over time.
Definition of Done (DoD):
A shared understanding of what it means for a user story or increment to be considered Cumulative Flow Diagram (CFD):
complete. ▪ CFD helps to identify bottlenecks and improve efficiency by visualizing work items
in different stages.
gtf.pt
