Skip to main content

Author: Marcos Ferrer

Five Critical Issues that will Define the BA Profession in the Next 10 Years

Well, loyal readers, John Dean didn’t set me off with his recent column (insufficiently fascist, entirely too rational), AND I want to think about what he said before deciding to respond.  This means we can take our discussion about BA and Identity Systems back to the highest level, before we diving for the next drill down (I know, I promised a drill down, AND this is more fun). 

In this case, the highest level issue that comes to mind regarding Identity Systems has to do with “executive sponsorship” for a national consensus on the requirements for such systems.

The ONLY source of executive sponsorship powerful enough for BAs to succeed in Identitying System Requirements are the people themselves, and yet the people (as a whole) rarely rally to a transparent process for the common good, which is exactly what we are proposing.  When the people do rally, the effect is immense.

Let’s face it – half the time, a BA can’t even get quality requirements on projects where the stakes are much smaller than for a National Identity System.  Commonly accepted “project failure” symptoms, such as Failure of user acceptance, Failure to deliver mission critical function, Missed deadlines, Over budget, Poor requirements documentation, Scope creep, etc. sound like Project Management problems to outsiders and executives. 

Most BAs know that these failures are really due to organizational resistance (including stakeholders and IT people) to the BA process.  As the famous joke goes:

Q:  How hard is it to deliver on time and under budget?

A:  It’s easy, how much must I spend by when?

Time and money are very important, but not if the what you are building gets lost in opaque, non-transparent petty politics.  The root problems tend to be deeply human ones, revolving around self respect, conflict avoidance, territoriality, work avoidance, organizational tribalism (silos and secrecy), fear of change, lack of trust and much more. 

To these deeply human issues, let us not forget simple corruption, which is less emotional and more premeditated, and cringes in the light that BA practice can bring.

This suggests the Five Great Challenges to our profession.  These are the issues that will define our profession, and will decide if BA can make a difference.  We believe that we can increase project success and reduce the overwhelming waste and failure rate that is currently an accepted part of the world of projects.  Will everyone else?

Will the society at large empower BAs to operate at the level of professionalism required of (say) accountants (transparency, completeness, accuracy)?

  1. Given the importance of the what in a project, will PMI agree that BA must precede projects, and BAs must be at least peers with PMPs, instead of answering to their time and budget needs first?
  2. Will the earliest CBAPs actually be a credit to the profession?  Will they generate successes, and word of mouth, to help boost the profession, or will they have the same outcomes as everyone else?
  3.  Can the society at large understand the BA process well enough to understand why they want to support it?
  4. What, if any, are the rules for public disclosure of private malfeasance?  There are such standards for lawyers, doctors, accountants, etc.  What will ours be?
  5. What, if any, are the rules for public disclosure of private malfeasance?  There are such standards for lawyers, doctors, accountants, etc.  What will ours be?

Mere certification cannot resolve these issues, but it is a good start.  If you believe, like I do, that BA must rise in our society, please contact me with your ideas. We must lead, or continue to follow, and I for one am tired of being an armchair quarterback.

Thanks for being my reader, if this inspired you at all, please make a comment, so BA Times can know that we care.

Have fun!

Congratulations and Condemnation!

Congratulations to John Dean for his analysis of what to do with a nearly infinite list of specific identity transactions (see March 2nd blog for the list, and John’s April blog for his ideas). 

Improve on it if you can, but I like his idea of grouping identity transactions by the “certainty” required, and using known technologies (Human Chip Insertion, Fingerprints, DNA, Retina prints, id cards) to “produce” the needed certainty.  Each “identifier” stakeholder can simply select the level of certainty they require from such a system.  This is a huge simplification, and seems to be a doable analysis.  There is evidence for the accuracy of many tests, AND we will have to consider the usual 4-D time/space complications (DNA is reliable, and is easy to plant at a crime scene).

Condemnation upon John for his focus on the “identifier” stakeholder, instead of “we the identified”, who live on the other side of such transactions (mostly). 

Leaving out the identified in these analyses is (increasingly) the cause of problems like identity theft, loss of privacy, deprivation of due process (sure, you can fix your erroneous credit record – have fun with your new full-time hobby), erosion of civil rights, and much, much more (the teen suicide who was berated on-line by the adult mother of another teen?).

Leaving us out of the requirements gives John access to a seemingly EASY solution – “chip insertion”.  The risk of crooks “stealing” someone else’s chip for illegal purposes can be dealt with by rigging the chips to self-destruct if removed or fiddled with.  I leave the problem of “counterfeit” chips for a later discussion (solution, as usual, is premature,so nyah, nyah, nyah, Mr. Dean).

This kind of solution is especially tempting for management, in spite of being clearly odious to the “workers. 

The day is coming where, if you are a convicted drug user, or a crummy boyfriend, or a whistleblower, or just a cranky person, people will be able to single you out electronically – even treat you the way we treat convicted pedophiles, just by accessing your history based on your chip id. 

Convicted pedophiles and other sexual criminals already know what this is like – no chance to really start over, always labeled.  The process created by the “identifiers” is great for labeling one for life; not so great for allowing for change and forgiveness. 

The current system protects the interests of the “identifier” stakeholders (John, language is important – can we just call them fascists?).  It assumes recidivism, and does not measure rehabilitation.  Remember – Civil Liberties are not just for people that you like.

One can claim that measuring rehabilitation is a different problem from identification.  Unlike John Dean, my perceptive readers immediately realize that if we can’t measure rehabilitation, then crime, or any “unapproved behavior” becomes a life sentence in the system John advocates.  Do you really want the letter L tattooed on your forehead for life, just because you once littered?

We’ll deal with such “identifier” requirements next time.  In the meantime, as a proof of concept for John’s analysis approach, would you agree with the following estimates of how much certainty is currently required for the following identity transactions?.

Amount of certitude required to identify:

  1. A terrorist = 0.1% (if we harass 1,000 people to actually catch one terrorist, we are satisfied – witness Guantanamo).
  2. Oneself for a driver’s license = 10% (or commerce will shut down – i.e., it is easy to fake the id required)
  3. Oneself to buy coffee and donuts = 95.0% (5% of transactions are “fraudulent”?)
  4. A death penalty convict = 70% (30% of death row inmates may not belong there, the states’ “management” are not investigating their own mistakes, of course). 
  5. A safe sex partner (varies by individual from 99.5% for those who want to witness your HIV test in person, no cheating, to 0% for Larry Craig, Senator from Idaho, who would prefer to know nothing about anyone next to him in a bathroom stall).

I finish with an important success point – small teams.  I want to make the point that our two person “team” (John Dean and myself) is (so far) enormously productive.

In perhaps 20 total person hours of actual focused, asynchronous but responsive work, we have enough grip on the scope to already despair of the sheer scope of the problem – this is good progress!

Next month (unless John tees me off again) we will contrast John’s “certainty” requirements with the requirements that “we the identified” might want to add.

Stay tuned – if we get the requirements right, it may only take one generation to finish this, and none to soon!

Personal Identification: The Soft Skills PRECEDE the Hard Skills, for BAs

Doggone and dadblast it, what is going on! Didn’t I just say the opposite last month? How is your tolerance for ambiguity holding up? Are you on top of the BABOK 1.6 BA Fundamentals? If you are aspiring to the top of your profession, and have the courage to self-identify, dive right in!

I begin by quoting the entirety of BABOK Chapter 8 here (don’t panic, it fits in the blog):

Chapter 8: Underlying Fundamentals
8.1 Introduction

8.2 Basic Skills
8.2.1 Analysis Skills

.1 Structured Analysis Techniques
.2 Issue Management
.3 Communication Skills
.4 Learning Skills
.5 Usability

8.2.2 Business/Domain Knowledge
.1 Products
.2 Processes
.3 Markets
.4 Systems
.5 Sources of Knowledge

8.2.3 IT Knowledge
.1 Paradigms
.2 Methodologies

8.3 Advanced Skills
8.3.1 Meeting Management
8.3.2 Presentation Skills
8.3.3 Decision-making Skills
8.3.4 Facilitation Skills
8.3.5 Communication Skills
8.3.6 Conflict Resolution
8.3.7 Negotiation Skills
8.3.8 Relationship Skills
8.3.9 Questioning Skills
8.3.10 Systems Thinking
8.3.11 Escalation Skills
8.3.12 Logic
8.3.13 Cultural Awareness

8.4 Leadership Skills
8.4.1 Coaching Skills
8.4.2 Facilitating Long-term Goal Setting
8.4.3 Motivational skills
8.4.4 Appraisal Skills
8.4.5 Interviewing Skills
8.4.6 Role Definition
8.4.7 Behavioral Coaching
8.4.8 Delegation skills
8.4.9 Succession Planning
8.4.10 IT Architectural Skills

8.5 Peripheral Skills
8.5.1 Sales

8.6 References

Interestingly enough, it is only the Basic Skills that have any detail at all, and those not much. What does this mean? The Basic Skills are the things that we learn just by doing IT requirements work. So many BAs cut their teeth on IT, that this is “self-evident” to many of us. The KEY skill is that we LEARN.

Self-test number 1:
Did you love school, or at least did you love reading and learning? Can you see the relationship between a three-year IT project and a three-year PhD program? WHY is it important to involve stakeholders (bet you don’t know)?

Next are the Advanced Skills. These are the sorts of things that BAs learn when (typically) we have been in a job long enough to have institutional knowledge and process experience, plus enough maturity to get along. In effect we get “promoted” to working with more people. We may not be good at it at first, but we’re here because we know so much and can share it. This thrusts us beyond analysis of processes affecting teams, into the processes of team analysis. We can lead the team to meetings, but can we make them think?

Self-test number 2:
How balanced were your SAT scores? Are you as comfortable with words as you are with complex IT and financial concepts? Would you rather listen, except when it is vital to talk?

Then comes Leadership Skills. This is Advanced Skills on steroids, in the sense that NOW you can really make it work, not just oversee uninspired meetings and team sessions.

Self-test number 3:
Do people just fall all over themselves to be with you and get your approval and do what you say because you are just plain charismatic and, frankly, too sexy for your project? If not, have you held at least one sales job for more than two years? If not, try it and find out if you want to lead.

Yes, this is the punchline. Leadership IS influence, regardless of style, or outcome. Sales IS the profession of learning to influence, for good or for evil (both kinds of leaders are out there – which will YOU be?).

SO, as you look for “people skills”, don’t forget that a successful sale means a happy customer, whether the customer is a stakeholder, an executive, a system user, a boss, or an IT team member.

Happy customers are getting what they want – good systems; no one loves a salesman who sells a lemon. If you have happy customers, you are on your way to the top of the profession.

Here is the problem we have posed: BUT, loyal reader, I am out of time this month.

© 2008 Marcos Ferrer

The Hard Skills Precede the Soft Skills for BAs

You may have noticed that I value soft skills (BA Fundamentals) very highly. The ability to work with (and at the highest levels, influence and negotiate with) people is a key success factor for senior BAs that the CBAP test cannot measure directly, but the world will always measure first.

I call on IIBA education providers to step up to this challenge – people classes are harder to do well, and look pretty flaky when done well, but they work (witness Dale Carnegie’s ongoing success, in spite of their “flaky” program).

In the meantime, soft skills without BA hard skills do not result in good BA practice. Promotions, recognition, a chance to jump to the next project before the first has collapsed, yes. Good BA practice, no.

This month is pure hard skill (thanks to blogger John Dean last month for an excellent presentation of the “sky level” overview of the problems I am presenting, and the importance of solving them).

In prior months we looked at a stakeholder type of breakdown (i.e., a top down analysis). We got individuals, businesses, governments, non-profit/non-government, and a sense of what they wanted (hire, do business, enforce the law, etc.).

There were still too many questions (what do you do if DNA is planted at a crime scene?) and too many gaps in understanding (all stakeholders need to identify employees when they hire them – what is the same, what is different).

The proposal for a new technical approach (i.e., in this case a bottom up analysis) is to move away from stakeholders for the moment, and consider actual identity transactions. Then we will see if any structure suggests itself when we consider the detailed transactions (did I say bottom up?).

There is no easy precedent for this analysis: it is huge. If anyone can suggest a technique for organizing the following list, I will try it out next month. Otherwise, I will do what I want, so there!

Here is one brainstorm – by the way, I think I’m smarter than my readers – prove me wrong!

How well does your brain compare with mine – what important transactions did we miss? What are the categories or structure we can use to organize this unruly list?

Identify a qualified BA (the CBAP is the current standard – are you helping to set it)?

  • Cross a Hostile Border
  • Cross a Welcoming Border
  • Cross a Border at some level of gradation in between (is there any set of statuses that is simpler than the exponential combinations of relations between individual countries)?
  • Identify a friend in person Identify a friend remotely Identify an enemy in person
  • Identify an enemy remotely
  • Identify family for daily stuff
  • Identify family for inheritance stuff
  • Identify the owner of an object
  • Identify the owner of non-physical property
  • Identify DNA at a crime scene
  • Identify the actual criminal regardless of DNA, which is portable
  • Paternity
  • Maternity (an issue for modern procreation, no doubt)
  • Buy candy
  • Buy cigarettes or alcohol
  • Buy medical marijuana
  • Buy stocks
  • Set up a trust
  • Create a will Identify a conspiracy group
  • Perform Identity theft
  • Counter Identity theft
  • Perform successful witness protection
  • Hide from an abuser
  • Identify an abuser
  • Control or prevent spam, viruses, worms, spyware, etc.
  • Hire a janitor
  • Hire an FBI agent
  • Hire a fast food worker
  • Hire a dockworker
  • Hire a government worker
  • Hire a CEO
  • Hire a doctor/nurse/health provider/hospital
  • Hire a CIA worker
  • Hire a CIA spy
  • Hire a black budget spy
  • Hire a president, congressman, etc.
  • Hire a police officer, detective, TSA screener
  • Buy weapons at a swap meet
  • Trade weapons for drugs on the street
  • Obtain permit to own a weapon
  • Obtain permit to carry a concealed weapon
  • Obtain permit to use a weapon in public with backing from law enforcement (this is NOT just cops)
  • Give blood
  • Give sperm
  • Adopt a child
  • Put a child up for adoption
  • Be convicted of a crime
  • Be acquitted of a crime
  • Be left in limbo re: a crime (mistrial, hung jury, never charged, never caught) omigod.

What are the categories, if any?

What did I leave out (participate in a one night stand? – follow-up one night stand if VD is detected?).

If you can’t think about this, you may be struggling with what you are working on – test yourself! ©

©2008 Marcos Ferrer

Building on Building the Right Thing

As a senior BA, I increasingly find the BA Times to be a fantastic resource for winning hearts and minds.  Kent McDonald wrote a terrific article last month about Value and Building the Right Thing.  It is a must read for any BA who is unsure what to do about difficult stakeholders (are there any other kind?).

In thinking back on numerous projects over the years I could suddenly see what Kent described – teams that were most excellent at building things right, but who were relying on stakeholders to identify and prioritize what to build.  This behavior has derailed a lot of projects (death by “superuser”*), and made Scott Adams a LOT of money for “requirements” jokes.

 

The ability to INFLUENCE a project to perform due diligence (BA) on what is possible AND worthy to build (as opposed to “recommend and retreat”) is a very advanced skill, requiring business and technical knowledge, plus people skills of significant depth and breadth.  This does not describe the experience set of most stakeholders, or even of many BAs (fundamentals, fundamentals, fundamentals!). 

 

Add to the above the natural reluctance of most stakeholders to change.  Since projects imply change, it is actually unreasonable to expect stakeholders to perform a thorough, balanced investigation and analysis.  That is our job.  Then we create as much consensus as possible.

 

Enabling this balanced investigation to happen IS a key BA move – it is the reason we are expected to speak ALL the dialects – “business” and “project” and “IT” and “user” and “developer” and “vendor”.  Failure to  find this balance can lead to projects that are infeasible, unbeneficial, too expensive, unacceptable to some or all stakeholders, and in some cases just funny (did you hear the one about the team that decided to re-invent accounting for the stakeholder who had to receive and cut checks across thousands of accounts, but who didn’t like accounting systems?).

 

SOOOO, deep breath.  Back we go to our exercise in identity requirements.  The reason I am walking through this exercise with you, the fearless reader, is that my experience has taught me that my value is focusing on value.  At this time, I can think of no greater value to freedom and democracy than a careful analysis of the requirements for identity systems.

 

BUT, loyal reader, I am out of time this month.  Here is the problem we have posed:

 

FOR NEXT MONTH:

 

To reassure ourselves that we REALLY understand the stakeholders for identity systems (see prior columns), we will try to list the “identity transactions” that might occur in society, and we will try to match these transactions to the kinds of stakeholders we are aware of so far (individuals, businesses, government, and other organizations).

 

How many identity transactions can you think of that have significant differences in identity requirements (purchase goods, fly to Palestine, get a driver’s license, buy a gun, become a citizen, visit Niagara Falls), or how would you elicit such a list?  Is this why no one has ever done it?

 

Potential answers will be discussed next month, and incorporated into the case study.  The best reader response will get acknowledged next month (send a picture with your response!) and will undoubtedly receive a large raise in the near future, just for rising above the pack.

 

 ALSO:  A tip of the hat goes out next month to anyone who shares a story about “death by superuser”.

 

© 2008 Marcos Ferrer