Your SlideShare is downloading. ×
0
 
<ul><li>why is </li></ul>
<ul><li>language </li></ul>
<ul><li>IMPORTANT </li></ul>
<ul><li>to </li></ul><ul><li>information technologists? </li></ul>
<ul><li>back in </li></ul>
 
<ul><li>we understood… </li></ul>
As Management Requested it
As Management Requested it As Specified in  the Project Request
As Management Requested it As Specified in  the Project Request As Designed by  the Senior Analyst
As Management Requested it As Specified in  the Project Request As Designed by  the Senior Analyst As Produced by the Prog...
As Management Requested it As Specified in  the Project Request As Designed by  the Senior Analyst As Produced by the Prog...
As Management Requested it As Specified in  the Project Request As Designed by  the Senior Analyst As Produced by the Prog...
<ul><li>and now </li></ul>
 
and
W W W
W e b 1.0 W e b 2.0 W e b 3.0
<ul><li>Complicate </li></ul><ul><li>things </li></ul>
<ul><li>what’s worse </li></ul>
<ul><li>we didn’t fix </li></ul>
As Management Requested it As Specified in  the Project Request As Designed by  the Senior Analyst As Produced by the Prog...
<ul><li>back in </li></ul>
 
<ul><li>so we need a language </li></ul>
<ul><li>that is </li></ul>
<ul><li>SIMPLE </li></ul>
<ul><li>and focuses on </li></ul>
business
people
and things that happen
<ul><li>Sophisticated </li></ul>but is enough …
<ul><li>to help us discuss </li></ul>
 
W e b 1.0 W e b 2.0 W e b 3.0
and fix
As Management Requested it As Specified in  the Project Request As Designed by  the Senior Analyst As Produced by the Prog...
<ul><li>Introducing… </li></ul>
<ul><li>VPEC-T </li></ul>
<ul><li>VPEC-T </li></ul><ul><li>(vee-peck-tee) </li></ul>
<ul><li>a language </li></ul>
<ul><li>for describing </li></ul>
<ul><li>Information Systems </li></ul>
<ul><li>using only </li></ul><ul><li>FIVE </li></ul><ul><li>words… </li></ul>
<ul><li>VALUES </li></ul>
<ul><li>POLICIES </li></ul>
<ul><li>EVENTS </li></ul>
<ul><li>CONTENT </li></ul>
<ul><li>TRUST </li></ul>
V alues P olicies E vents C ontent T rust
VPEC-T  links business & IT
by focusing on
outcomes and adoption
NOT
technology
NOR
processes & functions
VPEC-T is
a framework
for understanding
what’s wanted
what’s not wanted
what needs to change
and what will be
adopted
So…
VPEC-T  is a common language
<ul><li>that focuses on </li></ul>
business
people
and things that happen
<ul><li>Sophisticated </li></ul>but is enough…
<ul><li>to help us discuss </li></ul>
 
W e b 1.0 W e b 2.0 W e b 3.0
and fix
As Management Requested it As Specified in  the Project Request As Designed by  the Senior Analyst As Produced by the Prog...
which prevents
important
Tensions Issues Ideas Needs Concerns
from being…
lost in translation.
Find out more… www.lithandbook.com  By building a common language, shared understanding of the information system between ...
Upcoming SlideShare
Loading in...5
×

VPEC-T The Movie (Book Trailer)

1,816

Published on

Published in: Technology
1 Comment
12 Likes
Statistics
Notes
  • Nice work Nigel - I decided to write a book trailer in Slideshare, as Youtube is not my way of communicating, and figured someone must have already done this. The first one I found was yours, and I got a double bonus - a great trailer, and and the concept you are communicating is relevant to a project I have underway in Sharepoint - definitely to benefit from VPEC-T.

    Thank-you Nigel.

    ...Geoff
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total Views
1,816
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
91
Comments
1
Likes
12
Embeds 0
No embeds

No notes for slide

Transcript of "VPEC-T The Movie (Book Trailer) "

  1. 2. <ul><li>why is </li></ul>
  2. 3. <ul><li>language </li></ul>
  3. 4. <ul><li>IMPORTANT </li></ul>
  4. 5. <ul><li>to </li></ul><ul><li>information technologists? </li></ul>
  5. 6. <ul><li>back in </li></ul>
  6. 8. <ul><li>we understood… </li></ul>
  7. 9. As Management Requested it
  8. 10. As Management Requested it As Specified in the Project Request
  9. 11. As Management Requested it As Specified in the Project Request As Designed by the Senior Analyst
  10. 12. As Management Requested it As Specified in the Project Request As Designed by the Senior Analyst As Produced by the Programmers
  11. 13. As Management Requested it As Specified in the Project Request As Designed by the Senior Analyst As Produced by the Programmers As Installed
  12. 14. As Management Requested it As Specified in the Project Request As Designed by the Senior Analyst As Produced by the Programmers As Installed What the User Wanted
  13. 15. <ul><li>and now </li></ul>
  14. 17. and
  15. 18. W W W
  16. 19. W e b 1.0 W e b 2.0 W e b 3.0
  17. 20. <ul><li>Complicate </li></ul><ul><li>things </li></ul>
  18. 21. <ul><li>what’s worse </li></ul>
  19. 22. <ul><li>we didn’t fix </li></ul>
  20. 23. As Management Requested it As Specified in the Project Request As Designed by the Senior Analyst As Produced by the Programmers As Installed What the User Wanted
  21. 24. <ul><li>back in </li></ul>
  22. 26. <ul><li>so we need a language </li></ul>
  23. 27. <ul><li>that is </li></ul>
  24. 28. <ul><li>SIMPLE </li></ul>
  25. 29. <ul><li>and focuses on </li></ul>
  26. 30. business
  27. 31. people
  28. 32. and things that happen
  29. 33. <ul><li>Sophisticated </li></ul>but is enough …
  30. 34. <ul><li>to help us discuss </li></ul>
  31. 36. W e b 1.0 W e b 2.0 W e b 3.0
  32. 37. and fix
  33. 38. As Management Requested it As Specified in the Project Request As Designed by the Senior Analyst As Produced by the Programmers As Installed What the User Wanted
  34. 39. <ul><li>Introducing… </li></ul>
  35. 40. <ul><li>VPEC-T </li></ul>
  36. 41. <ul><li>VPEC-T </li></ul><ul><li>(vee-peck-tee) </li></ul>
  37. 42. <ul><li>a language </li></ul>
  38. 43. <ul><li>for describing </li></ul>
  39. 44. <ul><li>Information Systems </li></ul>
  40. 45. <ul><li>using only </li></ul><ul><li>FIVE </li></ul><ul><li>words… </li></ul>
  41. 46. <ul><li>VALUES </li></ul>
  42. 47. <ul><li>POLICIES </li></ul>
  43. 48. <ul><li>EVENTS </li></ul>
  44. 49. <ul><li>CONTENT </li></ul>
  45. 50. <ul><li>TRUST </li></ul>
  46. 51. V alues P olicies E vents C ontent T rust
  47. 52. VPEC-T links business & IT
  48. 53. by focusing on
  49. 54. outcomes and adoption
  50. 55. NOT
  51. 56. technology
  52. 57. NOR
  53. 58. processes & functions
  54. 59. VPEC-T is
  55. 60. a framework
  56. 61. for understanding
  57. 62. what’s wanted
  58. 63. what’s not wanted
  59. 64. what needs to change
  60. 65. and what will be
  61. 66. adopted
  62. 67. So…
  63. 68. VPEC-T is a common language
  64. 69. <ul><li>that focuses on </li></ul>
  65. 70. business
  66. 71. people
  67. 72. and things that happen
  68. 73. <ul><li>Sophisticated </li></ul>but is enough…
  69. 74. <ul><li>to help us discuss </li></ul>
  70. 76. W e b 1.0 W e b 2.0 W e b 3.0
  71. 77. and fix
  72. 78. As Management Requested it As Specified in the Project Request As Designed by the Senior Analyst As Produced by the Programmers As Installed What the User Wanted
  73. 79. which prevents
  74. 80. important
  75. 81. Tensions Issues Ideas Needs Concerns
  76. 82. from being…
  77. 83. lost in translation.
  78. 84. Find out more… www.lithandbook.com By building a common language, shared understanding of the information system between the different stakeholders, the authors argue that many of the frustrations felt around IT can be overcome, to the benefit of the economy and the wider society. IT and Business: Which do you speak? A handbook for Information Systems in the 21st Century
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×