I was recently asked by an "Agile" proponent if I thought our "PRIDE" methodologies were too rigid for today's fast-paced Information Technology world, that perhaps it was too bureaucratic. First, I pointed out that "PRIDE" was more of a way of thinking as opposed to anything else. You can remove all of the documentation associated with the methodologies, including the forms, and still produce a system for example. This took him aback somewhat as he had thought of "PRIDE" as an inflexible paper mill...
Discusses the implementation of a robust Systems Design Methodology.
Author: Tim Bryce
Over the last four decades I have met a lot of Systems Analysts in a lot of different industries. Some impressed me greatly by their knowledge of their business and the systems they designed, but I have also met a lot of duds along the way. When I think about the better ones, I consider the attributes they share which I can narrow down to three areas
In its simplest form, a Feasibility Study represents a definition of a problem or opportunity to be studied, an analysis of the current mode of operation, a definition of requirements, an evaluation of alternatives, and an agreed upon course of action. As such, the activities for preparing a Feasibility Study are generic in nature and can be applied to any type of project, be it for systems and software development making an acquisition, or any other project.
So you want to be a Business Analyst? “Analyst – analyse thyself….” This is what Business Analysts do in the real world when embarking on a new project: they analyse…
So – as any good BA should do when undertaking a new project – analyse what are your objectives in wanting to move to a new career as a Business Analyst. Put another way, how will you know (once you have done it) that it was a good move to make?
The difference between an art and a science is subtle but significant. An art form is based on the intuitiveness of the person performing the work, something that is difficult, if not impossible, to pass on to another human being. For example, apprentices serving under an artist may try for years to emulate the master, but may never attain his level of skill and creativity. In contrast, a science is based on a governing body of concepts and principles and, as such, can be easily taught to others.
THE ANALYST (aka, Systems Analyst, Systems Engineer, Systems Architect, Business Analyst) - requires specifications about the end-User's information requirements in order to design a system solution. This is normally based on a definition of the user's business actions and/or decisions to be supported. Following the system design, the Analyst produces the specifications required by the Programmer and DBA to fulfill their part of the puzzle. From this perspective, the Analyst is the translator between the end-User and the Programmers and DBAs. Each party has his own unique perspective of the puzzle and, as such, requires different "specifications." To compound the problem though, the role of the Analyst sharply diminished over the years, leaving it to the Programmers to try and determine what the end-User needs, a skill they are typically not trained or suited for.
I have been very fortunate to see a lot of this history first hand. I have observed changes not just in terms of systems and computers, but also how the trade press has evolved and the profession in general. It has been an interesting ride.
Throughout all of this, there have been some very intelligent people who have impacted the industry, there have also been quite a few charlatans, but there has only been a handful of true geniuses, one of which was Robert W. Beamer who passed away just a couple of years ago. Bob was the father of ASCII code, without which we wouldn't have the computers of today, the Internet, the billions of dollars owned by Bill Gates, or this document.
I always find it amusing when I tell a young person in this industry that I worked with punch cards and plastic templates years ago. Its kind of the same dumbfounded look I get from my kids when I tell them we used to watch black and white television with three channels, no remote control, and station signoffs at midnight. It has been my observation that our younger workers do not have a sense of history; this is particularly apparent in the systems world. If they do not have an appreciation of whence we came, I doubt they will have an appreciation of where we should be going. Consequently, I have assembled the following chronology of events in the hopes this will provide some insight as to how the systems industry has evolved to its current state. I'm sure I could turn this into a lengthy dissertation but, instead, I will try to be brief and to the point. Further, the following will have little concern for academic developments but rather how systems have been implemented in practice in the corporate world.
Recently I wrote a paper on the general state of craftsmanship which was geared more for public consumption as opposed to any specific industry. To my way of thinking, craftsmanship is a universal concept that touches all industries, regardless if they are product or service related. This resulted in a flurry of e-mails to me questioning how it pertains to specific types of work, including Business Systems Analysis (BSA) which, of course, is applicable but I question whether we have truly realized craftsmanship in this field.
From the outset, let me say unequivocally that business systems analysis is not a new concept and has been with us for a long time, actually predating the modern computer era of the 20th century. Prior to this, companies had formal "Systems & Procedures" departments with analysts focusing on streamlining business processes and primarily using paper and manual procedures. As tabulating and other office equipment emerged, they were responsible for their integration into the business. But as computers were introduced, a new function was devised that greatly impacted the future of analysts, namely programmers.
Business analysts often end up in this role by accident, as their careers evolve. They are perhaps called on to work jointly with the business or computer department, and end up linking the two. Two major sources of BA professionals can therefore be considered: the computer world (e.g. architects, developers) and the business world.
What is the best background for becoming a business analyst? The debate is still ongoing in the community. Both have their qualities and their faults—computer people have a tendency to anticipate the solution while mangers sometimes lack the knowledge to interact with IT.
I believe that good business analysts are above all specialists in business analysis. They have backgrounds in both disciplines and act as a bridge between the two worlds.
Business analysts go by many titles one of them being Management Consultant. In this article, Tony Jacowski talks about the management consulting career.
Author: Tony Jacowski
brought to you by enabling practitioners & organizations to achieve their goals using: