Fixed Price Contracts in Agile
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

Fixed Price Contracts in Agile

  • 1,627 views
Uploaded on

My presentation from the Rally Agile Success Tour in Chicago - October 15, 2009

My presentation from the Rally Agile Success Tour in Chicago - October 15, 2009

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
1,627
On Slideshare
1,600
From Embeds
27
Number of Embeds
4

Actions

Shares
Downloads
34
Comments
0
Likes
1

Embeds 27

http://agilemusings.com 17
http://www.linkedin.com 6
https://www.linkedin.com 3
http://www.slideshare.net 1

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. Fixed Price Contracts in Agile
    Rally Success Tour – Chicago, IL
    October 15, 2009
    Brendan Flynn
  • 2. We’re ShopLocal
    ShopLocal uses innovative digital marketing techniques to connect shoppers with local retailers.
    Key Points:
    Pioneered the Use of Online Circulars
    Developed first of its kind technology platform for digitizing and versioning, local DMA print circular data
    375+ Million Visits with 5+ Billion Page Views Annually to SmartCircular sites
    Founded in 1999 and headquartered in Chicago, IL
    Owned by Gannett Company, and partnered with PointRoll
  • 3. We’re ShopLocal
  • 4. Agile @ShopLocal
    Practicing Scrum since 2007
    Multiple product lines
    Multiple teams responsible for:
    Data Platform / API
    Custom client projects
    Product support / maintenance
    Code releases every week
    Using Rally since Feb. 2008
  • 5. We were practicing Agile… but not with clients
    Our contracts were not aligned with how we developed software
    Clients/Sales expect a fixed time, cost, scope contract
    Features were wide open to interpretation
    No acceptance criteria defined in contracts
    Schedules were not based on empirical data
    The dreaded change request
  • 6. Impacts
    Externally
    Missed delivery dates
    Misinterpreted requirements
    Clients had no visibility of how much work was left within a given release
    Internally
    Sales/account teams were working outside of delivery teams
    Increased cycle time
    No understanding of how project fell into overall programs / capacity
  • 7. Adapting Fixed Contracts to Work with Agile
    Optimize the whole, not just your development practices
    Value Stream Analysis – concept to cash
    User Stories & Acceptance Criteria in plain language, not technical jargon
    Clear definitions of DONE
    Limits defining what the feature does not include
    User Story workshops with clients/teams
    Client UAT sessions at end of each iteration
    Adaptive Release Plans
    Exchange Requests not Change Requests
  • 8. Results to Date
    Internally
    Empowered team, ability to influence release plan
    Iterative UAT cycles, mitigate gotchas
    Program level visibility to team and management
    Happy Sales and Product Management
    Externally
    Value of adaptive release planning
    Fully functioning features every 2 weeks
    Projects consistently delivered on time
    Client confidence/trust
  • 9. Continue the conversation…
    http://shoplocalblog.com
    @shoplocal on Twitter
    Brendan Flynn, Sr. Director of Project Management
    bflynn@shoplocal.com
    @hbflynn on Twitter
    Blog: http://agilemusings.com