Professional Documents
Culture Documents
Level 1 - Foundation (Knowledge and Understanding) Level 2 - Advanced Practitioner (Application and
e.g. remember, recognize, choose, find, describe, show, Analysis) e.g. select, identify, organise, use, solve,
list, explain. The candidate can ... analyze, categorize, compare, contrast, subdivide,
L1 0.1 L2 0.1
classify, or outline.
The Agile Manifesto, and underlying Can discuss the meaning of the Agile Manifesto and its
principles Remember and understand the Agile Manifesto and its underlying principles and practices
underlying principles
The terminology and main aspects of the L1 0.2
Know the terminology and, at a high level, the key
L2 0.2 Can speak in the appropriate language for Agile,
most popular Agile methods: Scrum, XP, elements of each of the most popular Agile methods. E.g. demonstrating an understanding of the common
DSDM, Kan Ban, Lean MoSCoW prioritization, the 3 pillars of Scrum, pair philosophy and principles shared by the Agile family of
programming, the Kan Ban / Scrum Board for planning; techniques
the removal of waste from process.
The most popular shared technical L1 0.3 L2 0.3
Be able to state the objectives of: Concurrent Testing,
techniques of these Agile Methods
Continuous Integration, Test Driven Development and the
concepts of "Ready", "Done" and Done-Done" and the
team roles involved with these.
TAILORING L1 Level 1 - Foundation L2 Level 2 - Advanced Practitioner
Competency Competency
number number
Choose an iteration length based on project Can identify the appropriate level of documentation
L1 1 characteristics L2 1 and rigor for different agile projects
Recognize the need to assess and tailor process to Can challenge the process, and innovate to tailor and
L1 2 project characteristics L2 2 improve the process.
Can scale agile methods within and outside the project
L1 3 L2 3
PRIORITISATION, PLANNING AND Level 1 - Foundation (Knowledge and Level 2 - Advanced Practitioner
DELIVERY Understanding: Describe, Explain, List)
Recognize ways to establish clear purpose and scope Can explain the concepts of product architecture and
(that gives the overall picture of the product and the IT technology on a general level
L1 4 business value) L2 4
Understand the need to deliver working product at the Can use modelling to help customer understanding of
L1 5 end of each iteration L2 5 their business processes
Understand the need to deliver using feature-based Can plan using features, not activities
L1 6 rather than task-based approach L2 6
Recognize how to create and maintain release plans and Can explain the prioritisation of features / new ideas /
L1 7 iteration plans L2 7 requirements
Can explain the concept of minimisation of waste
List several agile estimation techniques (user story points,
L1 8 wide band delphi, yesterday's weather, planning poker) L2 8
Can explain the protection of project value by
appropriate controls on quality, change management
L1 9 Understand the purpose of "fix the time, vary the scope" L2 9 and testing
Can explain the concept of timeboxing and a regular
List factors for prioritizing requirements (e.g. business pattern of delivery of business-valued increments
L1 10 value and risk) L2 10
Recognize the need to establish a technical environment Can identify and manage risk related to an agile
that supports iterative and incremental delivery: source approach.
control, infrastructure, automated testing, continuous
L1 11 integration, daily builds. L2 11
Can explain how to estimate in an agile environment
L1 12 L2 12
FEEDBACK AND ADAPTATION Level 1 - Foundation Level 2 - Advanced Practitioner
Is able to facilitate
Understand the elements of basic facilitation skills: how
to run a meeting and how to teach people how to behave
L1 24 in a meeting, decision making, team norms, etc. L2 24
Is able to help individuals via coaching
L1 25 L2 25
Is able to manage people
L1 26 L2 26
Is able to negotiate
L1 27 L2 27
Knows the team development phases: forming, storming, Knows the team development phases: forming,
L1 28 norming, performing L2 28 storming, norming, performing
Can identify team role preferences / types and explain
how to build on team members personal strengths
L1 29 L2 29
Can recognize the Agile differences when dealing with Can handle formal agreements / contracts where
formal agreements / contracts where necessary, as a necessary, as a basis for collaboration
L1 30 basis for collaboration L2 30
Can recognize the use of agile techniques for handling Can explain the use of agile techniques for handling
L1 31 requirements L2 31 requirements
HANDLING TEAM DYNAMICS Level 1 - Foundation Level 2 - Advanced Practitioner
Understand agile ceremonies such as "Celebrate small Can explain the importance of a team vision
L1 32 victories" L2 32
L1 33 Explain the importance of sustainable pace L2 33 Can explain the importance of sustainable pace
Can explain the value of growing a project by starting a
new team by distributing the original team members
L1 34 Recognize the necessary agile team skills L2 34 (DNA)
Can facilitate the team to establish team norms
L1 35 Describe typical team norms / team working agreements L2 35
Describe a collaborative work environment; Explain the Can explain the value of small teams, even on a large
L1 36 typical size and workings of an agile team L2 36 project
Can explain how to motivate a team by involving them
in planning and decision making
L1 37 Describe the team role in planning, estimating. L2 37
Describe the meaning of co-location of team members Can explain how to generate an open environment
L1 38 and recognise the advantages and disadvantages L2 38 where people feel safe to express themselves
Can explain how to establish team relationships based
Understand the concepts of personal responsibility and on mutual respect
L1 39 mutual respect; Understand the need to "Trust the team" L2 39
List and understand the responsibilities of typical project Can explain the importance of project organisation and
roles: Product Owner, Domain Expert, Project Manager, team roles and responsibilities, with both customer and
Scrum Master, Business Analyst, Designer, Developer, development roles
L1 40 Tester, Implementer, Release Manager etc. L2 40
Can explain the importance of appropriate means of
Recognize and explain: Visual Management, positivity
communication
L1 41 indicators, Kan Ban and Scrum boards L2 41
CUSTOMER AND STAKEHOLDER Level 1 - Foundation Level 2 - Advanced Practitioner
INVOLVEMENT