Your SlideShare is downloading. ×
0
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Agile Analysis Liftoff for ABE 2012
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Agile Analysis Liftoff for ABE 2012

617

Published on

A case study from a successful liftoff

A case study from a successful liftoff

Published in: Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
617
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
22
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  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 alarge organisation…
  7. …using Rational Unified Process
  8. Anyone worked with RUP?
  9. RUP defines many roles…
  10. The System Analyst
  11. ? what’s a BA and what’s an SA
  12. Time for a change
  13. The lean programme will result inmore frequent and predictabledelivery of higher quality solutionsthat more closely match the needs ofthe customer.
  14. ? How do analysts fit into the picture
  15. We don’t need system analysts in agile they only translate requirements
  16. “Responsible  for  valida0ng  and  transla0ng  user  requirements  gathered  by  IT  Business  Analysts  into  technical  solu0ons.     SA Job Spec
  17. let’s dissolve the team
  18. your  projects   will  fail   without  us
  19. In strides… César Idrovo
  20. Perhaps chartering can help
  21. Team charter (from III) 1.  Understand your context 2.  Create a vision 3.  Create a mission 4.  Select values and principles
  22. So we met in posh places
  23. We analysed our past
  24. drew spheres of influence
  25. We even played with Lego
  26. We establisheda shared understanding
  27. And finally created…
  28. a single page
  29. Vision statement Project analysis isrecognised as an essentialelement in the delivery ofquality solutions thatmaximise business value.
  30. Mission statement We give and share ourexpertise in analysis toenable rapid, focused andsuccessful realisation ofbusiness value, workingcollaboratively, and alwayslearning as we do this.
  31. Mission statement We look for opportunitiesfor improvement andacquisition of new skills toremain a dynamic andversatile team.
  32. Values and Principles Continuous improvement We take every opportunityto reflect on, learn fromand share in any success orfailure to continuouslyimprove our individual andcollective performance
  33. Values and Principles Relationships We proactively collaboratewith our customers andstakeholders, striving tobuild an open, honest andtrusting relationship
  34. Values and Principles Flexibility We are open and adaptablein our attitude to the roleswe are asked to performand assist our colleagueswhen required
  35. Values and Principles Team Work We value the success of theProject Analysis team andsupport each other
  36. Values and Principles Respect We respect the viewpointsof others and are open-minded to new ideas
  37. Values and Principles Courage We are not afraid ofdifficult challenges
  38. Values and Principles Delivery We focus on deliveringbusiness value quickly
  39. Values and Principles Working Software We value working softwareover comprehensivedocumentation
  40. Values and Principles Documentation We recognise theimportance ofdocumentation that addsvalue
  41. “And  when  a  group  is  small  enough  and  has  a  shared  purpose,  we  may  call  it  a  team.   Management 3.0
  42. to make it a reality with set OBJECTIVES
  43. ?So how did it all work out
  44. Now you can try this too
  45. purpose alignment context
  46. Purpose •  product vision •  project mission •  mission tests
  47. Alignment •  shared values and principles •  core team forming and cohesion •  working agreements
  48. Context •  boundaries •  resources •  prospective analysis
  49. “For  most  efforts,  success  or  failure  is  in  the  cards  from  the  moment  the  team  is  formed  and  the  ini0al  direc0ons  set  out.   Peopleware
  50. 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
  51. So Thank You
  52. Follow-Up •  Catch me, stop me, talk to me •  Contact me on twitter @mfloryan
  53. 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.

×