AGILE IN ACTION

Tuesday, October 30, 2007

Poster at d-tools

Posted by Simon Baker
Tags: poster
Poster at d-tools Originally uploaded by sjb140470
Read more...

Saturday, October 27, 2007

Vertical slicing

Posted by Simon Baker
Read more...

Wednesday, October 24, 2007

It's showtime

Posted by Simon Baker
Showcase is popular Originally uploaded by sjb140470
Read more...

Sunday, October 21, 2007

Continuous Integration using Hudson

Posted by Simon Baker
We've always used Cruisecontrol but in the last project we spent a lot of time deep in the code and it stank, big time. So despite, the facelift , we've decided to try Hudson on our new project. So far, so good. We've got our avatars on the big visible build screen and we've got some new build hats from the Oktoberfest .
Read more... Comments: 1

Saturday, October 13, 2007

Humble beginnings

Posted by Simon Baker
We recently started working with a new client and have been located in a new office. The pictures below were taken on the first day in the first hour with people busy setting up their machines. We'll be starting Iteration Zero on Wednesday .
Read more...

The power of colocation

Posted by Simon Baker
Brian Marick recently blogged about power steering in reference to that old XP metaphor of the Customer driving the project like a person driving a car. He says: When you drive, you don't think about the steering wheel, you simply think about turning the car, and it turns. But when the power steering goes out, what was once a simple reflex is now a conscious act. In our new office, we're colocated with our Product Owners , our Product Sponsor, and our customer. The opportunity to be colocated to this degree doesn't happen often. It's usually obstructed by silly reasons such as office politics, silos and hierarchy, or part-time team members from the business side having to be located elsewhere. Our thanks go to our client for recognising the benefits of colocation and for wanting to do things properly. Everyone is buzzing about the approach we're using and I'm excited about facilitatating power steering to achieve continuously improving levels of customer collaboration and feedback and value flow to our customer.

Tuesday, October 9, 2007

Self-discipline or just discipline?

Posted by Simon Baker
A short while ago, Brian Marick identified discipline as one of four values missing from the Agile Manifesto . Brian was recently asked:
Read more...

Sunday, October 7, 2007

A Product Owner has many skills

Posted by Simon Baker
The Product Owner needs a blend of the skills usually separated by traditional roles, should have empathy with the customers and and should have some knowledge of how software is developed and deployed. Product Owner Skills Originally uploaded by sjb140470 Product Management Synthesises the needs of the customers and the various stakeholders. Performs competitive research and analysis. Assists with product marketing strategy and devises pricing model. Conducts acceptance tests. Demonstrates the product to customers. Collects customer feedback and transforms it into new features or enhancements. Project Management Responsible for the business value delivered by the team. Helps the team plan the content of each iteration given costs (estimates) and risks. Provides feedback and makes decisions that steer the team based on what's delivered every iteration. Communicates progress to the Product Sponsor and stakeholders. Programme Management Why not put the Product Owner in charge of the budget? After all, he is responsible for maximising return on investment in every iteration. Business Analyst Articulates the product vision and business strategy to the team and defines goals that realise the product vision. Writes and evolves user stories to a suitable level of detail given their position in the Product Backlog. Communicates the details of the user stories so they can be captured as acceptance tests. Prioritises user stories in the Product Backlog by business value. Manages the Product Backlog in response to changes. Business Intelligence Collect information about the product to help make better decisions relating to future functionality and business value.

Accountability != Responsibility

Posted by Simon Baker
Via Christopher Avery . Accountability is an agreement to be held to account by another for your operations or the results you produce. If meetings are called to determine who was acccountable, you're looking for people who are trying their best to hide. Not the sign of a healthy culture. Responsibility is a feeling of ownership and stands out when you are leading, learning, correcting, and improving. The sign of a healthy, high-performing culture.
Comments: 1

Treat estimates as solution budget

Posted by Simon Baker
Jeff Patton gives us some good advice about how we view our estimates:
Read more...

Creative Commons Licence

Recent Posts

  1. Debugging Grails Database Performance
  2. Grails for Hipsters
  3. Governance - Friend or Foe?
  4. The Energized Work lab is moving aboard ship
  5. Gus Power on the future of software development at The CW500 Club
  6. Agile On The Beach: Session: How Are We Doing?
  7. Presenting BuyaPowa at Hacker News London
  8. Knowledge nuggets from Kent Beck
  9. There's gold in them thar hills
  10. No Bull: An author's note

Archives

  1. 2013 (2)
  2. 2012 (27)
  3. 2011 (24)
  4. 2010 (31)
  5. 2009 (41)
  6. 2008 (69)
  7. 2007 (152)
    1. December (11)
    2. November (7)
    3. October (17)
      1. Poster at d-tools
      2. Vertical slicing
      3. It's showtime
      4. Continuous Integration using Hudson
      5. Humble beginnings
      6. The power of colocation
      7. Self-discipline or just discipline?
      8. A Product Owner has many skills
      9. Accountability != Responsibility
      10. Treat estimates as solution budget
      11. Have you compromised your agility?
      12. Corporate idiocracy
      13. Mary Poppendieck at the Agile Business Conference
      14. Ken Schwaber at the Agile Business Conference
      15. You can't own something part-time
      16. At the Agile Business Conference
      17. Baker's Dozen poster
    4. September (8)
    5. August (7)
    6. July (13)
    7. June (15)
    8. May (24)
    9. April (14)
    10. March (19)
    11. February (7)
    12. January (10)
  8. 2006 (128)
  9. 2005 (63)
  10. 2004 (2)

Tags

agile (43) big visible chart (15) conference (43) culture (18) extreme programming (22) leadership (18) lean (47) people (27) planning (17) retrospective (18) scrum (41) story (19) team (30) testing (19) xpday (19)