Beruflich Dokumente
Kultur Dokumente
EMEA LATAM
Chapter Format
1. Introduction to Agile
2. Agile implementation
3. Agile framework
4. Requirements
5. Estimating
6. Planning
7. Retrospectives
8. Metrics
9. Scrum
10. Kanban
Hi,
I am Silvia your Agile Coach and will be here to help you
understand concepts and enjoy your journey towards Agile
The checklist and how-to icon presents you with practical instructions or a
stepby-step document which will help you do something. Refer this chapter Checklist to
see how a checklist looks like.
The Tip icon reminds you or points to information that describes a special benefit of
working with Agile or a specific practise.
INTRODUCTION TO AGILE
LEARN THE
KNOW AGILE
BASICS OF AGILE KNOW THE AGILE
WHY FRAMEWORKS
- Organisation
AGILE ECOSYSTEM - Scrum
- People
- Kanban
- Mindset change
- XP
In order to arrive faster to the market, we need to be very exigent in selecting the first minimum
key features of a product and test their usefulness in the market as soon as possible (test &
learn of Minimum Variable Product, continuous beta versions/high frequency versioning, etc.). This
idea also applies for internal product development: we need to be more selective on the
management of the demand to make better use of the company resources, focusing on the
functionalities really used in the company.
This approach is the opposite of creating the full featured product, that would take a lot of time to be
developed without real feedback from clients usage (by the way, people dont want complex products
difficult to understand, and product simplicity is a key factor for productivity).
As we can see from the Standish Group study, focusing in only selecting and developing the
key product features will save time, effort and money (around a 50%).
Agile has then been determined as a way to accelerate product development in AXA Group. We
believe it is a key facilitator for value creation in the coming years in the company areas where it makes
more sense from a business perspective because of Time to Market needs, initially starting in Digital &
MultiAccess.
An Agile transformation is based in experienced coaching more than training, because there
is not only a question of incorporating new practices but to foster a cultural change.
Agile is to be introduced in the parts of the organization where it makes more sense from a
Business perspective (Time to market, quick market feedback to adjust products, etc.), team
by team, in a gradual way.
An appropriate context is needed, but we wont wait to have the perfect context.
Well shape it gradually. The test & learn principle will also be key to succeed in the Agile
adoption. Below you can find the key success factors to take into account in each area to
transform.
The origin of Agile is in the software development industry, where complexity is common
(requirements uncertainty, participation of different people skills, new technologies, etc.). Currently
Agile principles and practices are being adopted in different areas as product
development, complex project management, team growth and environments constituted by
knowledge workers.
You can find the Agile values and principles, the Agile Manifesto, in the following links:
Agile values
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
Agile principles
1. Our highest priority is to satisfy the customer through early and continuous delivery
of valuable software.
2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's
competitive advantage.
3. Deliver working software frequently, from a couple of weeks to a couple of months, with a
preference to the shorter timescale.
4. Business people and developers must work together daily throughout the project.
5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to
get the job done.
6. The most efficient and effective method of conveying information to and within a development team is face-to-
face conversation.
7. Working software is the primary measure of progress.
8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to
maintain a constant pace indefinitely.
9. Continuous attention to technical excellence and good design enhances agility.
10. Simplicity--the art of maximizing the amount of work not done--is essential.
11. The best architectures, requirements, and designs emerge from self-organizing teams.
12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior
accordingly.
I have grouped some of the Agile principles in three areas that I want you to initially think on:
o Agile cross-functional teams include as much as possible of all the value chain
(projects keep self-contained inside a team), and this is why they are constituted by
Business & IT people, so we constantly involve the customer.
One important characteristic of Agile is that recognises that most effective processes cannot be
full up front defined and that there is the need of a continuous improvement process that
never ends. You will see that almost everything focuses on getting always better and better.
In order to keep the risk under control, I always keep an eye on these factors:
Customer priorities are a key a project plan should be based on customer priorities. We
get first a tangible core product half-way and add pieces incrementally to it in order to
complete the whole vision.
Short iterations we always work with short cycles to limit the complexity of the coming
requirements and to get early feedback of customer expectations, on product results and
working processes performance.
Incremental we use incremental iterations to focus on having stable products with excellent
quality.
Create synergies to be more productive we make sure we share, learn and daily
synchronise teams to identify impediments and always reflect on past events
(retrospectives).
You have to consider two main key factors when you want to
start adopting Agile: organisational and people related areas. If
some are not met before the time of Agile implementation, I strongly
believe that you should go ahead anyway and then create the right
conditions. Agile requires the proper context to work but dont wait to
have the perfect environment and all things in place at once but
test & learn what are the more important things to improve at each
moment.
Customer collaboration - clients have to be truly involved in a project in order for things to
work. Customer collaboration is the important factor for successful product development and
getting higher levels of satisfaction. This requires not only having customers available on site
with the product development team, but also highly motivated and active.
Autonomous teams in order to be fast in decision time, teams include as much skills needed
to be as autonomous as possible, thereby allowing them to take their own decisions.
Team co-location it is the preferred option that especially technical members should be
sitting together. When this is not possible we can work with distributed teams, but tools (as
quality videoconfence) should be provided to help the lack of face-to-face communication (read
more on Chapter 13).
Corporate Culture - having the right corporate culture is a must and it is a necessary factor
determining the introduction of agile methodologies. We need of transparency, continuous
improvement and learning culture.
Dynamism and uncertainty - Agile product lifecycle is always ready to respond to changes
over following a strict, fixed plan.
In summary:
Agile is a way to work that has emerged to provide more flexibility to customers and meet their
expectations in less time, with less risk and more creativity. For achieving this, more collaboration is
needed, people enjoying the work they do and quality time for improvement.
Remember that one of the primary objectives is to grow motivated real teams that constantly
look for high performance while keeping a fluent communication between the parts.
So far we have seen that Agile is about values and practices. This is certainly true but this is also
about a number of practises, frameworks, and techniques.
Agile uses techniques that the industry has been learning for years and has helped shaping the
adaptive, iterative and evolutionary development. Scrum and Kanban are usually used with XP
practices and Lean Principles. We can use the diagram below as a reference of this combination
(notice that the diagram circles do not represent containers).
Scrum main advantage is that it offers a group of practises and tools that allow early feedback, flexibility
and time to market while supporting people.
Scrum is based on experience and learning rather than theory. Lets see their basic components:
Product Backlog - List of prioritised requirements that define
a product.
Small cycles with complete functionality - usable product that meets the clients business
goals (working software/product)
Regular team planning and synchronization.
Regular interaction between business & IT.
Quality time for reflection.
There are mandatory meetings such as the Sprint Plan, Daily Scrum, Product Backlog
Refinement, Sprint Review and Sprint Retrospective; most of them are time-boxed (with a fixed
time) and all have a clear objective.
Product Owner
Unique representative of all stakeholders and users.
Facilitates priorities agreement in the Business side based on Biz strategy and
ROI.
Regularly accepts the completed product.
Collaborates with the Development team in requirement analysis and detailing.
Scrum Master
Develops a high performance, motivated and self-organized team, including Bz and
IT, that collaborates and improves continuously.
Process responsible, transmits the Agile values and principles.
Facilitates meetings, makes the team flow and creates synergies.
Removes impediments that the team cannot solve by itself.
Development Team
Cross-functional and self-organized.
Estimates requirements and provides a solution.
Presents the results to the Product Owner.
Project Manager Removes impediments that are out of the Extended Team
scope of the SM (mainly organizational).
Financial, terms and scope control.
Project reporting.
2. Limit WIP
3. Manage Flow
Improve Collaboratively
REMEMBER
Business heavily involved and working with IT
Fast and collaborative short lifecycles and feedback loops are a characteristic.
Business value is the trading currency.
Stable teams are needed.
Agile values and practises are needed in order to implement it.
Agile Manifesto
Agile Alliance
Agile Atlas
Agile methodology
BENEFITS
Business & IT are aligned to achieve a shared goal.
Working software / product is the primary measure of progress and features are created incrementally.
Encourage deep involvement throughout the products development and a very cooperative
collaborative approach.
Change is broadly accepted even in late phases of development.
Small incremental releases make the product visible and help to identify any issues/risks early.