You put yourself in the shoes of someone using the product and consider all the questions you would have. You would include questions that other folks asked when you shared the press release and you include questions that define what the product is good for. It includes questions that came up when we wrote the press release. Here's where we add meat to the skeleton provided by the press release.
The Working Backwards product definition process is all about is fleshing out the concept and achieving clarity of thought about what we will ultimately go off and build. The product definition process works backwards in the following way: we start by writing the documents we'll need at launch (the press release and the faq) and then work towards documents that are closer to the implementation.
The goal is to drive simplicity through a continuous, explicit customer focus. To ensure that a service meets the needs of the customer (and not more than that) 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 try to achieve. Each of these services require a strong focus on who their customers are, regardless whether they are externally or internally. In some sense you can see these services as small startups within the walls of a bigger company. The services have a strong ownership model, which combined with the small team size is intended to make it very easy to innovate.
#Working backwards software
In the fine grained services approach that we use at Amazon, services do not only represent a software structure but also the organizational structure.
0 kommentar(er)
