As someone who's been involved in software development since the early 2000s, analysis and architecture are just par for the course. But when business analysis emerged as a key player in the game, I jumped at the chance to dive in headfirst. I completed my business analysis diploma in the field of IT and immediately put my newfound skills to use on my team.
Then, a few years down the line, fate intervened once again. I was presented with an opportunity to learn about a completely different industry, and I was eager to see how I could apply my analysis and architecture skills in this new context. It wasn't long before I was working as a solution analyst/architect, combining my technical know-how with a keen eye for problem-solving.
These days, I'm putting every single one of my skills to the test in my current role. From analysis to architecture to technical prowess, I'm constantly pushing myself to produce products that are both valuable and feasible for our clients. And let me tell you, there's never a dull moment!
When it comes to business analysis, I'm in my happy place. No matter what industry you're in, the goal is always the same: to go from zero understanding to total mastery. There's nothing more satisfying than watching that progression unfold.
So, how do I get the job done? Well, I've got a trusty toolbox full of go-to tools that I rely on time and time again. Here's just a taste of what's inside:
Conceptual diagramming: I use this to get a high-level understanding of the problem at hand and explore possible solutions.
Contextual diagramming: This helps me map out the different touchpoints between systems and stakeholders, giving me a better understanding of the big picture.
High and low-level activity diagramming: I turn to BPMN and diagram narration to make sure I've got a handle on current and future processes.
Entity relational diagramming: This helps me define relationships between different entities down to the nitty-gritty field level.
Mockups and wireframes: These are a great way to test the waters with stakeholders before diving headfirst into development.
MS Excel: This is my go-to for all things data-related.
MS Word: When it's time to finalize business and functional requirements documentation, I turn to this trusty program.
MS PowerPoint: Finally, when it's time to tell the story and confirm requirements, there's nothing like a killer PowerPoint presentation to seal the deal.
So, there you have it: my trusty toolbox, ready to tackle any business analysis challenge that comes my way. There are definitely more tools available, like event tables which I use once a year if that, but these have carried me through every challenge to date.
Business analysis is all well and good, but it's the solution analysis and architecture where the real magic happens. That's where I discovered my talent for seeing the big picture, while still being able to dive deep into the nitty-gritty details.
Of course, I wouldn't have been able to get to this point without my business analysis skills and trusty toolbox of techniques. But it's my knack for quickly learning new technologies that really helps me understand the ins and outs of the products and solutions available for enterprise projects.
By working closely with business analysts, product owners, and project managers, I can design a solid foundation for project planning, dive into detailed business analysis, and make sure development teams know exactly where they fit in. It's the most critical part of the analysis process, but also the most fun, in my opinion!
System architecture has been a passion of mine since the beginning of my programming journey. It's like solving a big, complicated puzzle - and I love nothing more than rising to the challenge. Even if I later find out that other people have already solved the same puzzles in different ways, I always enjoy discussing, testing, and implementing architectures for products with other brilliant architects and developers.
When it comes to my own architectures, I've always followed the KISS (keep-it-simple-stupid) principle. I believe in prioritizing easy maintenance and shorter learning curves for new developers over flashy designs that are difficult for anyone else to understand. That's what makes architecting so fun - finding the perfect balance between re-usability and maintainability.