![]() How did the project leader understand it? At this stage, however, the most important thing is to make the vision coherent. Interestingly, the first sketches usually have nothing in common with the final product. You should start visualizing as soon as possible and discuss individual elements of product functionalities based on sketches. If you describe in words a product that you would like to build, there is a high probability that the development team will understand your vision in a different way than you intended. Why? The reason is very simple - everyone interprets reality in their own way, has an idea of something in the mind and may not accurately present this vision to the other party. There will be discrepancies in the product vision from the very beginning. While analyzing the graph above, I will present in a step-by-step manner all possible threats and suggest how to fight them. Then come further misunderstandings, misinterpretations and, eventually, the project quickly goes down the wrong path of development. Problems often arise from the very beginning, when the client comes with a (theoretically) final product vision and presents it to the team. I think it shows very well that big discrepancies and a lack of vision may appear in software development projects between all participants and people involved. Image source: You know this picture, right? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |