Software as a Service
Upcoming SlideShare
Loading in...5
×
 

Software as a Service

on

  • 984 views

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.

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.

Statistics

Views

Total Views
984
Views on SlideShare
975
Embed Views
9

Actions

Likes
1
Downloads
1
Comments
0

1 Embed 9

http://www.slideshare.net 9

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Software as a Service Software as a Service Presentation Transcript

  • Software as a Service
    Manifestation of a Manifesto
  • XP Values
    Simplicity
    Communication
    Feedback
    Courage
    Respect
  • Values Drive Principles
  • Principles Drive Practices
  • Tools Help Deliver Practices
    VCS
    Unit Testing Frameworks
    Acceptance Testing Frameworks
    Build Tools
    Languages
    IDEs

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