https://cobaltcorner.com/ Recent content in Home on Cobalt Corner https://cobaltcorner.com/images/papermod-cover.png https://cobaltcorner.com/images/papermod-cover.png Hugo en Andrew Wiedemann Sun, 23 Aug 2026 13:31:03 -0600 https://cobaltcorner.com/about/ Sun, 23 Aug 2026 13:31:03 -0600 https://cobaltcorner.com/about/ <p>In my free time I like to mess around with computers. I have taught myself programming and I have a bit of a homelab. I also host this site myself. Currently my programming goals are to learn more about systems programming and learn more about how operating systems and databases work.</p> <p>I have worked as a technical Business Analyst for a small consultancy working on ERP systems since 2019, which is very different from the Chemistry education I have. My hobby of programing has been very beneficial in my work as it has given me the knowledge of thinking through logic, APIs, most of the programming jargon. I can have discussions with developers using their language so that I can develop a deep understanding of how a project works which makes it fairly easy to communicate the details to business users and answer their questions about how something works.</p> https://cobaltcorner.com/posts/user-stories/ Sun, 23 Aug 2026 13:01:31 -0600 https://cobaltcorner.com/posts/user-stories/ <blockquote> <p>This is an entry in my series of post about techniques that are useful to Business Analysts. I am using the IIBA’s BABOK V3 (2015) as my source for what a user story it. It is worth keeping in mind that I come at this a as a IT Business Analyst from a consultancy that works on ERP systems</p> </blockquote> <p>A user story is one or two sentences that captures what is needed out of a solution. They take a the view of what a user would be trying accomplish when they use the functionality.Users stories are used to define what features should be included in a solution. They are not intended to be complete requirements which makes them more useful when trying to scope a project rather then an explicit list of what needs to be built. User stories are suppose to be short and focused on a single activity. Having them focused is very useful as it allows them to be used as a checklist to confirm that the solution meets the needs of the users. I have found this useful as if they are too broad then there are times where they can be half met which makes it difficult to communicate progress to stakeholders. User stories are not something that works for every project. When the project is strictly integrating data between two systems there are no real “users” of what is being developed making user stories not useful. They are useful any time a business process or product is user facing.</p> https://cobaltcorner.com/projects/stub/ Sat, 01 Aug 2026 13:01:31 -0600 https://cobaltcorner.com/projects/stub/ <p>Projet write ups in progress</p>