This pack goes through a quick refresher of the key values that makes great agile teams. It also goes through some key roles within the team, what x-functional teams are all about and about importance of the overall agile mindset.

1. agilerefresher
R E D F I G D I G I T A L I N N O V A T I O N
W W W . R E D F I G C O N S U L T I N G . C O M . A U

2. what is agile?
write 3 words in the sticky notes that
describe agile to you...

3. we don’t need an
accurate document, we
need a shared
understanding
JEFF PATTON

4. agile team
values
Commit to a common goal
Work together, help each other
Communicate to get clarity
Empower the team
Testing needs to be smart
Done means DONE
Being considerate of each other
Appreciate each other

5. the roles of
agile teams
Product Owner
BA/Designer/UX
Architect
Developer
Tester
Scrum Master
DESIGN VISION REALISE VISION
TOGETHER: Implement, Validate, Release Vision

6. Product Owner
Build and manage the product backlog
Clarify the the goals of the backlog
Give team clear guidance and priorities
Decide when to release the product
They are focused on understanding business
and market requirements, to prioritise the work
to be done by the agile team.

7. BA/Designer/UX
Clarify intent of a Feature, its Business Value
Ensure end user(s) are considered
Ensure there is consistency in design
Work with Architects/Developers to break
down user stories
Ensure Acceptance Criteria is testable
Help Implementers understand intent
They are focused on clarifying requirements, to
design functionality in a considered and
consistent manner. They must educate others.

8. Architect
Clarify intent of a Feature, its Business Value
Ensure big picture of system is considered
Ensure there is consistency in tech design
Work with BA/Devs to break down tech stories
Ensure Tech Stories have clear Exit Criteria
Help Implementers understand technical
design and its intent
They are focused on designing the system from a
technical perspective and to alignment with
global standards, so that it is robust, scalable and
performs well. They must educate team.

9. Developer
Clarify intent of a Feature, its Business Value
Question purpose, intent, usability, tech design
Learn about the big picture of system, input
Implement stories in a consistent tech manner
Work with BA/Architects to break down stories
Gain clarity on Acceptance and Exit Criteria
Gain understanding of overall intent
They are focused on implementing the system by
following tech design, so that stories/features meet
the overall intent and have Business Value.

10. Tester
Clarify intent of a Feature, its Business Value
Question purpose, intent, usability, testability
Learn about the big picture of system, input
Test stories in a consistent, thorough manner
Gain clarity on Acceptance Criteria
Gain understanding of overall intent so that
they can "test outside the square"
They are focused on ensuring that stories/features
meet the acceptance criteria and have achieved
Business Value as intended.

11. Scrum Master
Ensure there is clear estimated backlog stories
for upcoming sprints
Facilitate meetings for sprint/release planning
Resolve any impediments and distractions that
may affect the team
Maintain the sprint's scope airtight once it has
begun, ie no changes to scope during sprint
Champion agile, strive to improve process
They are focused on ensuring the team has all they
need to be able to implement the vision.

12. what does
x-functional
mean anyway?
We do the best what we can with
the people we have
We train the people we have
We are considerate if someone is
doing something new/outside their
comfort zone
We roll up our sleeves and help out
where-ever we can
We don’t sit idle, we look for ways
to achieve the goals team has
committed to
If we don’t understand something
we ask

13. Risks/Impacts
of NOT being
Agile
Changing Priorities - Loss of time
Minimal BA time - Loss of clarity
Unclear A/E Criteria - Loss of time
Stories too large - Expanding Points

14. agile … is an attitude, not a
technique with boundaries. An
attitude has no boundaries, so
we wouldn’t ask ‘can I use agile
here’, but rather ‘how would I
act in the agile way here?’ or
‘how agile can we be, here?’
ALISTAIR COCKBURN

15. in summary
The agile team is fully responsible for
understanding big picture, business intent, inputing into
and cross checking what they work on, validating
estimates commitment of goals and delivery of stories
agile is a mindset
Look around you, this is YOUR team, YOU ARE AGILE
Communication is so important, always ASK WHY,
always offer extra information - NEVER ASSUME!
Planning is paramount and WE CAN ADAPT the plan
IF YOU alert us of ANY changes