Business Analysis in Practice
|
Some years ago, I was asked: ‘What is the difference between a Business Analyst and a Business Architect?’ My reply was that a Business Architect was someone who can apply the techniques of business analysis to an architectural framework in a technology-agnostic way. There are other differences but that was what […] March 25th, 2017 | Category: Business architecture | 2 comments For any kind of enterprise-wide change initiative, if you derive your backlog of Business Stories only from interviews with users, you may to end up with a patchwork of individual needs that don’t necessarily hang together, some of which will conflict with each other and which won’t give you the enterprise picture.
March 20th, 2017 | Tags: agile, Product Backlog, user stories, User Story | Category: Business architecture | Leave a comment Several years ago a major software consultancy built a Pega solution for a client and within two years of deploying it, the client was having to rebuild it themselves. It’s not an uncommon scenario. The client brought me in, because of my background as a Pega Business Architect, to take […] It’s not news to you that collaboration is key to success in many fields, so it might shock you, as it shocks Software Delivery Managers and Scrum Masters when I say: “I don’t care whether you deliver your software.” OK, you got me, I do care because ultimately we are striving towards the same […] I admit it. I have a problem with user stories. Not with the Actor/Narrative/Benefit syntax or the idea of adding acceptance criteria or the idea of valuing conversation over documentation. I love all that. I have a problem with the name “user” stories. I’ve been applying Agile principles for about ten […] In 2012 one of my readers contacted me to ask whether business rules and user story acceptance criteria could be considered the same thing. I answered in a blog post that they should not. However, in 2013 I learned decision modelling, specifically, The Decision Model (TDM) and I was taught by […] July 13th, 2016 | Tags: Acceptance Criteria, agile, business architecture, Decision Model, DMN, TDM, User Story | Category: Business architecture, Decision Modelling | 2 comments Collaboration isn’t some kind of Arthurian round table. It’s not about everyone having their say or having equal weight assigned to their say. I have no time for the old style of business analyst who spends months crafting 3,000 pages of text (but not a single model) to describe requirements and […] July 5th, 2016 | Tags: collaboration | Category: Business architecture, Decision Modelling, General, Process Modelling | Leave a comment Most projects I’ve worked on have had a set of strategic goals that the project was supposed to realise. However, most people working on those projects could not say what the goals were or where they could be looked up. Even on projects where the goals were stated and available, they […] April 27th, 2016 | Category: Business architecture | 2 comments You are probably familiar with the Agile Manifesto that was written in 2001 by several forward-thinking software developers. However, it is a manifesto for software development and, as you may have seen in a previous post, business architecture is about more than software requirements. Does that mean we cannot apply the […] March 10th, 2016 | Tags: agile, business architecture | Category: Business architecture | 4 comments In my experience, not many people distinguish between “Requirements Analyst” and “Business Architect”. I consider them very different roles and here are some of my thoughts on the subject. A Requirements Analyst A Business Architect Asks what the user wants. Asks what the business needs. Asks how the user benefits from performing a task. Asks […] March 3rd, 2016 | Tags: Business Architect, business architecture, Pega Business Architect, requirements analysis, Requirements analyst | Category: Business architecture | Leave a comment |
Recent PostsArchives
|