Andre de Godoy Nunes

Dear readers, first I would like to apologize because my English writing is not really good. I am not an English native, however I am trying my best to improve my skills. I hope you understand that. Before starting an agile project it is usually necessary to perform some dynamics with the Scrum Team to facilitate the composition of product backlog. These dynamics are called INCEPTION meetings. In meetings like that is where the product scope statement is developed. Techniques such as Product Vision, Impact Mapping and Stories Mapping (Story Mapping) are initially applied to delimit the boundaries of the scope to the product and direct the focus of the work, which later user stories will be used to start the composition of product backlog. Creating a Clear Product Vision Product vision is quite important to the success of the product. It seems a simple statement, right? But think about how much impact it can really have in the project. A product vision gives us ...

Dear readers, first I would like to apologize because my English writing is not really good. I am not an English native, however I am trying my best to improve my skills. I hope you understand that. Regarding agile practice, it is common this question:  Why use a technique such as User Story? Using this technique assists in identifying a logical business requirement, allows breaking requirements in small pieces of requirements and also allows structuring these many requirements on a type of tree that will be a baseline for documentation. USER STORY  is a technique for identifying and organizing business requirements using stories told by users as they describe themselves their needs. User Stories are artifacts developed and managed by agile practices. Using User Stories not necessarily there is a need of interaction between actors and a system or software tool, once this interaction can put focus on the activities of the process. 3C Concept (Card, Conversation and C...