Saturday, May 29, 2010

Another attempt to understand Business Analysts

I am sure Ann Hall over at itbusinessedge.com is a nice person, and I appreciate her interest in what Business Analysts are or do, but she is not helping by quoting people who say my real key skill is customer service... have a look at http://www.itbusinessedge.com/cm/blogs/all/does-a-business-analysts-background-matter/?cs=41432#cf

Thursday, May 27, 2010

Conversations

Linked In is a pretty good place for conversations these days, here is one on "Should the BA be a SME?" at http://bit.ly/9VhruQ (No fair guessing my view before reading it...)

Thursday, May 20, 2010

Blogger's Block

I seem to be posting less often these days. and if no one else has coined the term, I will call it "Blogger's Block."

I have said before that when blogging first appeared, I paid it no mind as it seemed that they were all (mostly young) people's public diaries; eventually I saw that there were more and more blogs that were about topics of interest, the main ones for me being work-related on business analysis and methodologies and such. One of these must have been on blogger.com, which basically said I could have a blog too, just sign up...so I did. This was about the same time that after attending BA and IT conferences for many years, I realized I had things to say that were just as meaningful as the speakers whose sessions I was attending.

So, the dam was busted, and looking back, I am a bit amazed at just how much I wanted to communicate to anyone who might stumble upon this site. Often it was things I wanted to say in my work environment, but couldn't because my boss would not have liked it or it would have just fallen on deaf ears.

So over 20 years of thoughts and experiences just came pouring out, but the well is drying up. Perhaps it may be that what I am doing now as a consultant lets me speak more freely, along with the fact that I really like what I do now.

So, what to do about this? anything? does it matter? Should I start the "Best of David Wright's Business Analysis Blog", essentially re-run old posts that might still be relevant? or just let it fade away, it's purpose having been served? Stay tuned, anything could happen...

Saturday, April 24, 2010

Agile is Fragile

Recent experience at a client showed me that Agile can be successful for a project, but maintaining a level of success across projects and organizations is difficult.The client had one team using Scrum that was delivering sucessfully, but several others that were not.

A manager of one of these other teams told me that their biggest problem was turnover in the Product Owner role; a business person would take on the role, get better and betterat it, then change jobs. The team would have to acquire a new person and start from scratch again.
The other most common problems were scope creep, and excessive change during dev sprints in a project. To me, these are another sign that the Product Owner role was not being performed well. Overall, the discipline needed to make Scrum effective was not being practiced.

The client's response to these problems was to focus on a process for requirements definition, to have stable and clear requirements available for use by a dev team, irrespective of the development process that team may use. Yes, this can be seen as a step backward from an Agile point of view, but what else could the client do?

As a consultant involved in implementing the new requirements process, I have to acknowledge that some readers would say I am biased against Agile/Scrum. What I am biased against is any process that is not working. The client's original use of Scrum is certainly before my time, but it can be safe to assume that it was done for good reasons, one of them likely being that up-front requirements was not working for them.

Over time, the above agile fragilities became apparent and something needed to be done. Rather than try to improve their use of Scrum, the client looked back to its original problems and determined that ifScrum did not solve their requirements problems, what else might? ...leading to me coming to this client to do a Requirements Process Improvement program.

That does leave the one team that is successful with Scrum; how can a Requirements Process fit into what they do? What their team leader and I have worked out together is that functional requirement statements (e.g. The system must have the ability to create an Order) can be matched to User Stories. A good set of Requirements helps deffne a much better and stable Product Backlog to use going forward with Scrum.

In the end, it is about the process, whatever it is, that works for an organization, delivers successful results, is repeatable, and can be learned by others with the same results; anything else causes more problems than it solves.

Thursday, March 25, 2010

A Year on Twitter

I was a late-comer to twitter, one of the horde that joined in 2009. I was in a similar fashion a late-comer to blogs. When blogging started picking up, it was mostly painted as individuals exposing the equivalent of personal diary entries to the whole world. This was not something I had any interest in, but it eventually became apparent that people were blogging about topics of interest, including business and systems and methods and so on. Many of these people were authors of note on topics of direct interest to me. After seeing some of these, and realizing how easy it was, I started this very blog. It may or may not have have reached an audience of any size or import, but I have enjoyed it as an outlet for my thoughts and opinions on Business Analysis.

Then came Twitter, also first painted as people's random thoughts or status, the famous "what I just had for lunch" type of tweets; as before,this did not interest me. Then at the beginning of 2009, I saw some articles (and probably blog posts!) about how this odd Twitter thing might actually be useful, to busineses for example. I also saw on blogs I read the appearance of "follow me on Twitter" announcements. So I joined and started following some of these people. I have a been long-time user of Google Alerts to find things of interest to me, but I found I was getting links to things from Twitter that Google didn't pick up. It is apparent that following someone because of one interest may lead to other unexpected content. This is what I have found Twitter most useful for. People will tweet when they have a new blog post, and then tweet links to other things of interest.

I then discovered all the Twitter apps that tell you how influential you are and such. One thing they usually consider is if you are engaging with other tweeters in conversations, as opposed to just tweeting your own stuff all the time. I would say that of about the 300 people I follow, I do have conversations with about a dozen or so people, mainly other BAs and Systems folks.

The interesting thing is when you have a (probably one time) conversation with a more famous person. They may be tweet somethinng or even ask a question, which spurs me to reply. Most times the replies are not returned, but once in a while they are, which is oddly gratifying; recent folks I have conversed with are comedienne Elayne Boosler, and Peter Travers, movie critic at Rolling Stone. Why does this seem special? I guess it is like getting 15 seconds of fame (a whole 15 minutes of fame being so 20th century).

After a year, I guess what may be most surprising to me is that I have acquired over 500 followers... I mean, I think I have some interesting or funny things to say on occasion, and I do my share of re-tweeting, and I do tweet when I posted on this blog, or over at ITWorld Canada. Yet it does astound me that this has led to me to slowly but surely getting more and more followers. I don't expect I will ever have thousands and thousands, but actually getting into the hundreds was something I wasn't expecting a year ago.

Sure, I have used various apps to analyze who is following me. It is true that many are automated follows, like when I tweeted about the Toronto Blue Jays one day, their twitter account started following me. Then their is always the occasional email about a new follower who turns out to have been suspended for "suspicious activity". But there are some people following me I just don't understand, like all those people who describe themselves as on-line marketing experts.

However, there remains a group of people that number in the hundreds who found me somehow and decided "yeah, I will follow this guy." So, if you fair reader are one of those people, thanks a lot.

Friday, March 12, 2010

Great product for requirements sessions, why is it so hard to find?

The product is whiteboard sheets. They come on a roll, you rip one off and stick it to almost any wall surface, and it clings. You then write on it like a whiteboard, then the ink will dry permanently after a few minutes.

I and my peers use them in requirements discovery sessions. The walls fill up over time, so you can look at anything you have produced. The fact that the ink dries allows you to take them away and use them later for writing up results, and to keep as a record.

These are not a common item. Each new client we work with invariably says they have never seen them before. Our organization gets them from a supplier in Germany, the product packaging says Leitz.

Office Depot shows up as a source when you do a web search, and Amazon too, but actually finding them on their sites is difficult. Right now Amazon says they don't have any and don't know when they will.

If you look for them, don't confuse them with "instant whiteboards"; these are thick sheets that cling to a wall, but are erasable at any time, like a hard whiteboard.

But finding them is worth the effort, and I hope more people using them will make them easier to find.

Thursday, February 25, 2010

Thursday, February 11, 2010

Deep in many discussions.... 10 Signs that you're really "Wagile"

I have not posted here much lately because I have been out there engaging in discussions on business analysis and requirements topics at various sites.

So, here is the link to a good one called "10 Signs that you're really "Wagile""

at http://bit.ly/aIWBmB

(I am not sure when I post this if the link will be usable, but a search on the topic should find it...)

Tuesday, February 02, 2010

Thoughts on Consulting #3 - you get access

Sort of a corollary to #2... When I am engaged to work with a client, all of their people you need involved tend to show up when you need them. Sure, I represent a specific expense that no one wants to be seen as wasting, but it can be more that. The seniority level of the people is high as well, so you know if you need a decision made, the decision maker is in the room, no one has to go off to get that decision from someone else.

I am not saying this is fair or anything, it's just the way it is, so I enjoy it as it comes.

Thursday, January 28, 2010

Thoughts on Consulting #2 - if the Consultant says it, it must be right...

Thirty years in IT, 28 not as a consultant.

If you work in IT at a typical company, you may have had some good ideas, some recommendations, but they were not given their due by management, and you wondered what it would take to make some meaningful change... then an outside consultant comes in, and says basically the same thing, and management pays attention and says "that's great, let's do that!", and you sit there saying "but that's what I said...", or you keep your peace and help to make the change.

That's just the way things go sometimes, I have no great insight to offer you on this. Management laid out large amounts of money to get the consultant to come in, so it is real hard for them to say "we knew that already" or even "that sounds familiar...".

So, have I been part of something like this since I became a consultant? As Mr Bean said in in his movie "...not that I am aware of." I would like to think I would recognize it when I meet those employees, and try to work with them to increase the chances of success. So far, I have met people who agree on what the problem is I have come on to address, and want to help, but have not seen a case where someone already had figured out the solution before and had been ignored. The thing is, that could actually be true but I may never know it. So, I can only do the best job I can and leave everyone as happy as I can make them.

And if you are are an employee with good ideas not getting their due, maybe its time to start consulting!

Wednesday, January 27, 2010

Thoughts on being a consultant...

Since 1979, I was a regular IT employee of the organizations I joined and left up until early 2008. “Consulting” to others in the organization was something I started doing as I gained useful knowledge and experience (while trying to dump anything un-useful on an on-going basis…like Data Flow Diagrams), often within a staff unit that did R&D. I drove the implementation of new methodologies at one company, for example, to the point of defining and delivering training to other employees.

Of course, I also worked with external consultants now and then; most often they were people with experience in a method or tool the company was adopting, to accelerate that adoption. It is a slightly unusual that I never worked with out-sourced resources over those years; the employer I spent the most time with had been an early example of outsourcing their computer operations to a subsidiary, and then selling the excess capacity to other companies. But, the project and development staff stayed within the main IT organization to be ‘with the business’ and that included me. (This does not include the many contractors I knew who came on-site to work; to me they were peers who just had a different employment model.)

Back when outsourcing got going, it was all about the impact on programmers and related tech roles. As a Business Analyst, I was comforted by the initial assertions by various gurus and pundits that Business Analysts could never be out-sourced, because we need to be near the business people to do our jobs.

However, as I gained experience, learned a lot and (hopefully) got better at what I do, it became apparent to me that while Business Analysis could not be outsourced to other continents, it is a discipline that could be done by external resources. They would come in for a focused period of analysis and deliver a set of requirements that could indeed be understood by the business and be of use as input to design and development. I knew this because even as an employee, because more and more I would do analysis for one project, then move on to the next one while the first project moved into development. I would be available to that development team as needed for questions or changes, but this only required a small part of my time. So, it was not necessary for a Business Analyst to stay with a project until its conclusion, there was no more Business Analysis to do to keep them fully engaged. (Now, if a BA also manages the project, or does testing, that’s a different thing, and I avoided both of those tasks most of the time.)

Being somewhat of an optimist, I thought this could be an opportunity rather than a threat, and I started looking at consulting companies as an option for a career change. This ‘looking’ lasted a while, as the majority of consulting companies did not do business analysis; lots of design and coding, but no analysis. I did not want to branch out as an independent consultant, or even a straight contractor, a little too risky.

However, I and the right consulting company found each other in 2008. It took only a few weeks before I joined up.

Hmmm, this has been a lot of lead-up to what my thoughts are now; perhaps they will help someone else who is heading down the same path as I was.

So, thought #1, concerning Travel: the typical week is fly out to a client’s location on Sunday evening, work 5 days, return home Friday evening. I had never minded doing business travel in the past, but it was not frequent, so the concern is what will traveling all the time do to you; will you burn out in some way?

Two years in, the travel is OK. It’s not glamorous; all I see is airports, hotels and client offices. Only one time have I stayed over at the client location to do a little sightseeing; that is not the same as a vacation with family, though, so I don’t expect to do it again soon.

Speaking of family, I have three sons, and the youngest was 20 when I started this. I don’t think this could have worked when they were growing up, it would not have been fair to them or their mother, so the timing has worked out.

Benefits? A lot of hotel points that did cover lodging for our last vacation. Most of my flying is short-haul on the east coast, so the frequent flier points are building slowly. Don’t believe I will reach the million mile level anytime soon…

More thoughts to come in future posts….

Tuesday, December 29, 2009

Memories of IT - 2003-2006 - Business Rules, and blogging

So, I was back in the trenches. Most of the projects were enhancements of existing systems, while building up to a replacement of the main loan application processing system. I did a little project management along with Business Analysis on smaller projects.

One thing I did get some time to research was Business Rules, starting with the Business Rules Manifesto, and reading of proponents like Ron Ross. I worked on getting Business Rules defined explicitly in the company's requirements documents, which went well; I also attended 2 Business Rule Forum conferences, and did a track session at one of them on our use of rules in requirements.

I did the track session because it reached the point where I had been to enough conferences over the years that I thought I had something I could offer, rather than just attend. The conference organizers seemed to agree, as I did a few other Business Analyst World conferences on how I was doing requirements work.

Also, I had been ignoring the rise of blogs, until it became apparent to me at some point that it wasn't just for young people sharing their feelings and thoughts on movies; blogs on business and IT topics were emerging, and again I saw them and thought "I can do this", so I started this blog and did one over on IT Toolbox for a while. Being a Business Analyst can mean writing a lot, and I have found the blog a great outlet for writing that is not specifically for a project. I highly recommend it...

Thursday, December 24, 2009

Memories of IT - 2002 - DHL was fun while it lasted...

DHL Systems was located in the Bay area because it was felt that’s where the skilled systems people were. True enough, although the tech bubble had burst by now. Overall when I joined, DHL was owned by a combination of Deustche Post, Japan Airlines, and family of the original founders; then the Germans bought out JAL or something, and ended up as majority owners. (That’s why DHL vans and planes went from white with red/blue to yellow with black.) At some point someone in Deutschland decided that the Bay area was too expensive, so in December 2001, DHL Systems was ended. The operational part that ran the comm network moved to Arizona, but ATP was mostly dismantled and most of my friends end-dated. I think there was a lot of payback going on for past politics and disagreements. Somehow I, amongst a couple of other people, was offered a job elsewhere. Mine was in the London systems office I had visited. However, the salary was average, and not much was offered to help me and my family move. I also looked into what it would cost to put my sons in ‘american school’ in the UK, and that killed it. Probably for the best, as later on the London office was closed and the jobs moved to Prague. Nothing against Prague, never been there, hear its lovely, but I think it would have been too much of a culture shock.

…but, I am in the USA on an H1B sponsored by DHL. I start looking for a new job, but it’s a slim market, and no company wants to take over sponsoring me, so after some months its clear we have to move back to Canada if I was going to get work… so pack up and move, decide on Kitchener-Waterloo because we had been there before, my wife gets a job first, and then I get back into the workforce as a BA at a captive finance company, like GMAC, but it was for farm and construction equipment. So, out of the ivory tower and back into the trenches.

Afterword: I and my family certainly did like that time we spent in the Bay Area. Three out of 4 seasons was fine, although my son would go on school ski trips to Tahoe. We especially liked heading down to Monterrey and Carmel for weekends, and even just to Half-Moon Bay for the day, and drive up the coast to San Francisco. When I win the lottery, there is a little place on Monterrey Bay I may have to invest in...

Thursday, December 17, 2009

Memories of IT - 2000's - Architecture and the Ivory Tower

As the bringers of the new Architecture, we would get assigned to projects around DHL that say (or are told) that it will use the new way. The PMs would initially be happy, looking at us as another resource for their project. The shine would rub off when we recommended using the new methods to plan the project, especially if the PM had already built a plan. The other team members might get on board or, if the new way was very different from what they had been doing, they might resist. Eventually heated discussions would ensue, long conference calls, at odd hours depending where in the world the project team was.

The usual issue was the iterative aspect of the new architecture, which PMs or higher ups would be uncomfortable with because they wanted a completion date while we were looking to time-box the work and deliver what could be done in that time. Once during an all-hands IT meeting (DHL Systems and DHL USA), one of our key people raised a question about adoption of the architecture, and the senior guy in the room said iteration was never going to work in the real world. A sign of things to come…

The other angle in all this was that our Director actually reported to a VP in DHL central systems in London, U.K. This did mean that we would travel there and back on occasion. Having not been to the UK for decades, it was nice bonus, visited a few spots of interest; dropped over to Brussels once where DHL is actually headquartered, but all I saw was the airport, hotel and the office. The atmosphere in both locations was thoroughly byzantine, highly political, people jostling for position, you never knew when something you said might be turned around and used to bite you…didn’t happen to me but I saw it happen to others. The “Architecture” was often at the center of all this.

The thing was, though, the people I worked with in ATP are among the finest, smartest people I have ever known, so going to work was still great even with all the outside issues.

Quick aside: DHL was in the news a while back, and I know how it started. Back in 2000, DHL had no internal USA business to speak of; DHL was known rightly for being international. It also had a stupid way of measuring how it made money. Each country had its own DHL Corporation. Each one made money on shipments originating in its country, but got nothing for delivering shipments sent to their country, The USA got way more shipments sent to it than were sent out, so it always ‘lost money’, so whoever was running DHL USA looked bad. When I had this explained to me for the first time, I just could not believe it. I have to think that US management complained about this, but it wasn’t going to change.

So instead of more fairly reporting the real profits, DHL decided it would get into the domestic shipping business up against Fedex and UPS. They bought the smaller player Airborne Express, and then you started seeing yellow DHL trucks on the roads.

Well, seems to have not worked as DHL has announced it is getting out of US domestic shipping, going back to their focus on international shipping; hope they fixed their income reporting.

Tuesday, December 15, 2009

Memories of IT - 2001 - B2B and early days of Rosettanet

After the Shipment Tracking project was over, I spent the next year working on several things, overlapping and simultaneously.

One cool thing was Rosettanet, the standards-based B2B architecture being developed, mainly driven first by IT and electronics companies. The idea was to define a set of supply-chain messages that companies could use with other companies who used the architecture. So, once you started using the message with one other company, you could then use them to communicate with other Rosettanet –using companies with little to no added effort.

One of the key set of messages had to do with making shipments of orders through a delivery company like DHL, including getting shipment status, and notice of delivery. So, Frank and I signed on as the representatives for DHL, and joined a working that included reps from Federal Express, UPS and a few smaller players.

The main deliverable consisted of XML message formats, with all the data defined that would need to pass from sender to receiver. ( A lot of the other messages sets were about automatically checking a suppliers inventory for desired product, then making the product order, and the supplier confirming the order, shipping --- which was our part ---, followed by invoicing. When we signed up, there were upwards of 100 individual messages defined, and about half had been created, and the first companies were starting to use them.)

Our messages were drafted during a couple days of meetings with all the reps, at a Fedex Ground location outside Pittsburgh. We took along an actual business person from DHL USA (also located near San Francisco) for Shipment knowledge. DHL’s acknowledged expertise at that time was in international shipments, so a lot of the message content about customs clearance came straight from us.

After that, we met weekly by conference call to iron out the final versions, after which they went through a formal Rosettanet review and approval process, after which they were published. The interesting thing about Rosettanet was the published services were free for any company to use, to spread their use, obviously. The core companies like IBM and others provided the most, and it cost to join in order to participate in development of the messages, worth the money if you made sure the messages were going to work for you.

I also went to one Rosettnet User Conference, in Chicago. A lot of it was about how to implement and start using Rosettanet at a company, with all day sessions or various tracks of one hour sessions, like most conferences. The basic structure was to have software sit in front of a company’s existing order and inventory systems, extract data as needed from them, use it to create the standard message and send them off. The same software would do the reverse as well, accepts messages, parse out the data and feed the existing systems. As you might expect, a number of vendors in the B2B space had already built and were hawking software packages to do just that, including services to automate the extracts from and feeds to existing systems. So, all the vendors were at the conference, of course. That always meant some free food and drinks and entertainment, which always helps make any conference more enjoyable.

In the end, the interesting thing was that some months later, Cisco and DHL entered into a logistics agreement, where DHL would warehouse Cisco parts around the world and deliver the parts when directed by Cisco…and their requirement was that these shipments would be triggered automatically using Rosettanet messages.

Anyway, its still out there, see www.rosettanet.org , check it out if you are serious about B2B...

Monday, December 14, 2009

Memories of IT - 2001 - Arguments over interfaces...solved.

So, I deliver Use Cases and design/development begins. My group designs a service and interface following the Architecture. The KL systems people want a specific date/time-stamp form an existing system in the interface; our lead designer says no, that any other system using the interface should not know where the data provided came from, so that the service can be changed in the future without disrupting any systems using the service…. Things got quite heated. In a moment of prescience, upon hearing of this argument, I stepped in and said that this was a requirement issue, not a design issue. The date/time-stamp was actually the time a Shipment was first recorded in a DHL System. I added that date to our data model, then added it to the Use Cases, and the argument ended, at least publicly… there always seem to be some level of discord between DHL Systems ATP and Systems areas in DHL. We actually printed a poster of a white tower and put it on the wall heading into our office.

So, design and development went ahead for the pilot, was accepted, and then went live. For some period of time, at least, when you searched for your Shipment on DHL.com, you used a service based on my Use Cases.

Friday, December 11, 2009

Memories of IT - 2001 - Architectures, RUP, Iterative, BEA and other stuff in the life of Architecture Technology Pathfinding (ATP)

This pilot was the first real test of the work of the group I had joined, known as Architecture Technology Pathfinding(ATP). The architecture in the title was actually multiple architectures, and multiple uses of the word.

The main Architecture was about application structure, and it was a detailed description of an N-Tier environment, with interfaces invoking Business Services which would then invoke Data Services and such. The implementation of it was based around the BEA web server product, and DHL Systems had in fact been an early customer and supporter.

But how do you define the applications? We were strong adherents to the Zachman Architecture Framework for starting with concepts, then models, then implementations of models down to code. Frank and I were focused on the Data Column of Zachman, with overlap into the Process column when defining the CRUD functions on data. In the application architecture these CRUD functions were the lowest level services that supported everything else. The overall approach across the architecture was service-based, with a service being defined and made available through an exposed interface, so that everything behind the interface was unaffected by what used it (and vice-versa) as long as it could provide what the interface said it needed. Very OO, of course, and a hint of SOA (which had not appeared as a term yet).

The other main use of ‘architecture’ was that as used in RUP, summarized as development of an application by first creating an overall architecture for the app, and then building it up in the multiple iteration approach of RUP (not Agile, which wasn’t a well-known term yet either). Selling RUP and its iterative approach was a big desire of the key people in ATP, as a means of moving away from a big-bang approach to development that had failed in the past.

The thing was, it had to be sold to IT execs in DHL proper, and there was one of those for almost every country in the world (although we focused on the USA and Europe as the likely place that success of RUP would then spread from.) Many an IT exec had blown off iterative, mainly because it was believed you could not define a specific end date for iterative development, and so you could not estimate it. The fact that past projects with planned target dates and estimates had usually missed both by wide margins didn’t count. The execs wanted something that made big-bang work, not something different they could not understand or felt they could control. However, the whole combined Architecture approach espoused by ATP had taken some time to develop, and had involved some other DHL areas, so it could not just be ignored. That is why the pilot for Shipment Tracking was devised, to illustrate the use of the Architecture and Methods. The complications came when the design started and some non-believers tried to undercut the whole thing….more next time.

Tuesday, December 08, 2009

Memories of IT - 2000 - ERDs, OO, UML, Use Cases and all that

The first thing I did at DHL Systems was learn and use Rational Rose, and learn more about the RUP methodology. The aim was to figure out how to marry classic ERD data models with the Object-Oriented development modeling, especially the Class Diagram. This actually involved a lot of discussion with the OO experts in our group. I even went on another UML course (my first visit to Denver), but I still wasn’t grokking it. I also read one of those “UML for Business Modeling” books, but it didn’t help.

So, I translated some of the existing ERD models into Class Diagrams, and then tried my hand at some Activity Diagrams to model how some Classes would be created in a business transaction. Frank (my boss and fellow Analyst) and I showed these to our chief OO designer/developer, and his reaction was negative. His opinion was that UML is a software design language, not be used for analysis or requirements. He stated that what OO developers needed from Business Analysts was a “concept diagram” ( a generalized Class diagram that just showed what the main things of interest are) and Conceptual Use Cases. Frank was concerned that my hard work had gone for naught, but we moved on. Our Architecture group was going to participate in a company wide pilot to use UML, OO, RUP and a new architectural approach to create new services for tracking shipments through the DHL website. My job was to first write the Conceptual Use Cases, which would be used to create a design and concrete use cases, to be vetted by DHL IT in Brussels and built by another DHL Systems group in Kuala Lumpur.

There were no business people involved directly, the KL group was positioned as our ‘customers’. As such, any requirements they had were technical and cause for much wrangling between them and the OO folks in my group (more about that later). So, I went back to the big data models built in years past because, as you might expect, they were all about Shipments and all the supporting things you needed to pick-up, send, and deliver a Shipment. I created a set of Query Use Cases based on the data models that would accept enough data to identify a shipment (or at least a short list of candidates) and return whatever data you needed about the contents of the shipment, where it was and so on. I actually thought they were pretty lame, as my IEF days had installed in me the belief that queries and reports didn’t need requirements the way Create, Update and Delete transactions did; but, they were accepted pretty well, mainly because previous attempts had produced requirements that were either too vague, or too technical… I had found the middle ground. Then the real fun began as we moved into design…

Monday, December 07, 2009

Memories of IT - 2000 - A Canadian in California

For any Americans reading this post, you should know... there are Canadians amongst you. And I don't just mean Jim Carrey or Mike Myers or Neil Young or (so I am told) one of the guys on "Glee". For a while, there was also me, my wife and my two younger sons.

A true story... my wife and I were shopping at a little outdoor mall in Castro Valley CA, and there were booths set up for the day selling crafts and such. One booth, however, was for voter registration. A nice lady in that booth asked my wife as she passed if she had registered, and my wife said she couldn't, to which the lady replied with "why not?". "I'm not not a citizen" my wife told her. The Lady asked "where are you from?", and my wife replied "Canada". The nice lady then exclaimed, "Really? You look just like us!" But then she took a beat and then said "well, that was a pretty stupid thing to say...". So, we never complain about Americans or the USA, we just offer useful information when we can.

It was a big move again, of course, but my wife had always felt she should have been born in California, and we would have been there long ago if not for the world's longest undefended border. For the record, DHL sponsored me on a TN Visa and then an H1B. I know H1Bs are a touchy topic for some, but DHL was able to show that they had been looking to fill the job for a while (and they had), and had been unsuccessful until they found me.I believe that's what visas should be used for, and that it helps the USA in that case. If visas can be abused in some ways, though, that's not good.

We settled in the East Bay, first in Castro Valley then later in San Ramon. That did mean I had to drive over the San Mateo bridge every day, and it had not been widened yet. However, commuting has been something I have always done, and in a lot less interesting places than San Francisco Bay.

It was a great place to live. If you live there, you already know that. If you have never lived there, don't worry about the earthquakes or the state going bankrupt or whatever, mover there if you ever have the chance.

On other thing before I get back to the IT stuff; we actually got to California by driving to Chicago, and then taking the California Zephyr train out to Oakland. We planned it as a mini-vacation (that also meant that my wife did not have to fly..), and it was a great trip, across the plains to Denver, then up and down both the Rockies and Sierra mountains. I keep hearing they might stop running the Zephyr, but if they haven't, I highly recommend it.

About Me

Ontario, Canada
I have been an IT Business Analyst for 25 years, so I must have learned something. Also been on a lot of projects, which I have distilled into the book "Cascade": follow the link to the right to see more.