All You Need To Know To Being and Doing Agile 1728113667
All You Need To Know To Being and Doing Agile 1728113667
BEING Approach
Structure, Roles
AGILE Values and Skills
Before …
DOING
AGILE!
NOVEMBER 2020
Manual
All you need to know to being & doing agile
Together Everyone Achieves More .
We listen, respect , leverage on, adjust
I TEAM MANUAL CONTRIBUTION
flexibly & value each others input . We
Spread it around to shape healthy,
collaborative & winning . . .
THE AGILE APPROACH MANUAL | ALL YOU NEED TO KNOW TO BEING AND DOING AGILE BACK 2 NEXT
1. AGILE KEY CONCEPTS PAGE #
o KEY CONCEPTS AND DEFINITIONS pg. 4 , pg. 5.
E
o TRIBE, SQUAD AND CHAPTER pg. 8
THE AGILE APPROACH MANUAL | ALL YOU NEED TO KNOW TO BEING AND DOING AGILE BACK 3 NEXT
o
I KEY CONCEPTS Being Agile & Doing Agile
Underpinning agile is a set of values
and principles, that require a shift in
“ We cannot solve our problems with
“
the same thinking we used when
we createdthem
What is Agile? the mindset, from delegating to doing,
from arguing to negotiating. Still mindset
Agile is about working incrementally, alone is not enough, practice helps Albert Einstein
in cross-functional teams in order to teams deeply understand agile
recognize & respond to change
effectively (get feedback quickly and
adapt to it), in order to continually meet
the needs of swiftly changing customer The Agile Mindset...
needs. Don't Leave Home Without it! - Michael Sahota
THE AGILE APPROACH MANUAL | ALL YOU NEED TO KNOW TO BEING AND DOING AGILE BACK 4 NEXT
o
I DOING & BEING
p r a c t i c e s m a n i f e s t o
THE AGILE APPROACH MANUAL | ALL YOU NEED TO KNOW TO BEING AND DOING AGILE BACK 5 NEXT
a
o
I KEY CONCEPTS
Traditional Ways of Agile Ways of Development Model
Working: Working:
Focus
Traditional project Agile rejects these
management as an traditional methodologies Management
example (AKA waterfall) is being restrictive, and
a linear approach where unsuitable for the new Customer Involvement
all the phases of a era of speed. Agile
process occur in a project management is Developers
sequence, dependent on iterative and aims at
tools & experience. It constantly incorporating Technology
follows this life cycle: user feedback and
plan, design, build, test, continuous releases with Product Features
production, support every iteration of software
development project. Testing
The entire project is
planned upfront without Every task output is a Documentation
any scope for changing product sold to
requirements, assuming stakeholders. Here, QUALITY ASSURANCE
Workflow
that time and cost are Teams and work PLAN CREATE DEPLOY
RELEASE
DEFINE & DEVELOP
variables and structures are designed CREATE QUALITY ASSURANCE
PLAN
NEXT ITERATION
BRAINSTORM
REVIEW
PLAN
THE AGILE APPROACH MANUAL | ALL YOU NEED TO KNOW TO BEING AND DOING AGILE BACK 6 NEXT
a
o
I IS NOT A METHODOLIGY!
AGILE COULD BE THOUGHT OF AS A
PRACTICING AGILE SCRUM
TREE THAT ENCOMPASSES MANY
Agile is rather a practice that provides A process in agile methodology which is a
combination of the iterative model and METHODS, WHICH HAVE THEIR ROOTS
guidance on how to choose methods and
the incremental model. GROUNDED IN THE LEAN APPROACH
procedures , the most popular amongst
these methods are: Scrum & Kanban -
which are the most popular 2 - watch this video
All these methods focus on lean software
development and help in building better
“incrementing”, builds a bit at a time
software effectively and efficiently.
LEAN
A philosophy that focuses on waste
reduction. “iterating” builds a rough version, validates it, then slowly builds up quality
A leaner process means faster delivery
and less effort wasted in tasks which MVP - MINIMUM VIABLE PRODUCT
don’t help to achieve the team goals. This
a version of a new product which allows a
helps to optimize every step team to collect the maximum amount of
incrementally. validated learning about customers with the
In a nut-shell it aims at rooting out & least effort
eliminating any red-tape, bottle necks,
etc. in any process and/or team(s)
An illustrative video
interaction, communication, ..etc. will be explaining each
Making sense of MVP method & the process
1 2 3 4
as a recap
click here to watch
a
o
I STRUCTURE
The Tribe is …
Usually, 10-12 people
“
o
o The organizational maximum in one squad, all
The squad is the basic grouping of cross- fully dedicated
functional squads, working
delivery unit within a towards a common purpose
SQUAD 1 SQUAD 2 SQUAD 3
o Composition of a squad
tribe, with cross can be changed over time
Tribe lead (primary) and
functional disciplines & o
Tech Lead are considered
to match its evolving mission
functional expertise on it the Tribes leadership levels o When the squad executes
the mission, it may be
The squad as a unit is set disbanded
Scrum & non-scrum
based on specific principles
roles across tribes play “ which make it modular and o Members of a squad work
an integral part to together in one place, and
effective usually the Product Owner
deliver the squad’s & o Autonomy and self- is considered squads
tribe’s overall mission. steering leadership level.
a
o
I SCRUM CORE ROLES There are 3 core roles in scrum: Product Owner, Scrum Master
& together they are called the Scrum / Development Team
© SCRUMstudy.com
Defines product vision & Ensures Scrum theory & practices Deliver the chosen backlog items
communicates what team works on are well understood
Manages & maintains the product Removes impediments if a team Attend the required Scrum meetings
backlog member is blocked
Liaise with & answers questions of Ensures rules of Scrum are not Be part of a self- organization team
the Tech teams broken
Oversees product development, Coaches team members to self- Be transparent & share progress
ensures highest value items are organize
worked on
Works with other Scrum masters Help other team members
Understands & prioritizes needs of all across squads/tribes
stakeholders
The Product Owner optimizes ROI by analyzing product The Scrum Master helps the development team to learn & The Scrum Team creates the commodity that the Product Owner requires
aspects, converting these into a priority-wise list to decide on apply Scrum skills to achieve business value. The Scrum to go ahead. The Team in Scrum is “cross-functional” – so that they can
which should be at the top of the list for the next Sprint, & Master help the Team, Product Owner & the organization contribute accordingly as per the increment which is required to come with
continuously changing the priority based on analysis & with their knowledge, skills & by whatever means to the product. As the team is cross-functional, so they promote multiple
recreating the list. The Product Owner is responsible for profit & become more & more successful. The Scrum Master is not learning. Each person in the team has some specialization & keep on
loss of the product, supposing it is a retail product. In case of an the leader of the Team members, nor are they a project learning other specialties as well as that might be required for the project.
internal operation, the Product Owner is not accountable for manager or team representative. However, the Scrum The Team should be available throughout the project. They shouldn’t split
ROI unlike in the case of commercial product (which generates Master’s job is to serve the Team. They help to remove their time to other projects while handling this project. Their responsibility
revenue); however, they are still accountable for maximizing barriers to project, protect the Team from any outside is to self–organize themselves to achieve each goal & creating the product
ROI. The Product Owner & the customer might be the same conflict, & help the Team to adopt modern development as per each sprint plan. Once the product owner makes a complete list of
person in few cases. practices. things to be done, the development team members foretell how much they
can do in one sprint, & they further decide how they will accomplish it.
THE AGILE APPROACH MANUAL | ALL YOU NEED TO KNOW TO BEING AND DOING AGILE BACK 9 NEXT
a
o
Tribe leads report to Chief Digital Officer, owning the tribe targets cascading it down to POs
I ROLES & DESCRIPTION who report directly to them. Chapter Leads manage and evaluate the squad’s performance
holding relevant squad's performance discussions
Tech lead reports to Chief Technology Officer , where Tech Chapter Leads
manage & evaluate performance of IT & tech within squads
DESCRIPTION ROLE SQUAD 1 SQUAD 2 SQUAD 3
Leads tribe & coordinates between squads & other tribes. Is accountable for tribe’s
TRIBE LEAD
targets
Depends on
Leads all senior IT professionals & tech-related work within the tribe, counsel tribe scope,
lead & POs, oversees tech chapters, shares ownership of targets with tribe lead, TECH LEAD
capacity and
responsible for IT platforms integrity & mid-term evolution WHAT
organization
Responsible for
maturity/need.
Prioritizes backlog of tasks, collects requirements & inputs, estimates impact to
PRODUCT OWNER building the right
maximize value & manages stakeholders thing
Build products independently. They are fluent on both front (FE) and back end
(BE) languages and frameworks but also on servers, network and hosting;
FULL-STACK DEVELOPERS
the full stack of technical knowledge that helps build a website or a product, able
to build the T-shape, and integrate APIs
HOW
Responsible
Creates the visual language & defines the UI design UX DESIGNER for building a
great thing
Provides insights on customer service & business perspective SUBJECT MATTER EXPERT *
Responsible
Coaches squad to scrum & agile practices. Manages workflow & team dynamics.
SCRUM MASTER ** for building
Potential Agile Coach * it right
Supports 3-4 squads facilitating e2e value flow by coaching on agile practices,
roadblocks and gradually increasing team velocity
AGILE COACH *
* Depends on scope of role, and if only needed given capacity & maturity of squads/organization All roles are independent and don’t report to each other, rather circular org structure and not
** Optimizes customer experience based on user testing [CXX Expert, or Scum Master]] triangular, whereas chapter leads manage performance across as mentioned above
*** Coordinates roles to improve interaction between similar chapters within/cross tribe(s)
a
o
Desired
Desired Product Desired Scrum Master Scrum/Development Team
Owner Characteristics Characteristics Characteristics
o Responsibility to make o Servant leadership & o Versatile & willing to work cross-
decisions facilitation ability functionally.
o Availability to work with the o Approach with the pursuit of o Ability to plan a sprint & self-
team to answer questions continuous improvement manage around that plan.
o Knowledge (to answer the o A good relationship with the o Ability to understand the
team’s questions & to team & a certain degree of product requirements &
organize work appropriately) influence provide effort estimates.
THE AGILE APPROACH MANUAL | ALL YOU NEED TO KNOW TO BEING AND DOING AGILE BACK 11 NEXT
a
o
I SERVANT LEADERSHIP ABILITY
Why People Use Scrum? But being a great Scrum Master, one who
truly embodies the principles of servant-
Scrum is an agile way of working that helps leadership and helps move teams to high-
streamline your product development process performance levels possible with Scrum
and harnesses the power of your teams. way of working- this is much harder and
much more elusive.
A Scrum Master plays an integral role to
ensure that agile teams are more responsive,
productive, and collaborative! click on below book for a 3-pager summarizing the
Good to Great Scrum Masters. Listen also to Geoff’s
Geoff Watts - one of the most experienced PUBCAST episode on What Servant Leadership Is
and respected Scrum coaches in the world -
introduces the ‘servant leadership’
principle, demonstrating it in his latest book:
Scrum Mastery: Good to Great Scrum Master
A good Scrum Master, simply facilitates the
Scrum process and removes impediments.
THE
AGILE
PUBCAST
THE AGILE APPROACH MANUAL | ALL YOU NEED TO KNOW TO BEING AND DOING AGILE BACK 12 NEXT
a
o
I SERVANT LEADERSHIP COMPETENCIES
THE AGILE APPROACH MANUAL | ALL YOU NEED TO KNOW TO BEING AND DOING AGILE BACK 13 NEXT
a
o
I SCRUM FRAMEWORK There are 5 ceremonies in the scrum workflow
SM
Scrum Master
Scrum Team
Give open feedback
Improve the workflow and dynamics for next sprint
THE AGILE APPROACH MANUAL | ALL YOU NEED TO KNOW TO BEING AND DOING AGILE BACK 14 NEXT
o
a
&
UX
UX IS PART OF CX
CX
THE AGILE APPROACH MANUAL | ALL YOU NEED TO KNOW TO BEING AND DOING AGILE BACK 15 NEXT
o
a
&
DESIGN THINKING IN I SOURCES:
1..Service Experience Design TtT & CX Certification, Vodafone UK 2018/2019
2..This is Service Design Thinking | Basics – Tools – Cases (7th printing paperback 2017)
This model below the waterfall graph is known as the ‘DOUBLE DIAMOND’
which allows Agile & CX teams to explore what tools are needed to
understand the customers’ needs.
THE DOUBLE DIAMOND USES 2 THINKING METHODOLOGIES DIVERGENT & DESIGN THINKING IN
CONVERGENT THINKING WATERFALL
CONVERGENT THINKING
Think of A FINAL SOLUTION. It reaches a point where
you have FACTS, and its time to FOCUS and CONVERGE
into ONE ANSWER - the SOLUTION SPACE
o
a
&
I 4 VALUES THE 12 PRINCIPLES
Agile is people centric! It is about trusting the team to deliver how they
want to and trying ideas quickly and failing fast
1 2 3 4
Satisfy the Welcome Deliver Work
Customer Change Frequently Together
5 6 7 8
Trust and Face-to-face Working Products Sustainable
Support Conversation Solutions Development
THE AGILE APPROACH MANUAL | ALL YOU NEED TO KNOW TO BEING AND DOING AGILE BACK 17 NEXT
o
a
&
EXPERIENCE
I
THE POWER OF AGILITY THROUGH
SKILLS-SET PROCESSES
PEOPLE
SKILLS CAPABILITY BUILD INTERVENTIONS SKILLS CAPABILITY BUILD INTERVENTIONS
Agile Programming
Agile Lean and Agile Fundamentals [INHOUSE] Coding Design Patterns and Evolutionary Design
THE AGILE APPROACH MANUAL | ALL YOU NEED TO KNOW TO BEING AND DOING AGILE BACK 18 NEXT
o
a
&
EXPERIENCE
Read the Agile Approach Manual Scrum Fundamentals Follow recommended Agile-tube channels & actively
Certification SFC™ use the Agile Coaching App on the job
Watch embedded videos within the manual
Agile Principles Check the Agile Glossary List Engage in discussions with Agile-profiles & groups on
Linkedin
CX Design Thinking Certification [ 2 days] Agile Ways of Working Agile Fundamentals Workshop [inhouse]
Journey Mapping Simulation [1 day] Essentials
Agile Practitioner Self Funded ICAgile Certifications
[light version of the fundamentals - Professional Track
inhouse]
Self Funded Scrum Alliance Certifications
Self Funded ICAgile Certifications Expert Track Tribe Modeling Session Self Funded Scrum Alliance Certified Agile Leadership
Agile Expert CAL - For Leadership Teams
Self Funded Scrum Alliance Certifications
THE AGILE APPROACH MANUAL | ALL YOU NEED TO KNOW TO BEING AND DOING AGILE BACK 19 NEXT
a
&
o
AGILE TERMS IN A GLOSSARY
THE AGILE APPROACH MANUAL | ALL YOU NEED TO KNOW TO BEING AND DOING AGILE BACK 20 NEXT
a
&
o
I GLOSSARY & IMPORTANT TERMS
1 to 4
THE AGILE APPROACH MANUAL | ALL YOU NEED TO KNOW TO BEING AND DOING AGILE BACK 21 NEXT
a
&
o
I MIND-SET IN AN INFOGRAPH
An Agile mindset is the combinations of actions and Agile mind-set adoption of Ahmed Sedky’s
behaviors that result in an agile culture.
Encompasses values, principles, and a disciplined
focused approach to using the agile framework as part
of existing way of working.
It is a shift from linear plan driven ways of working
towards an adaptive, value driven, customer centric
approach.
This mindset is the environment within which agile
teams flourish. It isn’t a prerequisite for an agile
adoption, nor is it required for a functional agile team.
But if this mindset is cultivated and nourished, the & the
organization would experience amazing results – happy
employees delivering great value and making
customers delighted with the results.
THE AGILE APPROACH MANUAL | ALL YOU NEED TO KNOW TO BEING AND DOING AGILE BACK 22 NEXT
a
&
o
I ERGONOMICS IN WORKPLACE
INTERNAL USE ONLY | DEVELOPMENT & CULTURE TRANSFORMATION, PEOPLE TEAM BACK 23 NEXT
I LEARN WITH THE COACH I EDUCATIONAL CHANNELS
THE AGILE APPROACH MANUAL | ALL YOU NEED TO KNOW TO BEING AND DOING AGILE BACK 24 NEXT
a
&
o
I LEARNING CHANNELS I SCRUM MASTER TOOLBOX
© InfoWorld.com
THE AGILE APPROACH MANUAL | ALL YOU NEED TO KNOW TO BEING AND DOING AGILE BACK 25 NEXT
a
&
o
COACHING
I CARDS APP
WHO NEEDS AN
AGILE COACH
WHEN YOU HAVE ONE
RIGHT THERE IN YOUR POCKET!
THE AGILE APPROACH MANUAL | ALL YOU NEED TO KNOW TO BEING AND DOING AGILE BACK 26 NEXT
a
&
o
SCRUM METHODOLOGY IN A PAGE
© SCRUMstudy.com
THE AGILE APPROACH MANUAL | ALL YOU NEED TO KNOW TO BEING AND DOING AGILE BACK 27 NEXT
a
&
o
EXPERIENCE
I
THE POWER OF AGILITY THROUGH
SCRUM TEAM CERTIFICATIONS PROCESSES
PEOPLE
BUSINESS AGILITY LEADERSHIP AGILITY OPERATING WITH AGILITY
AGILE DELIVERY
THE AGILE APPROACH MANUAL | ALL YOU NEED TO KNOW TO BEING AND DOING AGILE BACK 28 NEXT
a
&
o
R E M E M B E R
BEING
AGILE
Before …
DOING
AGILE!
BACK 29
a
&
o