BA digest, January 2021: how to reject a feature request and estimate the cost of an error in BP

Hello! My name is Yura, I am a BA Tech Lead at NIX, and this is the first issue of the digest for business analysts. In it you will find, in my opinion, valuable and noteworthy materials over the past month. Enjoy!





In brackets near the headings - the difficulty level of the article (Normal * β†’ Hard ** β†’ Expert ***) and the approximate time to study the material.





Business Analysis

  • Sorting Through the Pile: Classifying Customer Requirements (*, 6 min) . Classification of requirements from Wiegers' grandfather for the smallest. Help for beginners, joy for old people.





  • Tactfully rejecting feature requests (**, 9 min) . Each of us got into a situation when another important request for a feature comes, but it β€œdoes not fit” into the product - it does not help the implementation of a business idea, breaks the architecture, does not benefit the target audience, and so on. And to refuse the same client is inconvenient, he is a client. So, in the article there are recommendations on how the asking person can understand why the feature is not needed after a few simple steps and techniques.





  • Where does the company's money go, or How to estimate the cost of an error in business processes (**, 6 min) . The article discusses an example of calculating financial losses due to imperfect business processes, types of errors, how to look for them and what to do with them. Relevant for process analysts who interact directly with the business. For the rest, it will not be harmful to overall development.





  • The 10 Attitudes of Outstanding Product Owners (**, 7 min) . Who has not yet come across - to find out, and who knows - to remember what lies at the heart of this role. These principles apply equally to analysts.





  • Top 7 Hybrid Business Analysis roles (*, 10 ). β€œ+…”. , , – .





  • Writing Kick-Ass User Stories (*, 7 ). , , , User Stories.





  • The Business Value of Better Requirements (*, 6 ). β€œ ”.





  • No One Expects the Requirements Inquisition: Asking Next-Level Questions (*, 6 ). (!). , needs.





  • . - (**, 10 ). SoftServe , , , .





  • Build effective Minimum Viable Products with the MVP Experiment Canvas (**, 13 ). MVP -.





  • . , (**, 15 ). , , , - β€œβ€, , Junior'. , , .





  • Lightning Cast: Resistance to Change (*, 4 ). Goldratt’s Four Quadrants on Change – .





  • Your Product Has Too Many Features (*, 6 ). β€œβ€ Facebook / Amazon, - .





  • Beware SAFe (the Scaled Agile Framework for Enterprise), an Unholy Incarnation of Darkness (*, 14 ). , – SAFe, β€œβ€. SAFe, , – . , – , , β€œβ€. β€œβ€, , SAFe.





  • , SAF’? , .





  • Ρ” . - Product Manager (**, 10 ). , .





  • A comprehensive list of UX design methods & deliverables (*, 12 ). – + . , , .





  • How to Spot and Prevent Useless Meetings (*, 4 ). , , β€œβ€, , , , .





  • IT- - (*, 4 ). , :)





  • UI cheat sheet: Icon categories + icon style reference guide (**, 21 min) . Another gorgeous guide from Tessa Gadd, this time on how to make icons correctly.








All Articles