Agile  Allows for FLEXIBILITY while working, you engage and collaborate whit your

stakeholders.
Now, we living in a unpredictable World

Agile Practicies
Teams Empowermen
Value- Whith tAutonomy
Stakehoder Risk Continous
Driven
Management Management Improvement Planning
Delivery

THINK AGILE Planing

Fail Fast
Low Learn Quickly
risk If
everithing You must
Focus on Short, Welcome Change fail Learn
Value-Driven delivery
cycles
Empower
customers and
tams to
Learn Continuos maximeze
Through get efficiency and
discovery Feedback Quality
 SCRUM  Empirical process control framework
(they inspect the product and adapt quickly)
Transparency, Inspection, Adaptation
Role in Scrum

helps the team best use Scrum, also

Product
Provides Owner
the vision for the Development
the Team
people who build the Scrum Master
helps in facilitating readiness for the
product product project, and providing support in the
removal of constraints

User Stories To do Doing Done

 Use Pareto to distribute all needing, features that always the customers use

Agile  Focus on MAKE VALUE for our customers, we need to see everything like a chain, we
have inputs like desires, feelings or necessities from our customers.

Release of product features Feedback

Minumum Viable
Valueable that have been developed from your
Product (MVP)
to meet early demand Customers
(Relase is useful Minimum
to customers) Product that can make introduce
Marketable
into the market
feature (MMF)

In Agile. the most priority it is a Customer Values

Agile  We engage and Collaborate whit StakeHolders
1. Identify your Stakeholders (Stakehoders Mapping)
2. Involve in the project, make cocreation springs
Agile  Show the process to can give that service or product to our customers  Road Map
Agile Communications Personal Communications it’s the best tools to can make a better product
or services, you can se the verbal and not verbal language
Charter Burn Charts
Vision Projects Risk
Sprints Quality / defect stats
Release Plan

Important Interaction
 Interaction 0 (before First Spring)
o Identify Resourses
o Establishing a vision
o Tackling early planning

 Interaction H (Before to production)

Risk Identification  Time, resources and another kind a source
LEAN  Way to identify and eliminate a system´s waste without effecting productivity
VSM (Value Stream Mapping)  Drawing the path something takes to get to users and create
value for them.

AGILE MINDSET Building and Learning

Ask tought
Agile questions
Teams Are open to
improvement

Agile Manifesto Better ways of developming

software by doing it and helping others do it.
We have a common Value.
3. Deliver Frequenly Our daily activities, we
change between Working and Multitasking 
Work by Springs, short interactions, focus
on the Project, all the members working in
the project (SCRUM)
Spring: time boxed interaction of work intended
to deliver a shippable portion of a product in a
short period of scale
 Lean Typical
Wastes

Partially Extra Extra features or Task SHORT

Waiting (just TIME FRAMES
Montion Defects
done work Processes gold plating Switching in time)
Agile Teams should be a Cross-
Funtional

As
a [user], I want [some
feature], so that I can
[GET SOME VALUE].
What (Customer
Want)
How (to
delivery)

SCRUM

SCRUM  Task Dashboards, Work

Queues, use to can see that the team
its working for the solutions of the
problems

Customers To Do Doing Done

Stories
Customers need priorate by Tasks to make reality that Taks doing Task Done
important customers insights
Hight
Low
 Adaptable to the Change
In an Agile team we have a small budget of work and delivery frequently  Springs

Agile Short Terms Planning

Spring review: Customer Feedback
Less than two hours

Extreme Programming  Only focus in Software development

User Stories= Short descriptions of the feature of customers.
Continuous integration= Integrated the code
Test-driven development= How work the software before start to work.
Roles on the team
https://www.javiergarzas.com/2014/02/derechos-y-deberes-de-los-miembros-de-un-equipo-scrum-o-agil-en-general-o-
de-cualquier-tipo.html
Face to face Interactions in Agile Teams, always being teaching a leaning
GroupThink  When a group decides to agree whit the opinion of the few expert in the group

Agile Transformations


Start with a Culture Change in your Organization, change of mindset
Planning poker  técnica para calcular una estimación basada en el consenso