• All Things Distributed: Working Backwards
  “To ensure that a service meets the needs of the customer we use a process called “Working Backwards” in which you start with your customer and work your way backwards until you get to the minimum set of technology requirements to satisfy what you tr
  (tags: Amazon Software development business management agile process)

Related Posts

• links for 2006-10-08 --  Scrum (development) - Wikipedia, the free encyclopedia “Scrum is a lightweight agile method for software development.” (tags: Agile Development methodology software management scrum Design) Scrum (management) - Wikipedia, the free encyclopedia “Scrum is an agile method for project management....
• links for 2006-10-19 --  Scrum et al. - Google Video “Scrum is an amazingly simple process that causes many, many changes when it is implemented.” Thank you Google for sharing (tags: Agile Scrum Dev methodology management process programming productivity software video) What is...
• links for 2006-10-20 --  Scrum Agile Process “Scrum is an agile process for developing software. With Scrum, projects progress via a series of month-long iterations called sprints.Scrum is an agile process for developing software. With Scrum, projects progress via a series of month-long...
• links for 2006-11-01 --  Agile Software Development Management Resources | VersionOne Velocity is an extremely simple, powerful method for accurately measuring the rate at which teams consistently deliver business value. To calculate velocity, simply add up the estimates of the features (user stories,...
• links for 2006-10-29 --  Cory Foy: Principles, not Processes True: “The only way to really become agile is to look at the practices and understand the principles behind why you would want to do them, then fit them into your organization.” (tags: Agile...
• links for 2006-12-04 --  Mountain Goat Software - Advantages of User Stories for Requirements - Agile Development Training and Consulting “Because stories exhibit some of the same characteristics of use cases or traditional requirements statements, it’s important to look at what distinguishes stories...
• links for 2007-01-02 --  InfoQ: Resolutions: Integrity of Code and Conduct “Agile Code: The ability to accommodate changing requirements is directly related to the flexibility and malleability of the code base. Agile code is: loosely coupled, highly cohesive, fully tested, expressive, rarely duplicated”...

Related posts brought to you by Yet Another Related Posts Plugin.