Samenvatting EXIN Agile scrum
Section 1 Agility Concept
Agile concept: to move quickly and easily, or to think quickly and in an intelligent way.
Agile refers to a group of frameworks for the development and management of initiatives, being
both project and programs.
Main goal is to make the development quicker and smoother and create an output that is more
satisfying for the customer.
Project delivery method and lifecycle
Common development processes: Analyze, design, construct, integrate and test
When the steps are one after another the method is called waterfall, which is a predictive lifecycle
When the steps are done in iterations (sprints) it is called agile, which is an adaptive lifecycle
There are many agile frameworks: scrum, XP, DSDM Atern and Crystal
Agile manifesto: We are uncovering better ways of developing software by doing it and helping
others do it. Through this work we have come to value:
1. Individuals and interactions over processes and tools
2. Working software over comprehensive documentation
3. Customer collaboration over contract negotiation
4. 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 later 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
Agile frameworks are not applicable to every project. E.g. we cannot produce a house iteratively and
we cannot develop it incrementally. But that’s not important as we can specify the requirements
upfront and therefore a predictive lifecycle will be fine for this type of project.
A project is used to create an output and a program to create an outcome, done via multiple projects
A project can be done predictively or adaptively, but a program only adaptively.
1
Section 1 Agility Concept
Agile concept: to move quickly and easily, or to think quickly and in an intelligent way.
Agile refers to a group of frameworks for the development and management of initiatives, being
both project and programs.
Main goal is to make the development quicker and smoother and create an output that is more
satisfying for the customer.
Project delivery method and lifecycle
Common development processes: Analyze, design, construct, integrate and test
When the steps are one after another the method is called waterfall, which is a predictive lifecycle
When the steps are done in iterations (sprints) it is called agile, which is an adaptive lifecycle
There are many agile frameworks: scrum, XP, DSDM Atern and Crystal
Agile manifesto: We are uncovering better ways of developing software by doing it and helping
others do it. Through this work we have come to value:
1. Individuals and interactions over processes and tools
2. Working software over comprehensive documentation
3. Customer collaboration over contract negotiation
4. 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 later 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
Agile frameworks are not applicable to every project. E.g. we cannot produce a house iteratively and
we cannot develop it incrementally. But that’s not important as we can specify the requirements
upfront and therefore a predictive lifecycle will be fine for this type of project.
A project is used to create an output and a program to create an outcome, done via multiple projects
A project can be done predictively or adaptively, but a program only adaptively.
1
