Sriram some anti-patterns of agile software development

  • 661 views
Uploaded on

 

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
661
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
13
Comments
0
Likes
0

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. Some anti-patterns of agile software development Sriram Narayan ThoughtWorks
  • 2. Velocity as target
    • stages within an iteration
    • each stage is inventory for the next
    • minimize build up of inventory
    • velocity is a measure of end to end flow
    • purpose of velocity is to minimize waste
    • difficult to achieve this without on-site customer
  • 3. Points estimation under fixed time and scope
    • estimating in points makes sense when scope is negotiable
    • If budget, schedule, quality and scope are fixed at the outset, then estimation becomes commitment
    • commitment is better served by real units of time
  • 4. Not failing fast enough
    • Fail fast is enabled by tight feedback loops
    • Feedback must be of good quality
    • Best feedback is tested functionality
    • Iterative versus incremental
    • But what about costs?
  • 5. Risk adjusted costs
  • 6. Cost-ineffective pair programming
    • For a project that runs for, say six months or more, there should no extra development cost on account of pair programming.
    • Pairing pays off in several intangile, hard-to-measure ways.
    • How to see if there is extra cost?
  • 7. Questions? Comments? [email_address]