The tools of the

software
development
cycle
SPRINTS

01 DEFINITION
Sprints are time-boxed
development intervals during
which specific tasks must be
completed. They are a
fundamental concept in Agile
methodologies, especially Scrum.

PURPOSE
Focus: Sprints provide a focused period
for the development team to work on
specific tasks or user stories.
Adaptability: Agile teams can adapt their
strategies based on the feedback
received after each sprint.

PURPOSE
Predictability: Sprints create a
predictable rhythm for
development, allowing
stakeholders to anticipate
when certain features will be
developed.

KEY COMPONENTS
Sprint Planning: At the beginning of each sprint, the
team plans the work to be done during the sprint.
Daily Standups: Short daily meetings where team
members discuss their progress, plans, and any
impediments.
Sprint Review: At the end of the sprint, the team
demonstrates what they've built.
Sprint Retrospective: A meeting after the sprint review
where the team discusses what went well and what
could be improved.

Brian Josué Escalante

Martínez
 The tools of the
software
development
cycle
BOARDS

02 DEFINITION
Kanban Boards visualize the
workflow of tasks or user stories,
typically using columns to
represent different stages of
development (e.g., to-do, in
progress, done)..

PURPOSE
Visualization: Boards provide a clear, visual
representation of work items and their
progress.
Limit Work in Progress (WIP): Teams can set
limits on how many tasks can be in a
particular stage simultaneously, preventing
overloading of team members.

PURPOSE
Continuous Flow: Kanban
emphasizes a continuous
flow of work, allowing tasks
to be pulled as capacity
allows.

KEY COMPONENTS
Columns: Represent different stages of
development.
Cards: Each task or user story is
represented by a card that moves across
the columns as work progresses.
WIP Limits: Limits set for each column to
optimize workflow and avoid bottlenecks.

Brian Josué Escalante

Martínez
 The tools of the
software
development
cycle
COHORT ANALYSIS

03 DEFINITION
Cohort Analysis is a
technique used to analyze
the behavior of specific
groups of users (cohorts)
over time.

PURPOSE
User Behavior Understanding: Helps in
understanding how different groups of
users engage with the product over their
lifecycle.
Data-Driven Decisions: Provides data for
making informed decisions about product
features, marketing strategies, and user
experience improvements.

PURPOSE
Retention Analysis: Especially
useful in understanding user
retention patterns.

KEY COMPONENTS
Cohort Definition: Groups users based on
specific criteria like sign-up date, acquisition
channel, or any other relevant characteristic.
Metric Analysis: Tracks specific metrics (e.g.,
retention rate, conversion rate) for each
cohort over time.
Comparative Analysis: Compares the
performance of different cohorts to identify
trends and patterns.

Brian Josué Escalante

Martínez
 The tools of the
software
development
cycle
PAIR PROGRAMMING

04 DEFINITION
Pair Programming is an agile
software development technique
where two programmers work
together at one workstation. One
writes the code (the driver), while
the other reviews each line as it's
written (the observer or navigator).

PURPOSE
Code Quality: Leads to higher code quality
due to real-time code review and discussion.

Knowledge Sharing: Facilitates knowledge

sharing among team members, reducing
knowledge silos.

PURPOSE
Error Reduction: Helps in
catching errors and bugs early,
leading to fewer issues during
testing and deployment.

KEY COMPONENTS
Driver: Actively writes the code.
Observer/Navigator: Reviews the code in
real-time, offering suggestions and
catching errors.
Frequent Switching: Developers switch
roles frequently to maintain focus and
prevent fatigue.

Brian Josué Escalante

Martínez