Software as a Service<br />Manifestation of a Manifesto<br />
XP Values<br />Simplicity<br />Communication<br />Feedback<br />Courage<br />Respect<br />
Values Drive Principles<br />
Principles Drive Practices<br />
Tools Help Deliver Practices<br />VCS<br />Unit Testing Frameworks<br />Acceptance Testing Frameworks<br />Build Tools<br ...
Frequency of Change<br />
Craftsmanship<br />Understanding the challenges in writing software, and finding the most effective ways to mitigate or el...
Values & TDD<br />Simplicity<br />Tests enable you to refactor your code relentlessly.<br />Testing first makes you focus ...
Personal Examples of Craftsmanship (and lack of…)<br />Context<br />Big project, big budget, small company<br />Done Well<...
isCraftsmanship<br />Writing unit tests under pressure<br />Cleaning up when you are “done”<br />Using acceptance tests to...
!isCraftsmanship<br />Meeting the “estimate” by all means<br />Not offering solutions to suboptimal designs<br />Convincin...
Future Topics<br />What is the path to craftsmanship by studying just the practices?<br />How do you stand up to the man?<...
Upcoming SlideShare
Loading in …5
×

Software as a Service

910 views

Published on

As programmers, we provide a service to our customers. To create the best possible experience for a customer, we must adhere to our values and beliefs.

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

No Downloads
Views
Total views
910
On SlideShare
0
From Embeds
0
Number of Embeds
11
Actions
Shares
0
Downloads
3
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Software as a Service

  1. 1. Software as a Service<br />Manifestation of a Manifesto<br />
  2. 2. XP Values<br />Simplicity<br />Communication<br />Feedback<br />Courage<br />Respect<br />
  3. 3. Values Drive Principles<br />
  4. 4. Principles Drive Practices<br />
  5. 5. Tools Help Deliver Practices<br />VCS<br />Unit Testing Frameworks<br />Acceptance Testing Frameworks<br />Build Tools<br />Languages<br />IDEs<br />…<br />
  6. 6. Frequency of Change<br />
  7. 7. Craftsmanship<br />Understanding the challenges in writing software, and finding the most effective ways to mitigate or eliminate them.<br />
  8. 8. Values & TDD<br />Simplicity<br />Tests enable you to refactor your code relentlessly.<br />Testing first makes you focus only on what is needed.<br />Communication<br />Tests provide objective documentation on current system behavior.<br />Feedback<br />Tests tell you when you break something.<br />Courage<br />Tests setup a framework for you to fail safely.<br />Testing first puts you on solid ground when working out business value with the customer.<br />Respect<br />Tests show respect to your organization by treating the code as the asset that it is.<br />
  9. 9. Personal Examples of Craftsmanship (and lack of…)<br />Context<br />Big project, big budget, small company<br />Done Well<br />Iterative delivery approach proved successful for organizational change<br />Done Poorly<br />Integrating the SAP team<br />
  10. 10. isCraftsmanship<br />Writing unit tests under pressure<br />Cleaning up when you are “done”<br />Using acceptance tests to help new developers understand the objectives<br />
  11. 11. !isCraftsmanship<br />Meeting the “estimate” by all means<br />Not offering solutions to suboptimal designs<br />Convincing yourself or others that a workaround is “OK, for now”<br />Hiring a developer for one month to “get back on track”<br />
  12. 12. Future Topics<br />What is the path to craftsmanship by studying just the practices?<br />How do you stand up to the man?<br />

×