Our Development Plans Part II
The key deliverable to give the developers will be the “user story”, from Wikipedia
In software development and product management, a user story is one or more sentences in the everyday or business language of the end user or user of a system that captures what a user does or needs to do as part of his or her job function. User stories are used with agile software development methodologies as the basis for defining the functions a business system must provide, and to facilitate requirements management. It captures the 'who', 'what' and 'why' of a requirement in a simple, concise way.
Defining the needs of a system of the size of People, Ideas & Objects needs to go through this process of the Detailed Specification to help manage the scope of the application. What is necessary in the application can not be left open ended when the developers sit down and begin their work. There must be a defined product that they are setting out to complete. That is one of the purposes of the Detailed Specification.
Capturing the needs of the users, the producers, the Joint Operating Committees, the service providers and the service industry into these specifications will also eliminate the redundancies in developing similar systems for similar needs. The output from this phase of development will be large. The more people that we have looking at the output of this phase and the more errors that we can correct, the better the systems will be and the less overall costs.
It is imperative that people understand that People, Ideas & Objects are user driven developments. We have chosen this methodology as this provides the highest quality of systems available. Participation should be looked upon as an opportunity to make a difference in the development of the industry, its profitability and its innovativeness. How the industry solves its problems and addresses its opportunities should be as a result of the actions taken by the user community to change the software to meet those challenges. Users are in control of the tools that make the industry what it is.
This is the importance of user communities in the near future. What they may have looked like in the past was more predefined by the softwares needs or the organizational context. With the People, Ideas & Objects user community the organization is defined and supported by the software. And the user community defines the software. So the shoe is on the other foot as they would say. I think that you can see with the Preliminary Specification how the software definition redefines how the industry operates. This power is being placed in the hands of the user community. User community participation is now at the top of the food chain.
The Preliminary Specification provides the oil and gas producer with the most profitable means of oil and gas operations. People, Ideas & Objects Revenue Model specifies the means in which investors can participate in these user defined software developments. Users are welcome to join me here. Together we can begin to meet the future demands for energy.