Recent Posts

Saturday, November 23, 2013

Product Owner in Scrum = Project Manager!


I became a CSM last week: Certified ScrumMaster after taking a thoroughly enjoyable course over the weekend. I read my first book on Agile and scrum back in 2007 and have taken a number of courses since then. I also got a PMP along the way. However, this was simply the best course ever! Check out www.beardedeagle.com for their excellent training.

One of the things the trainer said that got me immediately stirred up was that in many cases the closest analogy for the Product Owner in scrum is the project manager in traditional style of project management. (There is no role of project manager in scrum). This got me really thinking as I always believed that the product owner would be someone from the business side (bringing this into the Wall Street Banking IT arena). I could not for the life of me envision a senior manager in Product Control, Front Office, Operations, etc taking Scrum training and playing by the rules of Scrum (Perhaps I shouldn't be so pessimistic about it, but if you work in Investment Banking IT, you'll probably see my point). So I had determined that Scrum wouldn't really work well in my environment and that I would have to continue to act as traditional project manager and use a modified scrum-like methodology.

But lo and behold, the Product Owner = Project Manager solved the problem for me! And it makes perfect sense. The traditional project manager is the one that has to manage the stakeholders, assess the priorities, etc. That makes for a perfect product owner! And now under this light, it all seems work-able now. Of course, in some instances I'll have to play dual role of Product Owner & Scrum Master (which is dangerous as it's a bit too powerful) but I have some room now to empower my colleagues in running our projects. I can give the role of Scrum Master to one of my Analysts and have him work with the Dev team to accomplish our goals while I can step back and concentrate on other things.

Tools, tools and more tools

I've been having some thoughts about tools in the project management biz. I actually embarked on writing a specification for a new project management tool: one that would be the 'right' way to manage projects. I was even trying it out on a live project I am doing. The first few 'rules' I was using to manage the project (rules that would eventually become requirements in the software implementation of the tool) seemed to work well.
I became so enamored with the idea that I called an MBA friend of mine and told him of my idea and how this tool would revolutionize project management and that we should do a startup!

Shortly afterwards, I happened to look up project management tools online and discovered that they were a dime a dozen! There's just so many tools out there it's unbelievable. It would be extremely difficult to differentiate my tool from one of the many that already exist. But this wasn't a dealbreaker. Perhaps my tool would just be so incredible that it would out-shine the competition.

But as the project moved forward, I had to keep developing more intricate rules to take care of each case. It went well at first but after a while, it became cumbersome. In fact it became downright unwieldy. It dawned on me at some point that what I was developing when I was creating these rules was actually a philosophy or style of project management, not a tool. The tool didn't matter; in fact, I could use any tool (even MS Project as it's so darn customizable) and adapt it to my needs.

The over-reliance of tools to 'get the job done' is a joke. A tool can't get any job done. It's just a tool. There needs to be an intelligence behind the tool and how it's used. Namely, that's you or me: a sentient human being who is actually using the tool for a purpose.

That's one of the reasons many agile methodologies don't prescribe tools; Whiteboards are the favored means of communication. One level from that is Excel, which happens to be my favorite tool (also Word & Outlook). In the Project Management biz, communication is king and these tools all do the job quite handily.

In fact, I constantly create & abandon tools all the time! For example, I created a spreadsheet to track my own projects back in 2012. When new management came in 2013, and the style of reporting was changed, I realized my internal spreadsheet I was using wasn't fit for purpose. I wholesale abandoned it and created another one that would enable me to report on the relevant state of my projects. The lesson is: Don't get married to your tools and force-fit them. The need to *communicate* first and foremost is paramount.

I won over a difficult stakeholder across the pond by abandoning tools. When a fresh year started, he wanted me to represent my projects in a spreadsheet he liked (even though the group as a whole mandated another way, which led me to maintain two spreadsheets representing similar information). It got cumbersome and eventually I wasn't able to complete these in a timely manner. I then resorted to straight updates on e-mail: these were very focused and to the point and *relevant*. I figured I needed to get him the information one way or another and b/c of bandwidth limitations, plain bullet items in e-mail was fastest. He thanked me for the great updates and I knew I had a winner. I completely stopped filling out a spreadsheet for him (which I doubt he looked at anyway) and continued with bi-weekly updates over email. He even spoke about what a great job I was doing to my own managers!

A key point here is: What was important one week may not be as important the next week. Blindly filling in spreadsheet templates with boring, non-relevant details (just to get it over with) every week will make your stakeholders deaf, dumb and blind to your needs. [This harks back to my previous point about a sentient human being actually using the tool for a purpose]. You need to focus attention on what is important in that reporting time period. A rule of thumb: if you don't know what is important, then if it's important to YOU, that makes it important. And then of course there's listening: people will tell you what is important. Note it down, capture it in the actions, put someone down as owner and track it. And of course deliver on your actions.

Another tool that I've found quite useful is the depiction of scheduling of projects. It has been previously difficult to look ahead to see when projects will end and when others can start. Typically, people might use a Gantt chart for this (and I did) but I stumbled on quite a nice way to represent on-going projects that are being run in parallel across my group and show this to the exact number of weeks. It looks quite nice and I can share it with stakeholders to easily grasp where we are. [I roll off past weeks simply by deleting rows on top]. The flexibility of Excel makes it easy to play around with the best ways to deliver information (not just data!) and give a picture. If you rely on one prescribed tool (like say, a big portfolio management tool your company may have purchased) and only use that, you'll put your stakeholders to sleep!

Sunday, December 30, 2012

Complex Systems

I'm reading Michael Crichton's last novel called Micro and I love the introduction. I'd like to post some of it here:

Perhaps the single most important lesson to be learned by direct experience is that the natural world, with all its elements and interconnections, represents a complex system and therefore we cannot understand it and we cannot predict its behavior. It is delusional to behave as if we can, as it would be delusional to behave as if we could predict the stock market, another complex system. If someone claims to predict what a stock will do in the coming days, we know that person is either a crook or a charlatan. If an environmentalist makes similar claims about the environment, or an ecosystem, we have not yet learned to see him as a false prophet or a fool.


Human beings interact with complex systems very successfully. We do it all the time. But we do it by managing them, not by claiming to understand them. Managers interact with the system: they do something, watch for the response, and then do something else in an effort to get the result they want. There is an endless iterative interaction that acknowledges we don't know for sure what the system will do--we have to wait and see. We may have a hunch we know what will happen. We may be right much of the time. But we are never certain. Interacting with the natural world, we are denied certainty. And always will be.

Saturday, December 15, 2012

Legacy Software

Working at an investment bank is challenging. There's constant pressure to deliver, not screw up, reduce operational risk (which is the new buzzword that represents the same concepts that we've always been wanting less of), reduce TCO (another buzzword), etc. and of course to produce new software that helps the business do deals or reduce their manual workload.

Here are a few of the challenges:

  • Maintaining Legacy Software and/or trying to Decomm Legacy software
  • Satisfying audit & internal regulatory requirements that have little impact
  • Hiring button pushers rather than smart people who can actually debug issues


I will address the first two points in this post & leave the last for another day.

We have tons of old, legacy software whose original developers have moved on. I'm talking about software that just runs and that is mostly a black box. We feed them (i.e., keep the lights on, reboot the servers on a routine basis, monitor them) so they keep running but occasionally they fail. That means I need to pull a developer who is working on a new project to resuscitate the old software. This is painful because the developer is not very familiar with this software and it takes time to figure things out. Users may be impacted and thus screaming and escalating to senior managers, so this adds to the pressure. Note that most if not all of this software was not constructed with the latest agile practices like TDD so there are no unit or integration tests to speak of, and the documents (if they even exist) are yellow & crusty.

Of course, making changes to this software is risky, because the developer could make a change that impacts another part of the software and break something else. And without a good suite of tests, how will you ever know? Given the time pressure to get this working again in production, we can't do adequate testing. So we release into production and hope for the best. And we document what we learned in a wiki or FAQ, so we can at least build our knowledge base (hopefully). Then we all context-switch back to our new software development.

This is an oft-repeated pattern in my group and I would not be surprised if this is universal. (or I would be surprised if this was NOT universal!) Additionally, morale slips because we lose time fixing old software, we disappoint both the users of the legacy software and the new users who are expecting their new software on time, etc. Developers become disappointed because they can't seem to get traction on the new software as well.

So as a general rule of thumb, we should try to minimize modifications to the legacy code-base. If you need to do it, then do it. But let's look at one 'need' in more detail; this brings me to the 2nd bullet point above: Satisfying audit & internal regulatory requirements that have little impact

I'm currently on a project to satisfy an internal audit point (not a government regulatory item) that requires me to modify a legacy piece of software (which by the way we are trying to decommission). This change, I'm finding is incredibly risky. One, it touches at least a dozen files across the board and the software is responsible for getting all kinds of data intra-day and End of day. Two, the developer is in Singapore whereas the rest of the team is in NY and so we can't even talk real-time about the changes. Three, there are other, new components that the legacy software will need to make use of and so may require a 3rd party to be available on stand-by. Taken all together, it would have been wiser to get an exemption for this.

Unfortunately, this comes back to the way I presented the problem to my manager. I hadn't thought through all the ramifications of the change. I only knew I didn't think it was in our best interests. But I went to my manager and all I said was "Look, we have this audit point but we want to decomm this software so do we really want to do this?" and he said, "Yes, we need to". So off, I marched.

My point is that I didn't have a strong enough view on the situation. At that moment in time, I only had a 'leaning' but not a clear enough picture of what the whole thing would entail. If I did, I could have possibly persuaded him that this wasn't in our best interests to do.

So what's the lesson here? When modifying legacy software, (1) get the scope of the change (how long it will take, impact assessment, how many files/modifications need to be made, etc), (2) assess overall risk, (3) if too risky, push back and make the case as persuasively as possible.

Audit points, regulatory risk, operational risk are big buzzwords that make people jump and immediately act but wait! not so fast...  (1) there could be abuse of those terms and they can be inappropriately applied, especially if there are other agendas involved like politics & (2) they should not all be treated equally. Some audit points just aren't as important as others and we need to really understand what's important and what's not. It's similar to taking something in the spirit of the law and not just going by verbiage. So if the risk to satisfy this point is riskier than not satisfying it, well, that should be taken into account. We shouldn't just blindly do it because that's what the audit point says. Let's have a conversation about it and negotiate.

So in writing this point and thinking further about this, what I will do is: re-examine the exact scope of the change, and if warranted, re-have the same conversation with my manager asking for an exemption. I'll fill him in on the exact risks and have him sign off on email if he still wants to proceed. That way, if there are issues, he can't say he didn't know about them. And I'll have done my due diligence.

Thursday, July 14, 2011

The Start-Up of You

The title is a reference to Thomas Friedman's Op-Ed column in the NYTimes, dated 12-July-2011. Click here for the article: http://www.nytimes.com/2011/07/13/opinion/13friedman.html?_r=1&scp=2&sq=thomas%20friedman&st=cse

 It caught my eye because it sounded similar to "The Brand of You" by Management Consulting guru, Tom Peters.

In any case Friedman is dead-on. So dead-on that I came out of semi-retirement to even write this post! :)

I won't rehash what he writes but I will raise examples in my own workplace that illustrates what he states.

E.g., We've been having cuts at the investment bank where I work, and it's just one in a parade of many. People have to constantly look for new jobs or are worried that they'll lose their existing one. Constant re-invention is a must. Workers must always look for ways to add value (which is one of the things I stated in my earlier posts). You can't be idle in this day & age. Look around for what else needs to be done. Kaizen! Continuous Improvement! People who are bored at work simply aren't looking. If you claim to be bored, look at it is a tremendous opportunity to use your imagination to poke into something/get involved and make suggestions.

Another eg. I've seen is what happens after the layoff. In my own group, we were at a height of 100+ people at one point. Now we're down to under 50. People got let go & others left on their own. But the company never replenished. We still have to maintain our ongoing operations however. So what does that mean? Many people are filling multiple roles and are busier than ever. We've gotten pretty damn lean and efficient. And furthermore, we're not just going to hire anyone. We did have a few openings for contractors. But it took several months to fill them. Why? Why when there's a glut of IT people out there did it take us so long? Because as Tom Friedman put it, "we are increasingly picky". We want "people who not only have the critical thinking skills to do the value-adding jobs that technology can’t, but also people who can invent, adapt and reinvent their jobs every day, in a market that changes faster than ever."


I also look at how I can make the job more efficient. I think in terms of the franchise model. The key to franchise success is how to replicate your business easily and cheaply. McDonalds hires burger flippers. These burger flippers don't stick around all that long, I'd gather. It's an easy skill to train them in, and if they leave, you train the next one. And so on. They have it down to a science. Well, even in IT, a similar thing can happen. I am working with a system that has traditionally caused a lot of noise. It takes someone of high intelligence to figure out what's going on. Since I've come into the group, I've whittled the noise down slowly but surely. I've gotten rid of the false positives. Now the system is beginning to hum. Any errors that actually do pop up are being documented in a HOW-TO guide. When I am done, suddenly we don't need that person of high intelligence anymore. That person can be re-assigned to work on more interesting tasks. And in that person's place? You got it: a burger flipper. Someone of mid-level intelligence who can follow instructions and handle basic tasks and attend to those errors. Not the greatest job, but hey, it's a foot in the door and people can move on once they get bored. Even for this job, though, I wouldn't just hire anyone. I'd want someone who could master the task easily and then say "What else? What else can I do?" 

Saturday, March 26, 2011

Pure PMs vs. BAs

I've been noticing lately that pure Project Managers on Wall Street are losing popularity. Of course I have only a limited perspective but the sentiment I'm getting is that pure PMs aren't adding as much value. In fact I see a trend towards hiring more BAs with PM experience, or Senior Dev Leads/Project Managers. So some specialty role + PM experience is a more popular choice with employers.

A pure PM might fit into a PMO role better, but an actual project manager doing projects is better off diving into the details.

Wednesday, January 12, 2011

Collaborating & Engagement with Colleagues

I am on a new project with new colleagues. I had been working with the same personalities for so long now that I forgot what it was like to go through the Forming/Storming/Norming phases again!

It's interesting to see how some people prefer to work alone even when the work requires collaboration. I actually think this is an easy trap to fall into. In this era of the knowledge worker, each worker has such specialized skills and knowledge of his/her area that it requires serious effort for someone else to intervene and pick up a new task or role. It is just easier to wait for the person who specializes in that area to pick up the task. This can result in long wait times for things to get done, but that's a topic for another post.

A side effect of this type of specialization however is that people start to work in their own silos. Because one person can do so much in just their one area, a type of rigidity sets in and people only do what they know. If something is outside their bailiwick, they will assume someone else will pick it up; or they'll punt the task over to someone else and wash their hands of it and rush back to their own specialty business. In fact, that other person may be new and has no clue and is waiting for direction from you!

It's becoming harder to recognize that picking up the phone and talking to your colleague might be a good idea. A few face to face meetings and phone calls are the equivalent of 1000 emails (or IM chats) just as a picture is worth a thousand words. I moved the project many fold in 1 day than it had moved in several months.

There is nothing like the feeling of several of your colleagues hunched over a screen trying to work out a problem together. Research shows group problem solving is way more productive and efficient than solo solving. In fact, in a project management course I took a few months back I was witness to this exact phenomenon. We were told to do an exercise by ourselves. After that, we had to do the exercise as a group. This provided for a lot of debate because each person had their own views on what the correct answer was. We had to come up with a consensus and convince each other. Eventually we arrived at a solution. Then we graded our own individual solutions and then the group solution. What do you think the result was? The group solution score was higher than any of the individual solutions! I was astounded.

I can see myself get lethargic at times as well and just want to stay at my desk and manage from there. I have gotten facile however at recognizing when this happens and am able to override it and keep myself moving. I will make that extra phone call to push a dev ticket ahead or will sit with my colleague at his cubicle for an hour discussing an issue and how to address it. These are the little things that when added up move projects and eventually implement a company's strategy.

Thursday, December 30, 2010

PMP !

It's official. I have done it. I am now a PMI-certified Project Management Professional (PMP)!

I took the exam yesterday (29-Dec) and spent a little over 3 hours on it. When I hit the submit button to finish the exam, I was fairly confident that I would pass. In fact, during my entire preparation I had full confidence that passing this exam was inevitable.

The reason for my confidence is that I had fully project-planned my entire PMP experience! I made the goal of attaining the PMP back about May 2010. I then realized my company was offering a prep course for the PMP exam in November. I signed up for the course and targeted December as to when I would take the exam. So my milestones were set!

I signed up to become a member of PMI & my local chapter in mid-June. I then spent Saturdays going into the office over the summer to count up my hours. To aid in this, I scoured the web for a spreadsheet that would enable me to easily count my hours. I found one and several Saturdays in June, July & August were spent tallying these hours going back 3-4 years.

The next step was to get these hours into the PMI website. I'll admit there was some slight procrastination here :) Actually, I already had a lot of slack for this task. The hard part was counting the hours. All that was left was data entry. So one Friday night, I stayed late at work and entered all the hours.

The next step came in November when I took the PMP course. I missed a lot of it because of work issues that came up, but the materials in the class were invaluable. It was taught by ESI and I got all their study aids as well as the 9-disc CD set for each knowledge area. I then decided to set a date for the exam in late December and made that my target. For over a month, I studied: Listened to the CDs, read the PMBOK, did practice questions, downloaded PMP apps for the iphone that I could play with on the subway; After this initial stage, I deep-dived (dove?) into each knowledge area. I bought the Head-First PMP book and did the entire book. I then re-took the practice questions from Stage 1, elevating all my previous scores to about 90% and higher. I was already sure that I would pass the exam at this stage. I then took a full comprehensive test exam that ESI provided me with and then the online Head-First PMP exam. On both I scored 85 % and higher.

I then just practiced writing down a few formulas and making sure I knew them cold. And that was it!

It's really amazing how planning this whole endeavor worked so well. I executed flawlessly and mission accomplished!

So tips for passing the PMP: I don't have much to add that would improve upon what many others out there already advocate. Just that you should know your own style of studying. I am an accomplished test taker and so I already knew what would be the most effective for me. Do the same for yourself and you should be fine. A little discipline goes a long way!

Friday, December 3, 2010

Cross-Managing

One of the most valuable things I've heard on my project management journey is "If you want to be a project manager, you have to first learn to be managed". I was puzzled by this but it was so zen-sounding, I just knew there was some truth in it. That was several years ago and since then I've seen the truth of that statement everywhere. Many people want so badly to be "managers" and feel that by getting their PMPs & learning to delegate, they will have made it in the project management profession. They don't want to put in the time to learn the tasks they need to do their current job really well. They do the tasks to get them over with so they can get onto the next "bigger" thing. In other words, they become close to "un-manageable" in the job they are already in. Why would a senior person trust such a person with an important project to do if they are unable to perform their current job really well?

That's the way to grow in this business of business: Perform excellent work *now* in whichever role or function you're in. Gradually you begin to build yourself up and show yourself capable. Then people everywhere come to see you as reliable and you will increasingly get more work (which is a good thing!) Before you know it, you will become a manager!

However, it doesn't stop there. The entire business of management is not only top down, but also  bottom-up (as I've blogged about here: Managing Up). Now, I have yet another addition: Managing Across! What does this mean? It means managing people on initiatives/requests that you have no direct relationship with. So for e.g., since I am in IT, I have no direct relationship with someone in Expense Management or Credit. However they may ask me for something or I might need something from them. There is no on-going project that we're all involved in. Usually it's something like a one-off request. And yes, this can easily be seen as a distraction from current project work. And people may not respond with alacrity. Or they may not respond at all! In fact in some circumstances, you may need to escalate to get your request fulfilled. So in this case, there's nothing really in the PMBOK guide that addresses such circumstances (or actually there may be; I just haven't looked closely enough). However, some of the techniques that are used for managing people in general can be valuable here as well.

Here are a few:

  • Ask for a favor
  • Make the request as simple as possible
  • Make a phone-call OR send an email and then follow up with a phone call: a personal touch is much more effective than an email to someone you don't know
  • Thank them!
  • When someone requests something of you in a similar fashion, respond with alacrity and be helpful
Managing Across is yet another opportunity to learn to be managed. We're managed by our bosses, but we can also be managed by colleagues in other parts of the organizations to provide them help/information. It's a constant exercise and requires discipline. There is no point at which you will NOT be managed.

In fact, if I can get philosophical, Life is the greatest manager of them all. Life constantly introduces new stresses and pressures; it changes directions on all of us & sometimes does so whimsically.  We all are managed by life in one way or another. So how do you deal with it?

The answer: Being managed at work is a microcosm of life in general and serves as excellent practice! So if you find yourself getting frustrated by requests from others or "distracted" from your project, treat that as an opportunity to be managed. How you respond in such circumstances will be an indicator of how you respond to your life in general.

Wednesday, November 24, 2010

Too Much Code!

We are releasing some new software soon and I discovered that the developer put in some extra functionality. This functionality was not requested; He just thought that it would be valuable in case there was ever an issue and we needed to trace things back.

He had mentioned it to me some time ago but I didn't understand the full gist of it and I let it go. However, just the other day we were testing our software and a bug related to this feature came up. So he's putting in a fix for this. The bug was the result of doing some a-typical behavior but nonetheless it's something that should be resolved once detected.

However my concern is with why is that feature there in the first place? It was never requested. Developers need to understand that adding new features comes at a price. I not only serve as PM, but also BA & QA on this project. I am also the PM on multiple other projects and my time is limited. Adding any new feature => (means) adding more code => creating additional pathways => testing more code. This can grow exponentially. Simply put, the price you pay is additional testing time but also increased probability of bugs.

Users who request features with abandon and software teams who accomodate them get into lots of problems. Feature requests need to really be evaluated for the payoff they'll deliver. The thing with software is that it is invisible; you can't touch it or taste it or see it. So it's easy to overlook the amount of time, effort & money that goes into producing it. This message needs to be constantly sent to users in the form of pushing back or pricing each feature. Say No if you don't believe the feature will provide enough value vs. what will go into producing it. Or give a price tag: if they want something the user will have to pay for it somehow: either monetarily (cash, budget xfer, etc) or time-wise (this will delay the next feature x amount of days/months, etc)

You constantly need to remind users of the cost of producing quality software (and that includes QA time). It's easy to forget. Again, I need to point to the guys at 37signals.com; They turn down LOTS of feature requests in their quest to keep their software bug free and clutter free.

Friday, November 12, 2010

Project Management Tip #1

I was going to write a top 10 list but the first one alone is enough for a post! So here is Tip #1:

Email Communication
When I see email sent from colleagues to several people in the To line and the cc line, I am still amazed to see that people don't address things to specific people.
An e.g. of a bad communication:
"Yes, I agree. IT needs to check whether we have connectivity via Radianz BT to the exchange. Once we know that, Operations can go ahead and request the appropriate credentials to get us going"

Seems like a normal piece of communication. But it's not very effective. Why?
IT & Operations are huge! If the above email was sent to one person, that person know s/he knows to do something, but if you have a number of people on the list, then (and this is the most pervasive thinking around), everyone assumes someone else is doing it! It baffles me to this day why people who send such email also sit around and complain that nothing gets done...

Much more effective would be:
"Yes, I agree. Steve, can you check whether we have connectivity via Radianz BT to the exchange. Once you confirm that, let Rick in Operations know so he can request the appropriate credentials to get us going."

PUT ACTUAL NAMES against tasks! This actually shows that the delegator knows his/her co-workers and their responsibilities which is nice (don't you feel good if a manager knows that you're responsible or good at something?)  I even use this tactic if I'm not sure who the right person is. I may just take an educated guess. One thing I know for certain: If I address it to the wrong person, that person will reply back *right-away* and say "I don't do that. Jason handles that" and now I know that Jason should be handling it!

Monday, November 1, 2010

The Dangers of Bad Project Management

Bad Project Management gives all Project Managers a bad name!
Done badly, it actually can scar one for life and diminish management's effectiveness in running an organization.

Too many people have the notion that all project management is is: issuing tasks for people to do, and hounding people for status. A lot of people think project managers add no value. And I would have to agree: if this is all they are doing, then they are probably not contributing much at all and detract from the project. This kind of project management gives us all a bad image. However, it just doesn't stop there. The damage becomes pervasive: People who have *never even been managed* on a project learn from their peers and others in the organization the attitude of "Oh no, we gotta listen to this guy" and watch as their colleagues roll their eyes at the PM who doesn't know what s/he is talking about.

PMs are caught in the middle between senior management and the people doing the work. From a senior management point of view, if I plan a strategy and want to execute, I look to my PMs to implement that strategy. They are my levers to push and pull on to get the organization to move in a certain direction. So as a senior manager, I need to have trust in my PMs. If I have a negative view of Project Managers, I'll never place much faith in them and empower them to get the job done. I might second-guess, or micro-manage them; basically doing their job for them. That would put me at risk of losing my own job.

I'm sure there are senior managers who have these attitudes but those who are effective senior managers believe in the virtues of effective project management and have seen that it truly is the way to get things done.

My concern is more with the people doing the work. We should be more worried about the effect of project management on the line workers and those in the functional areas. If they're disillusioned by project management and its practices, they won't execute and the whole practice becomes a failure.  Many of them have been burned by the application of bad principles, or principles inexpertly or inappropriately applied. (e.g., long, wasteful meetings with too many people or the opposite: badly run scrum meetings) or bad PMs (who stay above the fray and don't get involved and miss key details, report wrong facts, etc). This has a cascade effect as I mentioned above: they don't feel utilized or listened to;  they feel ineffectual or that the project isn't going anywhere or headed in the wrong direction or it may simply stall because decisions aren't being made => other colleagues become infected. These personnel may start to look for work elsewhere. The problem with this is they carry the same negative views of project managers with them where ever they go & history can easily repeat itself.

So what's the remedy? Simple! (but more difficult in practice) Hire good PMs; PMs who aren't afraid to get into the guts of the project; to sit down with a BA and have them make that call to the customer to clarify a requirement (I did this just the other day because the BA sounded unsure of what the customer was asking for) or to sit with a developer and get into the details of why something is not working. You don't have to have a particular skillset to do this. You don't have to solve the problem. But just listening alone shows others that you are deeply involved and care what's going on: that you're all one team. And this is the most important thing in project management: Operating as a team.

Project Managers are leaders by definition. Thus they need to also model the behaviors that go into successful execution of tasks. If a BA is uncertain of something, call up the customer. If a developer doesn't know how to proceed, suggest things to google, etc.

Wednesday, October 27, 2010

Don't bring me problems; bring me solutions!

or "Don't come to me with a problem if you don't have a solution"

These sayings are some things I've heard along the course of my career. 

Now, when I first heard it, I thought it was dumb. I mean why the heck else would I approach my boss? If I didn't have a clue how to fix a problem, then why *shouldn't* I go to my boss?

But just as in observing a jewel & its many facets, there are many ways to interpret the above remarks... 
A few experiences have shifted my attitude from the one I previously held.

1. I encountered an issue at work and realized it needed to be addressed with a higher priority than some projects that I was managing currently. I called my manager and told him about this new problem. He seemed to be pretty busy but listened to me and then came right to the point: "What do you need to do?" My first reaction was to feel put on the spot. I thought he'd want to mull it over, hash it out, conduct an exercise in re-prioritization, etc. But instead I responded with "I need a developer and it will take 2 weeks ". He said, "OK, it's important. Do it". Problem solved...

If I were to have not thought of a solution and simply told him the problem and stopped there, I wouldn't have added any true value. I just would have laid the problem at his doorstep and waited for instructions.  That's not what I get paid to do. In that moment that I felt put on the spot, I was able to move past it & instead respond with my proposed solution and so he was able to make a decision and give the go-ahead. This is what being pro-active is all about and in that moment, I realized the truth of those sayings above.

2. I had a discussion with a medical doctor about this very same topic and she expressed to me the parallels of this in her own work. She supervises residents who would call her up with the patient's condition and explain things to her. Then silence... The residents wait for her to tell them what they should do. She can of course easily do that. She knows what needs to be done. But residency is training for medical doctors. So she simply turns the tables and asks them what they want to do. "They can suggest the craziest things; it's OK. We don't have to do it, but they need to generate ideas" is what she said. She can identify the good doctors from the not-so-good ones from interactions like these.

I'm not saying that you can't go to your manager with problems. Your manager is supposed to guide you and if you have no clue about how to go about something, then by all means ask your manager. The saying is just a reminder that we always have more power than we think in creating solutions to the problems we encounter.

Sunday, October 17, 2010

The Apprentice, Donald Trump & Project Management

The last time I watched the Apprentice was several years ago (probably more than that even: Omarosa anyone?!). I only had a faint idea of what a project manager did. I never gave it much thought. After all it was just entertainment.

However, I have recently caught a few episodes this season (Season #10) and it hit me that this is exactly what I do for a living! (I only embraced the formal role of PM a little over 2 years ago).

So I've been paying more attention this time around in the hopes of seeing if I could glean something valuable to take back to work. Unfortunately, I haven't learned much, except in the category of what-NOT-to-do!

The premise of the show is such that it pits people against each other from the get-go. Instead of focusing on a task and pulling together as a team, people are simultaneously trying to win the task but also plotting how to cast others in the worst possible light. If that happened in the military, on a sports team or some other organization that was actually trying to achieve something, those kinds of people would be kicked out. Except on "The Apprentice", they're kept around for entertainment.

One idea that I've picked up the last few years is the idea of surrender vs. succumb. I don't mean the literal dictionary meanings but actually from a different perspective. Let me re-define them:

First, succumb: To succumb to something is to give in and accept defeat, but you will make the other person wrong for it. So it wasn't your idea to watch "When Harry Met Sally"; it was your partner's. You actually wanted to watch "Batman", but fine... you'll watch it but you won't have a good time. You'll also ensure your partner doesn't have a good time by punishing him/her so you both don't have a good time.

Now surrender: To surrender to something is to give in as well *but then to treat it as if it was your idea in the first place* How novel! So it wasn't your idea to watch "When Harry Met Sally", but you know what? Why the hell not? It sounds like a blast. I'll go microwave the popcorn. You get the blankets! This creates a win-win situation. You don't punish anyone. In fact you both have a great time.

Believe it or not, this is actually possible! Lots of people go through life not even knowing that this alternative exists. But it does. And the funny thing is: you even forget you wanted to watch Batman in the first place. Life just moves on and you along with it...

So back to the Apprentice. If the teammates could actually allow themselves to be guided by the Project Manager and surrender to his/her decisions, they might actually win consistently and *never* even go into the boardroom! Now that would be a sight... I'm not saying that the Project Manager should be allowed to do whatever s/he pleases; after all, multiple perspectives and collaboration is necessary to decide how to tackle the challenges they are presented with. However, after a decision is made, the teammates squabbling and acting out (succumbing and dragging their feet) doesn't help achieve the objective. In fact it slows them all down, creates a hostile/negative working environment, purges creative energies from the team and makes them vulnerable to losing.

Meeting hatred!

There's a short blog posting on the NYTimes CityRoom blog about meetings.

Meetings Post

The author absolutely *hates* meetings.
Here, take a look at this humorous poster on meetings.

Also, someone had posted this link about seeing how much meetings actually cost in real dollars (or euros, or other currencies): Meeting Timer; It's pretty cool. Just enter a few values and go! Watch the cost of your meeting add up. pretty scary!

I personally am agnostic about meetings. I've been to meetings which have been a waste of time of course. But I've been to other meetings where we've had to hash out real technical decisions and decide which way to proceed. Everyone's input was needed. A meeting is really the only way to arrive at those decisions.

Agendas are the key to having a good meeting. Know what the meeting is for: know its purpose going in. One meeting I held was because a senior member of the team didn't feel comfortable about a technical choice in the architecture that was made. The software was already tested and running fine and was a few days away from production release but this guy just didn't feel comfortable. So I held a meeting with him and a few other senior people. I quickly took everyone through the architecture, got everyone on the same page and then voiced his concern so we could all debate it. I actually thought that was a good meeting because everyone contributed and came away with an idea of what the architecture consisted of. This senior manager felt more comfortable as well. That was my primary objective actually: his acquiescence to what was going to be deployed. I didn't plan on having any action items come out of it nor did I want to address anything in the architecture that late in the game.

Project meetings where you don't come away with action items are basically a waste of time. When I am the Project Manager running meetings for my projects, I will also take on this responsibility of documenting the items. When I first started out as a PM, I didn't do this b/c I thought someone else would do it (big mistake!) just because 'someone else always did' (and it never used to be me!)

So then I started doing it. But then I realized there was a *huge* benefit for me to do this. It entitles me to become a 'revisionist' (as in revising history!). This sounds a bit dubious but it actually is quite a very useful practice. Let me explain where it come in most handy. In some meetings, there might often be those one or two stakeholders who don't have anything to do with the project itself but throw out 10 concerns: "You're going to want to check this, and then check that, but that might be ok, as long as you check this..." It's usually the case that these people are on the periphery of the project and will actually contribute no manpower whatsoever to the completion of it. They just want to be heard. (Pigs & chickens)

As PM, I believe I have license to do what it takes to get the project done. So on my action list after the meeting, I might conveniently leave out some of the suggested items that were brought up. This all depends on the exact concerns voiced or the level of influence of the stakeholders, etc. There have not been many instances where someone has emailed me back saying I missed something. And if they do, my response is to say "I'm sorry. I've added it now". Because if they do notice it's missing and actually write me about it, I'll take that as my cue that it actually is important. Life gives you the lessons when you need it the most...

Saturday, October 16, 2010

The bright side of project practices

A good article on Projects @ Work about looking at the positives on projects rather than only concentrating on the negatives: On the Bright Side

The idea is to do MORE of the things that went well. Unfortunately, since the tendency is to concentrate on the bad and fix it, we forget the positives and to do more of those. Human beings' tendency to forget what went well and magnify what went wrong is epic. There are a # of studies in customer service that have shown that when a person has a positive experience at a business, s/he will tell 4 friends/acquaintances about it. However, if s/he had a negative experience, s/he will tell 9 friends/acquaintances about it! No wonder we quickly forget what went great and go for the bad...

In this vein, at my own workplace I am suggesting that PMs at the end of each project reflect and think about 3 things that went well about the project and that they would do again (so those are positively reinforced) and 1 or 2 not-so good things (so those could be rectified).

This kind of reflection will increase awareness of the positive things so we can bring those best practices forward into future projects.

Harry Potter & Project Management

This is a great post on the Unclutterer blog:
Post on JK Rowling's organization of Harry Potter

about how JK Rowling organized her thinking about the storylines of her Harry Potter series. I was never a Potter fan until last year. I dismissed the books as just for kids after summarily reading the first one. Luckily I picked it up again and just became entranced with the whole thing. I devoured all the books and movies one after the other. My life was put on hold until I was done... (I'm sure millions of fans around the world have had similar experiences).

In coming to appreciate the books, it dawned on me that Rowling's achievement was monumental. I was witness to a masterpiece: the books are elaborately crafted affairs with things happening in book 2 that don't rear their heads until books 5 or 6. She didn't just write the 1st book, and then after all the money came in, say "Oh that did well... Let me write another". No... she had these plotlines and twists organized from the very beginning! It is just amazing to see this mastery of organization in action!

Friday, October 15, 2010

Communication within your Project Team

I saw some things today that really threw me a curveball. Let me explain:
I sank my claws into a new project today. It's basically a collection of 'tickets' that got lumped together and got called a project and prioritized. Each ticket goes through a cycle of requirements -> design -> coding -> QA -> UAT -> Release.

I started investigating one ticket in depth and talked to the architect reviewing the design to see if the suggested approach was feasible. After 15 minutes, I knew that what was being asked in the requirements was too big and that the best way to proceed forward was to descope some things. I called over the Business Analyst who wrote the requirements spec (and who luckily sits a few aisles over) to clarify. The architect went over his concerns and the BA understood and we quickly honed in on a much more tractable solution. The whole thing took about an hour. And furthermore, the solution was so simple, that the architect simply coded it himself! Now we can actually go ahead and test it!

However, it wasn't completely as smooth and easy as I described above. There were some valuable insights I gained from facilitating the interaction.

Some of the highlights are:
1. The architect thought the writer of the requirements document was in London because he assumed the person who created the ticket (who is in London) also had written the requirements; this was not the case. The author of the document was in NY but the architect never even looked at the cover page of the document! There would have been a lot of time wasted going back and forth with the person in London trying to get clarification on requirements when the 2 people who needed to talk most were both in the same location! It's really mind-boggling how something so simple can become so convoluted. We easily could have lost 2 or 3 days if the person in London got involved and tried to be the go-between.

2. We all know one of the functions of the BA is to translate business requirements into technical specs; basically being the go-between for business & IT. One doesn't think there needs to be any kind of translation within IT itself. It's easy to assume IT staff can all talk to one another and understand each other. In yet another twist of events, this assumption has also proven not to be true. In this particular case, the architect is very technical, repeats himself, and elaborates on points to an extreme degree. He is also a non-native speaker of English and speaks haltingly. It does take some effort to really listen and draw out the salient points. The BA isn't very technical and wanted things explained at a higher level. I facilitated the conversation between them. Where the BA didn't understand things, I stepped in to explain. In some cases I would cut off the long-winded explanations of the architect and other times I would ask him pointed, leading questions so he would emphasize something important.
It dawned on me that even within IT, it's dangerous to assume we all are on the same page. Miscommunication can easily happen between 2 co-located colleagues. (Note that this is the most ideal form of collaboration: a face-to-face meeting; yet it can still go horribly wrong!)

The larger lesson here is that a Project Manager with great listening skills can make a huge difference by facilitating interactions between the various members of the team and making sure everyone is clear on next steps. Many PMs just want to stay above the action and merely delegate the tasks to the team members and collect status items to report. They can add so much more value by delving into the details of the project alongside their teammates.

Thursday, October 14, 2010

Making it in Financial IT

I subscribe to the Dice newsletter and there was an interesting article recently on Five Skills you need to Succeed in Financial IT. Click here

It's a good article and very accurate. Some of the things they get spot-on are:

  • "Educate yourself on both financial terminology and IT best practices," "This will allow you to truly understand your internal and external customers and provide a much higher level of service than someone who just has IT experience."
  • While your job may include creating and managing trading platforms, that's not your real job. Your real job is to serve the clients, whether they're internal or external. You must know to communicate with people who are very different than you, who are under extreme pressure, and probably not very nice
I really like that they point out that the people we deal with are under extreme pressure and probably not very nice. Very true! You need to develop some objectivity and learn to not take things personally. It's about getting the job done. If you're worried about a bruised ego, you'll probably do better somewhere else. I learned this over the course of my career. 

Tuesday, October 12, 2010

How many projects are too many?

Very interesting question posed in this article here: https://www.examiner.com/project-management-in-miami/how-many-projects-are-too-many-projects

It's actually an excellent question. I've been handed multiple projects simultaneously myself. Can I handle them all? How much is too much? Will I go crazy?

The article takes almost a mathematical approach, where you seemingly plug in values to a formula and out comes your answer: "Yes, that's too many" or "No, you can handle one more". Of course it doesn't do this explicitly, probably because it's actually impossible but the underlying message is that this problem is mathematically tractable and one can start to hone in on an answer.

I have a different viewpoint. Because by definition projects are unique, and you cannot predict the future, then there is no way you can even begin to apply some kind of calculus to the process. I wouldn't even try. I would let the PM make the determination as to what s/he can take on based on current bandwidth. Some of it is yes, calculated, but there's a whole other dimension involved: Intuition and gut instinct. This plays a much larger role than most people believe, I think.

The article in the link concludes with several tips for PMOs and senior management when assigning projects to Project Managers. However, this is only a one-sided communication. What's left out is: There always exists the possibility of the PM to say No: "No, my bandwidth right now is too limited."; "No, I'm still wrapping up this other project"; etc.  Perhaps this is what is called for in some cases. Constantly saying yes to more projects without assessing what you're capable of spells doom for the project and the organization right from the get-go. Brutal honesty is required. Senior Managers must be made aware that there are consequences to their actions, whether it's pulling people off projects they think are 95% done and only a minor effort is left to get the project out the door (in my experience, that last 5% requires a LOT of attention to the details to get right; you cannot for a moment take your eye off the ball) or thinking you can at least initiate a new project early-on while juggling other projects (again, the first phase of a project: initiating/planning takes up an inordinate amount of time).

PMs know what goes into making a project successful; usually a lot of hard work, determination, persistence, constant attention to detail, etc. It's a very easy trap for people who are distant from the action (like senior managers) to think of projects as encapsulated pieces of work that they can juggle and shuffle around and that can be started and stopped on almost a whim. However, the reality is that there is a price to pay for context-switching: slowing down, changing tracks and getting back to speed all take time and energy, not to mention the impact of morale when projects people have devoted themselves to take a backseat or don't get completed.

An e.g.: I have a project that I was asked to manage but I have pushed back twice so far because of other priorities that have surfaced recently. I was tempted to start the project just because of my strong tendency to delve into the unknown and solve problems. However, I've had to hold myself back because I realized that once I started, I'd create an avalanche of expectations which I would then not be able to address because of lack of bandwidth. Again, this shows senior managers that their own choices (about priorities) have created this reality. It's important to have that feedback loop where people can see the consequences of their decisions and actions. Only then will people learn.