Buy Verified TransferWise Accounts From Seosmmearth
The Agile BA
1. Agile with
a small ‘a’
A bit about what we’ve done
and what we’ve learnt as BA’s
in LBG Digital Banking
Steve Thomson
Head of Business Analysis for Digital Banking at LBG
2.
3. Agile; what’s the point?
When is Agile not Agile?
It wouldn’t work here
OK.. What did work?
Q&A
5. Some reasons why projects fail
1. The world outside moving on, which forces a project to be
redefined during its course so it never really ends, but just runs
out of steam
2. The administrative burden imposed on the IT team eats more
resource than technical development work.
3. Business sponsorship and participation start off strong and then
tail off, leaving the IT project drifting;
4. Red herring stakeholders frustrating a project by raising numerous
side issues and minor concerns;
5. Lack of robust business requirements at the outset, leading to
unrealistic IT project budgets and timescales;
1
2
3
4
5
10. 1. Customer satisfaction by rapid delivery of useful software
2. Welcome changing requirements, even late in development
3. Working software is delivered frequently (weeks rather than months)
4. Close, daily cooperation between business people and developers
5. Projects are built around motivated individuals, who should be trusted
6. Face-to-face conversation is the best form of communication (co-location)
7. Working software is the principal measure of progress
8. Sustainable development, able to maintain a constant pace
9. Continuous attention to technical excellence and good design
10. Simplicity—the art of maximizing the amount of work not done—is essential
11. Self-organizing teams
12. Regular adaptation to changing circumstance
The Agile Manifesto is based on 12 principles:
1
2
3
4
5
6
7
8
9
10
11
12