Getting started with Agile

677 views

Published on

This presentation is about Agile Methodologies for delivering software. It explains how they were born, what motivated them, and why they work. We'll also take a look at how Agile can help you deliver a product of extreme complexity, with high quality levels, and with constant innovation by tapping into OutSystems' R&D case-study. Finally, we'll take a look ahead on the software lifecycle, and you'll learn how you can use Agile beyond development

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
677
On SlideShare
0
From Embeds
0
Number of Embeds
15
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Balancing Agility and Discipline: A Guide for the Perplexed\n
  • Balancing Agility and Discipline: A Guide for the Perplexed\n
  • Balancing Agility and Discipline: A Guide for the Perplexed\n
  • Balancing Agility and Discipline: A Guide for the Perplexed\n
  • Balancing Agility and Discipline: A Guide for the Perplexed\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Vision: A general idea for the app (as opposed to a rigid set of requirements)\nProduct Backlog: A list of requirements, sorted by priority\nIteration Backlog: The top most item of the backlog, that fits in an iteration\nIteration: Were dev magic occurs. Typically lasts 2 weeks.\nCustomer participation is paramount!\nPSP: Potentially shippable product\nBack to product backlog, that can change, with the participation of the customer.\n
  • Vision: A general idea for the app (as opposed to a rigid set of requirements)\nProduct Backlog: A list of requirements, sorted by priority\nIteration Backlog: The top most item of the backlog, that fits in an iteration\nIteration: Were dev magic occurs. Typically lasts 2 weeks.\nCustomer participation is paramount!\nPSP: Potentially shippable product\nBack to product backlog, that can change, with the participation of the customer.\n
  • Vision: A general idea for the app (as opposed to a rigid set of requirements)\nProduct Backlog: A list of requirements, sorted by priority\nIteration Backlog: The top most item of the backlog, that fits in an iteration\nIteration: Were dev magic occurs. Typically lasts 2 weeks.\nCustomer participation is paramount!\nPSP: Potentially shippable product\nBack to product backlog, that can change, with the participation of the customer.\n
  • Vision: A general idea for the app (as opposed to a rigid set of requirements)\nProduct Backlog: A list of requirements, sorted by priority\nIteration Backlog: The top most item of the backlog, that fits in an iteration\nIteration: Were dev magic occurs. Typically lasts 2 weeks.\nCustomer participation is paramount!\nPSP: Potentially shippable product\nBack to product backlog, that can change, with the participation of the customer.\n
  • Vision: A general idea for the app (as opposed to a rigid set of requirements)\nProduct Backlog: A list of requirements, sorted by priority\nIteration Backlog: The top most item of the backlog, that fits in an iteration\nIteration: Were dev magic occurs. Typically lasts 2 weeks.\nCustomer participation is paramount!\nPSP: Potentially shippable product\nBack to product backlog, that can change, with the participation of the customer.\n
  • Vision: A general idea for the app (as opposed to a rigid set of requirements)\nProduct Backlog: A list of requirements, sorted by priority\nIteration Backlog: The top most item of the backlog, that fits in an iteration\nIteration: Were dev magic occurs. Typically lasts 2 weeks.\nCustomer participation is paramount!\nPSP: Potentially shippable product\nBack to product backlog, that can change, with the participation of the customer.\n
  • Vision: A general idea for the app (as opposed to a rigid set of requirements)\nProduct Backlog: A list of requirements, sorted by priority\nIteration Backlog: The top most item of the backlog, that fits in an iteration\nIteration: Were dev magic occurs. Typically lasts 2 weeks.\nCustomer participation is paramount!\nPSP: Potentially shippable product\nBack to product backlog, that can change, with the participation of the customer.\n
  • Vision: A general idea for the app (as opposed to a rigid set of requirements)\nProduct Backlog: A list of requirements, sorted by priority\nIteration Backlog: The top most item of the backlog, that fits in an iteration\nIteration: Were dev magic occurs. Typically lasts 2 weeks.\nCustomer participation is paramount!\nPSP: Potentially shippable product\nBack to product backlog, that can change, with the participation of the customer.\n
  • Vision: A general idea for the app (as opposed to a rigid set of requirements)\nProduct Backlog: A list of requirements, sorted by priority\nIteration Backlog: The top most item of the backlog, that fits in an iteration\nIteration: Were dev magic occurs. Typically lasts 2 weeks.\nCustomer participation is paramount!\nPSP: Potentially shippable product\nBack to product backlog, that can change, with the participation of the customer.\n
  • Vision: A general idea for the app (as opposed to a rigid set of requirements)\nProduct Backlog: A list of requirements, sorted by priority\nIteration Backlog: The top most item of the backlog, that fits in an iteration\nIteration: Were dev magic occurs. Typically lasts 2 weeks.\nCustomer participation is paramount!\nPSP: Potentially shippable product\nBack to product backlog, that can change, with the participation of the customer.\n
  • Vision: A general idea for the app (as opposed to a rigid set of requirements)\nProduct Backlog: A list of requirements, sorted by priority\nIteration Backlog: The top most item of the backlog, that fits in an iteration\nIteration: Were dev magic occurs. Typically lasts 2 weeks.\nCustomer participation is paramount!\nPSP: Potentially shippable product\nBack to product backlog, that can change, with the participation of the customer.\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Things that can impact the speed:\n- Team\n- Type of project (UI, code only, ...)\n\n
  • Things that can impact the speed:\n- Team\n- Type of project (UI, code only, ...)\n\n
  • Things that can impact the speed:\n- Team\n- Type of project (UI, code only, ...)\n\n
  • Things that can impact the speed:\n- Team\n- Type of project (UI, code only, ...)\n\n
  • Things that can impact the speed:\n- Team\n- Type of project (UI, code only, ...)\n\n
  • Things that can impact the speed:\n- Team\n- Type of project (UI, code only, ...)\n\n
  • Things that can impact the speed:\n- Team\n- Type of project (UI, code only, ...)\n\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • - 60/60 rule\n- Book is from 2002. This is bigger with Agile.\n- There are some challenges here: Getting things into production; Getting user feedback; Technical debt; Upgrading processes\n- But let’s focus on bug fixing\n
  • - 60/60 rule\n- Book is from 2002. This is bigger with Agile.\n- There are some challenges here: Getting things into production; Getting user feedback; Technical debt; Upgrading processes\n- But let’s focus on bug fixing\n
  • - 60/60 rule\n- Book is from 2002. This is bigger with Agile.\n- There are some challenges here: Getting things into production; Getting user feedback; Technical debt; Upgrading processes\n- But let’s focus on bug fixing\n
  • - 60/60 rule\n- Book is from 2002. This is bigger with Agile.\n- There are some challenges here: Getting things into production; Getting user feedback; Technical debt; Upgrading processes\n- But let’s focus on bug fixing\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • - Team must be able to change its processes\n- Team must be eager do deliver value\n- Team must have a frequent and honest communication with customer\n- Collaboration within and beyond the team. Meetings != Collaboration\n- Never give up on quality\n- Small steps to everything\n- Automate the repetitive, error-prone time consuming tasks\n
  • - Team must be able to change its processes\n- Team must be eager do deliver value\n- Team must have a frequent and honest communication with customer\n- Collaboration within and beyond the team. Meetings != Collaboration\n- Never give up on quality\n- Small steps to everything\n- Automate the repetitive, error-prone time consuming tasks\n
  • - Team must be able to change its processes\n- Team must be eager do deliver value\n- Team must have a frequent and honest communication with customer\n- Collaboration within and beyond the team. Meetings != Collaboration\n- Never give up on quality\n- Small steps to everything\n- Automate the repetitive, error-prone time consuming tasks\n
  • - Team must be able to change its processes\n- Team must be eager do deliver value\n- Team must have a frequent and honest communication with customer\n- Collaboration within and beyond the team. Meetings != Collaboration\n- Never give up on quality\n- Small steps to everything\n- Automate the repetitive, error-prone time consuming tasks\n
  • - Team must be able to change its processes\n- Team must be eager do deliver value\n- Team must have a frequent and honest communication with customer\n- Collaboration within and beyond the team. Meetings != Collaboration\n- Never give up on quality\n- Small steps to everything\n- Automate the repetitive, error-prone time consuming tasks\n
  • - Team must be able to change its processes\n- Team must be eager do deliver value\n- Team must have a frequent and honest communication with customer\n- Collaboration within and beyond the team. Meetings != Collaboration\n- Never give up on quality\n- Small steps to everything\n- Automate the repetitive, error-prone time consuming tasks\n
  • - Team must be able to change its processes\n- Team must be eager do deliver value\n- Team must have a frequent and honest communication with customer\n- Collaboration within and beyond the team. Meetings != Collaboration\n- Never give up on quality\n- Small steps to everything\n- Automate the repetitive, error-prone time consuming tasks\n
  • - Much of it depends on you!\n- On your commitment\n- On your efforts to learn more\n- On your pledge to improve the quality of your work\n- On your courage\n- Agile only works with great teams. Great teams only work with great people. That means you!\n
  • \n
  • Getting started with Agile

    1. 1. Getting started with Agile
    2. 2. Waterfall
    3. 3. The idea
    4. 4. The ideaDesign
    5. 5. The ideaDesign Implementation
    6. 6. The ideaDesign Implementation Testing
    7. 7. The ideaDesign Implementation Testing
    8. 8. The idea Design Implementation TestingIdea
    9. 9. The idea Design Implementation TestingIdea Result
    10. 10. Release
    11. 11. ReleaseAx
    12. 12. ReleaseA Bx x
    13. 13. ReleaseA Bx x
    14. 14. ReleaseA Bx x B’ x
    15. 15. ReleaseA Bx x B’ x C x
    16. 16. ReleaseA Bx x B’ x What the business wants now! C x
    17. 17. The result? Succeeded Failed ChallengedFrom CHAOS Report 2009
    18. 18. The result? 32% Succeeded Failed ChallengedFrom CHAOS Report 2009
    19. 19. The result? 32% 20% Succeeded Failed ChallengedFrom CHAOS Report 2009
    20. 20. The result? 32% 49% 20% Succeeded Failed ChallengedFrom CHAOS Report 2009
    21. 21. This does not work!
    22. 22. Manifesto for Agile Software Development
    23. 23. Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
    24. 24. Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:Individuals and interactions over processes and tools
    25. 25. Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:Individuals and interactions over processes and tools Working software over comprehensive documentation
    26. 26. Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation
    27. 27. Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan
    28. 28. Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.
    29. 29. Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more. Kent Beck James Grenning Robert C. Martin Mike Beedle Jim Highsmith Steve Mellor Arie van Bennekum Andrew Hunt Ken Schwaber Alistair Cockburn Ron Jeffries Jeff Sutherland Ward Cunningham Jon Kern Dave Thomas Martin Fowler Brian Marick
    30. 30. Agile
    31. 31. AgileFeature 1
    32. 32. AgileFeature 1 Feature 2
    33. 33. AgileFeature 1 Feature 2 Feature 3
    34. 34. AgileFeature 1 Feature 2 Feature 3 Feature 4
    35. 35. AgileFeature 1 Feature 2• Design Feature 3• Implement• Test Feature 4
    36. 36. AgileFeature 1 Feature 2• Design Feature 3• Implement• Test • Design Feature 4 • Implement • Test • Design • Implement • Test • Design • Implement • Test
    37. 37. What’s the point? Design Implementation TestingFeature 1 Feature 2 Feature 3 Feature 4
    38. 38. What’s the point? Design Implementation Testing Ready to shipFeature 1 Feature 2 Feature 3 Feature 4
    39. 39. What’s the point? Design Implementation Testing Ready to shipFeature 1 Feature 2 Feature 3 Feature 4
    40. 40. What’s the point? Design Implementation Testing Ready to shipFeature 1 Feature 2 Feature 3 Feature 4
    41. 41. What’s the point? Design Implementation Testing Ready to shipFeature 1 Feature 2 Feature 3 Feature 4
    42. 42. What’s the point? Design Implementation TestingFeature 1 Feature 2 Feature 3 Feature 4
    43. 43. What’s the point? Design Implementation TestingFeature 1 Feature 2 Feature 3 Feature 4
    44. 44. What’s the point? Design Implementation Testing Feature 5Feature 1 Feature 2 Feature 3 Feature 4
    45. 45. What’s the point? Design Implementation Testing Feature 5Feature 1 Feature 2 Feature 3 Feature 4
    46. 46. What’s the point? Design Implementation TestingFeature 1 Feature 4 Feature 5 Feature 2
    47. 47. ReleaseA Bx x B’ x C x
    48. 48. ReleaseA Bx x B’ x C x
    49. 49. ReleaseA Bx x B’ x Demo! C x
    50. 50. ReleaseA Bx x B’ x Demo! C x
    51. 51. ReleaseA Bx x B’ x Demo! C x
    52. 52. Easy, isn’t it?
    53. 53. DependenciesFeature 1 Feature 4 Feature 5 Feature 2
    54. 54. DependenciesFeature 1 Feature 4 Feature 5 Feature 2
    55. 55. DependenciesFeature 1 Feature 4 Feature 5 Feature 2
    56. 56. DependenciesFeature 1 Feature 4 Feature 5 Feature 2
    57. 57. DependenciesFeature 1 Feature 4 Feature 5 Feature 2
    58. 58. Customer Feedback
    59. 59. Customer Feedback
    60. 60. Customer Feedback Just one more thing...
    61. 61. Customer Feedback Just one more thing... This is wrong!
    62. 62. Customer Feedback Just one more thing... This is wrong! Cool Stuff!
    63. 63. Customer Feedback Just one more thing... This is wrong! Cool Stuff! Found a bug!
    64. 64. Customer Feedback Just one more thing... This is wrong! Cool Stuff! Found a bug! While you’re at it...
    65. 65. Customer Feedback Just one Is it more important than more thing... the next feature? This is wrong! Cool Stuff! Found a bug! While you’re at it...
    66. 66. Customer Feedback Just one Is it more important than more thing... the next feature? This is wrong! Cool Stuff! Oops... we’ll fix it! Found a bug! While you’re at it...
    67. 67. Customer Feedback Just one Is it more important than more thing... the next feature? This is wrong! Cool Stuff! Oops... we’ll fix it! Found a bug! While you’re at it... Next version...
    68. 68. Customer Feedback Feature 2
    69. 69. Customer Feedback Feature 2 Feature 2
    70. 70. Project Delay? Design Implementation TestingFeature 1 Feature 4 Feature 5 Feature 2
    71. 71. Project Delay? Design Implementation TestingFeature 1 Feature 4 Feature 5 Feature 2
    72. 72. What gives?
    73. 73. What gives? Features WaterfallCost Schedule
    74. 74. What gives?Fixed Features Waterfall Cost Schedule
    75. 75. What gives?Fixed Features Waterfall Cost Schedule Variable
    76. 76. What gives?Fixed Features Cost Schedule Agile Waterfall Cost Schedule Features Variable
    77. 77. What gives?Fixed Fixed Features Cost Schedule Agile Waterfall Cost Schedule Features Variable
    78. 78. What gives?Fixed Fixed Features Cost Schedule Agile Waterfall Cost Schedule Features Variable Variable
    79. 79. Courage! From Agile in a Flash
    80. 80. Courage! • Quality work From Agile in a Flash
    81. 81. Courage! • Quality work • Make things simple From Agile in a Flash
    82. 82. Courage! • Quality work • Make things simple • Go for the hard problem From Agile in a Flash
    83. 83. Courage! • Quality work • Make things simple • Go for the hard problem • Architectural corrections From Agile in a Flash
    84. 84. Courage! • Quality work • Make things simple • Go for the hard problem • Architectural corrections • Throw away From Agile in a Flash
    85. 85. Courage! • Quality work • Make things simple • Go for the hard problem • Architectural corrections • Throw away • Only complete work From Agile in a Flash
    86. 86. Courage! • Quality work • Make things simple • Go for the hard problem • Architectural corrections • Throw away • Only complete work • Be transparent From Agile in a Flash
    87. 87. Not a silver bullet
    88. 88. Not a silver bullet Personnel
    89. 89. Not a silver bullet Personnel Team Size
    90. 90. Not a silver bullet Personnel Team Size Criticality
    91. 91. Not a silver bullet Personnel Team Size Criticality Dynamism
    92. 92. Not a silver bullet Personnel Team Size Criticality Dynamism Culture
    93. 93. About outsystems
    94. 94. About outsystems Since 2001
    95. 95. About outsystems Since 2001 199 Customers
    96. 96. About outsystems Since 2001 199 Customers 22 Industries
    97. 97. About outsystems Since 2001 199 Customers 22 Industries 59 Partners
    98. 98. About outsystems Since 2001 199 Customers 22 Industries 59 Partners 600+ Agile Projects
    99. 99. About outsystems Since 2001 199 Customers 22 Industries 59 Partners 600+ Agile Projects agileplatform™
    100. 100. agileplatform™ overview
    101. 101. agileplatform™ overview
    102. 102. agileplatform™ overview
    103. 103. agileplatform™ overview
    104. 104. agileplatform™ overview
    105. 105. agileplatform™ overview
    106. 106. agileplatform™ overview
    107. 107. agileplatform™ overview
    108. 108. Service Studio
    109. 109. Service Studio
    110. 110. Service Studio
    111. 111. Service Studio
    112. 112. Service Studio
    113. 113. Service Studio
    114. 114. The Application
    115. 115. 5 founders2 developers
    116. 116. BUFD
    117. 117. What was there?
    118. 118. What was there?• Visual Language
    119. 119. What was there?• Visual Language• Meta-model structure
    120. 120. What was there?• Visual Language• Meta-model structure• Platform Architecture
    121. 121. What was there?• Visual Language• Meta-model structure• Platform Architecture• Application Architecture
    122. 122. What was there?• Visual Language• Meta-model structure• Platform Architecture• Application Architecture• Security Model
    123. 123. What was NOT there?
    124. 124. What was NOT there?• Tools
    125. 125. What was NOT there?• Tools• Low Level Algorithms
    126. 126. What was NOT there?• Tools• Low Level Algorithms• Application Details
    127. 127. What was NOT there?• Tools• Low Level Algorithms• Application Details• User Interface
    128. 128. What was NOT there?• Tools• Low Level Algorithms• Application Details• User Interface• User Experience
    129. 129. What was NOT there?• Tools• Low Level Algorithms• Application Details ! ile• User Interface Ag st• User Experience lm o A
    130. 130. SCRUM
    131. 131. SCRUMVision
    132. 132. SCRUM ProductVision Backlog
    133. 133. SCRUM Product IterationVision Backlog Backlog
    134. 134. SCRUM Iteration Product IterationVision Backlog Backlog
    135. 135. SCRUM P.S.P. Iteration Product IterationVision Backlog Backlog
    136. 136. SCRUM P.S.P. Iteration Product IterationVision Backlog Backlog
    137. 137. SCRUM P.S.P. Iteration Product IterationVision Backlog Backlog
    138. 138. SCRUM P.S.P. Iteration Product IterationVision Backlog Backlog
    139. 139. Functional Teams
    140. 140. Functional Teams Server Team
    141. 141. Functional Teams Server Service Studio Team Team
    142. 142. Functional Teams Server Service Studio Team Team QA Team
    143. 143. Functional Teams Server Service Studio Team Team c t QA Team o je P r 1
    144. 144. Cross-functional Teams
    145. 145. Cross-functional TeamsProject A
    146. 146. Cross-functional TeamsProject A Project B
    147. 147. Cross-functional TeamsProject A Project BProject C
    148. 148. Cross-functional Teams DevProject A Project BProject C
    149. 149. Cross-functional Teams DevProject A Project B QAProject C
    150. 150. Cross-functional Teams Doc DevProject A Project B QAProject C
    151. 151. Cross-functional Teams Doc DevProject A Project B QAProject C Source Control
    152. 152. Cross-functional Teams Doc DevProject A Project B QAProject C Build & Test Source Control Automation
    153. 153. Burndown Charts
    154. 154. Missing Effort Burndown Charts
    155. 155. Missing Effort Burndown Charts Week
    156. 156. Missing Effort Burndown Charts Week
    157. 157. Missing Effort Burndown Charts Week
    158. 158. Burndown Charts Late!Missing Effort Week
    159. 159. Burndown Charts Late!Missing Effort Early Week
    160. 160. Missing Effort Burndown Charts Week
    161. 161. Burndown Charts TodayMissing Effort Week
    162. 162. Burndown Charts TodayMissing Effort Week
    163. 163. Burndown Charts TodayMissing Effort Week
    164. 164. Burndown Charts TodayMissing Effort Week
    165. 165. Burndown Charts TodayMissing Effort Week
    166. 166. Success
    167. 167. Success~30 people in R&D
    168. 168. Success~30 people in R&D16 major versions
    169. 169. Success~30 people in R&D16 major versions 543 updates
    170. 170. Success~30 people in R&D16 major versions 543 updates1.4M lines of code
    171. 171. Success ~30 people in R&D 16 major versions 543 updates 1.4M lines of code76,000+ tests running daily
    172. 172. Success ~30 people in R&D 16 major versions 543 updates 1.4M lines of code76,000+ tests running daily 20,295 installations
    173. 173. Beyond Development
    174. 174. The big effort... 40% 60% From Facts and Fallacies of Software Engineering
    175. 175. The big effort... Development 40% 60% From Facts and Fallacies of Software Engineering
    176. 176. The big effort... Development 40% 60%Maintenance From Facts and Fallacies of Software Engineering
    177. 177. The big effort... Development 40% 60%Maintenance From Facts and Fallacies of Software Engineering
    178. 178. Bug Fixing
    179. 179. Bug FixingTodo OnGoing Done!
    180. 180. Bug FixingTodo OnGoing Done!#12 @xpto UI
    181. 181. Bug FixingTodo OnGoing Done!#12 @Yai UI
    182. 182. Bug FixingTodo OnGoing Done!oh oh #12 @xpto Yai UI
    183. 183. Bug FixingTodo OnGoing Done!#12 oh oh @xpto Yai UI
    184. 184. Bug FixingTodo OnGoing Done!abc #12 @ oh ohxpto Yai UI
    185. 185. Agile Success Factors From Agile in a Flash
    186. 186. Agile Success Factors • Freedom to change From Agile in a Flash
    187. 187. Agile Success Factors • Freedom to change • Energized team From Agile in a Flash
    188. 188. Agile Success Factors • Freedom to change • Energized team • Communication with customer From Agile in a Flash
    189. 189. Agile Success Factors • Freedom to change • Energized team • Communication with customer • Collaboration From Agile in a Flash
    190. 190. Agile Success Factors • Freedom to change • Energized team • Communication with customer • Collaboration • Attention to quality From Agile in a Flash
    191. 191. Agile Success Factors • Freedom to change • Energized team • Communication with customer • Collaboration • Attention to quality • Incrementalism From Agile in a Flash
    192. 192. Agile Success Factors • Freedom to change • Energized team • Communication with customer • Collaboration • Attention to quality • Incrementalism • Automation From Agile in a Flash
    193. 193. You!
    194. 194. Thank you!rodrigo.coutinho@outsystems.com http://www.outsystems.com

    ×