A case study from a successful liftoff

1. Agile Analysis Liftoff
October
2012

2. I’m Marcin Floryan
http://marcin.flor yan.pl

3. You can find me at:
@mfloryan
with Sergei

4. The ABE Conference:
#abe12
This presentation:
#liftoff

5. Acceptance criteria
☐ You learnt about one example of
an agile liftoff
☐ You can identify potential benefits
of chartering
☐ You will consider an opportunity to
apply chartering with your team

6. Once upon a time there was a
large organisation…

7. …using Rational Unified Process

8. Anyone worked with RUP?

9. RUP defines many roles…

11. The System Analyst

12. ?
what’s a BA
and what’s an SA

13. Time for a change

15. The lean programme will result in
more frequent and predictable
delivery of higher quality solutions
that more closely match the needs of
the customer.

16. ?
How do analysts
fit into the picture

17. We don’t need system analysts in agile
they only
translate
requirements

18. “
Responsible
for
valida0ng
and
transla0ng
user
requirements
gathered
by
IT
Business
Analysts
into
technical
solu0ons.
SA Job Spec

19. let’s dissolve
the team

20. your
projects
will
fail
without
us

21. In strides…
César Idrovo

22. Perhaps
chartering can help

23. Team charter (from III)
1. Understand your context
2. Create a vision
3. Create a mission
4. Select values and principles

24. So we met in posh places

25. We analysed our past

26. drew spheres of influence

27. We even played with Lego

29. We established
a shared understanding

31. And finally created…

32. a single page

34. Vision statement
Project analysis is
recognised as an essential
element in the delivery of
quality solutions that
maximise business value.

35. Mission statement
We give and share our
expertise in analysis to
enable rapid, focused and
successful realisation of
business value, working
collaboratively, and always
learning as we do this.

36. Mission statement
We look for opportunities
for improvement and
acquisition of new skills to
remain a dynamic and
versatile team.

37. Values and Principles
Continuous improvement
We take every opportunity
to reflect on, learn from
and share in any success or
failure to continuously
improve our individual and
collective performance

38. Values and Principles
Relationships
We proactively collaborate
with our customers and
stakeholders, striving to
build an open, honest and
trusting relationship

39. Values and Principles
Flexibility
We are open and adaptable
in our attitude to the roles
we are asked to perform
and assist our colleagues
when required

40. Values and Principles
Team Work
We value the success of the
Project Analysis team and
support each other

41. Values and Principles
Respect
We respect the viewpoints
of others and are open-
minded to new ideas

42. Values and Principles
Courage
We are not afraid of
difficult challenges

43. Values and Principles
Delivery
We focus on delivering
business value quickly

44. Values and Principles
Working Software
We value working software
over comprehensive
documentation

45. Values and Principles
Documentation
We recognise the
importance of
documentation that adds
value

46. “
And
when
a
group
is
small
enough
and
has
a
shared
purpose,
we
may
call
it
a
team.
Management 3.0

47. to make it a reality
with set OBJECTIVES

48. ?
So how did it all
work out

50. Now you
can try this too

52. purpose
alignment
context

53. Purpose
• product vision
• project mission
• mission tests

54. Alignment
• shared values and
principles
• core team forming and
cohesion
• working agreements

55. Context
• boundaries
• resources
• prospective analysis

56. “
For
most
efforts,
success
or
failure
is
in
the
cards
from
the
moment
the
team
is
formed
and
the
ini0al
direc0ons
set
out.
Peopleware

57. The Remember Slide
• Chartering can give a team an
identity essential to succeed
• It creates a shared purpose
• It must be owned by the team
• It’s the journey that matters not
just the outcome

58. So Thank You

59. Follow-Up
• Catch me, stop me, talk to me
• Contact me on twitter @mfloryan

60. License
This presentation is provided under the Creative Commons
Attribution - Share Alike 3.0 Unported License
You are free
to Share — to copy, distribute and transmit the work
to Remix — to adapt the work
Under the following conditions
Attribution — You must attribute the work in the manner specified by the author or licensor
(but not in any way that suggests that they endorse you or your use of the work).
Share Alike — If you alter, transform, or build upon this work, you may distribute the
resulting work only under the same or similar license to this one.