The main goal of the business idea formalization is to shape and assess future product. Formalized idea can then be described as a task for implementation. As a result, software requirements document (system requirements specification) is an agreement between business and software developers about how the resulting product should looks like. But the story is not finished, since the requirements tend to be changed throughout the software product lifecycle, which requires monitoring and adjustments in: User stories, Use cases, Acceptance tests
User
stories
We use User Story to hold and keep up to date the system-wide process, overall system behavior or interoperation rule.
Use
cases
Use case is a business-feature that brings the value to particular user. Usualy we formalise it as short intro of the value and wireframe
Acceptance
tests
One of the ways to match expectation of the product owner is to track acceptance criteria for each feature as detailed step-by-step test
Innovation Games, developed by Luke Hohmann, are successfully help to eliminate the barriers between the business people and development teams to achieve common vision. There are four innovative methods we use to define business requirements:
"Product Box" to identify most valuable business requirements for a product,
"Me and My Shadow" and "Start Your Day" for user cases identification,
"Story mapping" for particular backlog description.
Priority task for software is to be user-friendly. Usability is another dimension of the product quality and before the UI/UX is suggested the inputs goes through several stages of formalization: Information, Navigation, Interface
Information
Information decomposition is activity for this stage. We need to find, evaluate and highlight main business-messages to deliver information clearly.
Navigation
Set of business-messages and its relations creates the graph. We analyse it to fetch optimal screen-flow so that user gets the value he has looking for.
Interface
UI is a compilation of information and navigation both. We represent it as clickable prototype to test product's usability on early stages of product planning.
Your Customer does not want to know about the complexity of your systems. Implementing of modern techniques in conjunction with the basic laws of Cooper, Fitts and Hick help maximize the effectiveness of the complex data presentation. Clear and easy-to-use ptopotype of the feature or whole product is the best way to take Customer's feedback into account.