0% found this document useful (0 votes)
16 views16 pages

Agile Cookbook

This CookBook provides an overview of agile methodologies, including principles, roles, tools, and methods such as Scrum and Kanban, aimed at enhancing project management in dynamic business environments. It emphasizes the importance of agility in meeting customer needs and improving team collaboration while offering practical guidance for problem-solving and project execution. The document serves as a resource for individuals within the GCA organization to adopt agile practices effectively.

Uploaded by

Jure Maleš
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
16 views16 pages

Agile Cookbook

This CookBook provides an overview of agile methodologies, including principles, roles, tools, and methods such as Scrum and Kanban, aimed at enhancing project management in dynamic business environments. It emphasizes the importance of agility in meeting customer needs and improving team collaboration while offering practical guidance for problem-solving and project execution. The document serves as a resource for individuals within the GCA organization to adopt agile practices effectively.

Uploaded by

Jure Maleš
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 16

Kickstart for an agile problem solving

This CookBook provides condensed overview of an agile world:


Principles, Comparisons, Methods, Roles, Tools

▪ Vision / Goal
Why CookBook? ▪ Emphasized benefits of Agile

Whom for is the CookBook? ▪ Key users / Problem definition / Activity setup

▪ Approaches (Waterfall, Agile)


What’s in the CookBook? ▪ Decision tree to pick the method
▪ Minimum Viable Agility overview
▪ Classical project management
▪ Agile methods and tools
▪ Scrum
▪ Who is Who in the Scrum Team
▪ Kanban
▪ Hands-on help (different sources)
Why CookBook?

Business dynamics require new ways of work and approach towards every day tasks and lasting projects especially in
digitalizing industries as Telco providers.

As pointed in A1 Group Strategy, the company aims to transform via adopting agile frameworks in order to meet the
increasing demands for value creation, constant improvement of customer satisfaction, up-to-date vendor relations,
modern partnership models etc.

GCA Team Vision Goal


GCA is on the path of this process and needs to make Provide a condensed first 'living' Cook book which
steps forward. extracts main definitions of agile frameworks, tools,
templates and other practical, hands-on-'help' material.
VISION is to enhance the agile mindset in the area by
outlining the benefits as well as the Support adoption of agile via the principle 'No One size fits
necessities to agilize our way of work. all'.
Why CookBook?

Emphasized benefits of Agile

Expectation Work as Transparent


Simplicity Testable
Management a team Effective

All team members are well All stakeholders work as a Agile project management is Agile methodology provides It is ensured that the complete
aware of the expected outcome team and trust in each highly transparent with effective simplicity and moves from solution is easily end-to-end
of the project and expectations other and efficient communication simple to complex solutions testable and it brings value to
can be easily managed' the customer

As the focus on one common As the team meets on a


As all team members are project with defined roles and daily base and in regular As the iterative process is As the solution is tested in
involved in all steps and competencies show everybody´s planning and review strictly organized and regular iterations/sprints
regular updates and reviews contributions meetings (ideally in one continuously progressing
room!)
This is for anybody in GCA who has to organize a project / solve a problem within
Whom for is this CookBook?
the group or with OpCo(s) in a new way

What do we typically expect from “issue solvers”?


What needs to be done along the way?

Problem definition Activity Set-up Activity Execution Activity Handover Solution

▪ Description of the customer and ▪ Agree on the way of ▪ Team management ▪ Identify the best way to implement ▪ Increased
the customer's need working (organization, tools, the solution in the organization customer
meetings, ceremonies,…) ▪ Stakeholder management happiness that
▪ Get management approval for the results in better
▪ Definition of Goals and Non-Goals financial result
▪ Solution development intended
of the activity ▪ Get management approval for A1
▪ Plan and execute handover process
▪ Align with corporate strategy ▪ Secure resources (team, budget,
time)
▪ Explore initial scope and initial
technical strategy ▪ Identify risks

▪ Discuss level of uncertainty ▪ Identify stakeholders


There are many ways and mindsets to solve modern business
What’s in this CookBook?
issues...

Here is an overview (…well – kind of)


Choosing the right approach depends a lot on the nature of the
What’s in this CookBook?
problem or issue

▪ How well-understood and well-


defined are the project’s goals and
requirements

COMPLEX COMPLICATED
Far from Probe Sense
agreement Sense Analyse
Chaos More adaptive approach
Respond Respond

WATERFALL
Emergent Practice Good Practice
Requirements

AGILE
Disorder
CHAOS SIMPLE
Act Sense
▪ How well-understood is Sense Categorise
the technology and
Respond Respond
solution for solving the
Close to Novel Practice BestPractice
problem
agreement

Close to Far from


Certainty
Technology Certainty

More plan-driven approach


What’s in this CookBook? Use this Decision Tree / Checklist to pick a method

Eliminating Which Consideration is most A clearly defined


Waste important for your team? plan

Flexibility

Is your
Is your end product
Pick a focus
goal clear? deadline set
in stone?
Doing more with
Reducing Defects
less Yes No No Yes

Adaptive
SIX Will external
LEAN Project Agile Waterfall
SIGMA events likely Yes
Framework
affect your
timeline?
Find the right Agile Method
Event Chain
No Methodology
Do you want to They’re somewhat Do your
plan and review flexible customers want
project tasks to decide what
You focus
every two get’s done and
your planning
weeks? when?
on:
Yes No Yes, they want to make all Tasks Resources
of the decisions

Kanba Extreme Critical Path Critical Chain


Scrum
n Programming Method Method
No matter which approach you choose, aim for the
What’s in this CookBook?
Minimum Viable Agility (MVA)

Nothing is “given” – question


Customer Centricity
everything everyday
▪ The customer is always right
▪ We work to solve the customer's problem, not ours

Prioritize Backlog together


▪ Helps to make work transparent
Make work and Prioritize Backlog ▪ Helps to focus on the important / urgent things
progress transparent together
Distribute Knowledge
Customer ▪ Willingness to learn and to share knowledge improves the
Centricity performance of cross-functional teams

Short Iterations
▪ Help to adjust quickly and improve learning curve

Communicate a lot Communicate a lot with each other


with each other Distribute Knowledge ▪ Don't just talk – try to say something! Exchange info daily and in
person!

Make work and progress transparent


Short Iterations ▪ Helps to identify bottlenecks and dependencies
▪ Improves common understanding of the tasks

Nothing is “given” – question everything everyday


▪ Question your way of working and the processes to continuously
improve your results
If you know what you have to deliver at what time and with defined
What’s in this CookBook? resources, here is an overview on classical project management.

Standard Process Planning Execution Review

▪ Planning ▪ Agree success criteria and major ▪ Monitor / report progress to ▪ Document project result
▪ Execution constraints with management the Gantt chart
▪ Review
▪ Compare to initial plan
▪ List Task, estimate time and cost of each
▪ Monitor cumulative cost
task
▪ Learn from what went
Focus Dimensions ▪ Manage project team good or bad
▪ Assess dependencies and identify critical
path
▪ Manage Stakeholders
▪ Scope
▪ Cost ▪ Draw Gantt chart for the project (including
Milestones)
▪ Quality
▪ Timing
▪ Calculate resource requirements
▪ Risk
▪ Resources ▪ Assess risks and prepare action plan
Overview on agile methods and tools
What’s in this CookBook? Agile project management is an iterative approach to delivering a project throughout its life
cycle. It concentrates on empowered people and their interactions and early and constant
delivery of value into an enterprise.

AGILE MANIFESTO AGILE PRINCIPLES (EXCERPT)

Agile project management focuses on 1. Put the customer first: Include stakeholders in the planning
delivering maximum value against business process
priorities in the time and budget allowed, 2. Improve constantly: Regular reflections on how to become
especially when the drive to deliver is more effective
greater than the risk. 3. Deliver on a continuous basis: Accommodate to changing
requirem.
4. Work in an inter-disciplinary team (self-organized): Skilled
team with have decision-making power & willingness to take
ownership

AGILE ARTIFACTS AGILE METHODS & TOOLS

▪ Collocation ▪ Scrum: Focus on delivering highest business value in the shortest time
▪ Dedicated teams ▪ Extreme Programming (XP): Improves software quality and responsiveness
▪ Relative estimating ▪ Kanban: Visualizes the workflow
▪ User stories ▪ Feature Driven Development (FDD)
▪ Velocity ▪ Behavior Driven Development (BDD)
▪ Definition of done
Deep Dive - Scrum Methodology
What’s in this CookBook? Scrum is a framework within which people can address complex adaptive problems, while
productively and creatively delivering products of the highest possible value.
.

SCRUM METHODOLOGY & BENEFITS SCRUM VALUES

▪ Transforms complex tasks into manageable user


stories (ideal for difficult projects)
▪ Ensures transparency and collective ownership
by clear demarcation of roles and planned events
▪ Motivates the team as progress can be observed in a
short period of time
Deep Dive - Scrum Team
What’s in this CookBook? Scrum team is a collection of individuals (4-9 members) working together to deliver the required
product increments (follow a common goal, same norms and rules, respect)

STAKEHOLDERS
We are providing regular feedback and support to the Scrum team Inputs from Executives, Stakeholders, Customers
CUSTOMERS

PRODUCT OWNER DEVELOPMENT TEAM

▪ Represent “customer needs” ▪ Our main focus is HOW THINGS ARE DONE

▪ Care about the VALUE ▪ We provide the estimation points (for stories)

▪ Main focus is WHAT is DONE


Value ▪ We commit ourselves to deliver the story

▪ Main artifact is a PRODUCT BACKLOG ▪ We define Sprint Backlog / Definition of Done

(Backlog grooming) Scrum Team


▪ Defines SPRINT GOAL
▪ Accept or reject work items
SCRUM MASTER

▪ I ensure team’s productivity („Burndown chart”)


▪ I am a shield for external interferences
▪ I faciliate the meetings
Deep Dive - KANBAN
What’s in this CookBook? Kanban is a popular framework used to implement agile software development.
Work items are represented visually on a kanban board, allowing team members to see the
state of every piece of work at any time

4 KANBAN CORE PRINCIPLES KANBAN CORE PROPERTIES

1. Start With What You Do Now ▪ Visualize the workflow


2. Agree to Pursue Incremental, Evolutionary Change ▪ Limit WIP
▪ Manage Flow
3. Respect the Current Process, Roles & Responsibilities. ▪ Make Process Policies Explicit
4. Encourage Acts of Leadership at All Levels. ▪ Improve Collaboratively

KANBAN BENEFITS

▪ Team members' ability to focus


▪ Increased efficiency and productivity
▪ Focus on continuous delivery
▪ Flexibility
EXPAND YOUR KNOWLEDGE

#A1LearningTopic Agility 2019 ▪ Agile Coach Development Program via A1 Learning Hub (starting
(mindset, basic understanding, in Nov, nomination already closed)
terminology, can give first orientation
to employees with no knowledge), ▪ OKR Learning Experiencing, OKR Masters Certifications (starting
#A1LearningTopic Agility on ecampus Nov, Dec) (Barbara Schmiedinger from GCA involved)
from 01/2021 (deep dive into agile
roles & responsibilities, agile daily ▪ Agile Toolbox (currently only GER version)
hacks – when to use what)
▪ Agile role descriptions & Minimal Viable Agility

Click on the story to go to external materials


If you want to become more professional
take a look at the learning portfolio
offered by our Group HR.
WHEN AGILE AGILE
SCRUM GUIDE SCRUM VS KANBAN WHEN WATERFALL METHODOLOGIES
Thank you & The CookBook goes on as we
would expand our knowledge and content
within!

You might also like