Showing posts with label Management. Show all posts
Showing posts with label Management. Show all posts

Monday, November 5, 2007

PM Q: What causes a project to slip?

Q: What causes a product or project to slip schedule in your opinion? Where have you had the most problems in the past?


Mistake #1:

Everything in life is a tradeoff and software projects doubly so. Oversimplifying a little, the three variables of software projects are the amount of resources (and that typically means people), the product’s features and lastly, the time to market. You can not change one without affecting at least one of the others.

There are limits to this. Getting 100 people to do 100 features in a week would, in fact, create a program, but probably not something that would be a good program.

If time to market is the number one priority, then features and/or resources must be ruthlessly adjusted to keep the schedule on track.


Mistake #2:

Not enough buffer in the schedule. The different team members will give you estimates of how much work the different tasks require. The key word is estimates. There are a lot of techniques you can use to maximize the accuracy of the estimates, but in the end, people are always going to be optimistic and the only way to address this is to make sure there is room in the schedule for mistakes.


My Feelings:

It’s not IF the project will slip, it’s WHY the project slips.

Projects where the date is the most important thing are called “Slogs” or “Death Marches”. You can’t ask a team to do too many of these without repercussions. Projects that allow features to change or new ones to come in willy-nilly never ship and are just as painful to work on.

I like a reasonable number of milestones whose dates are adjusted as they approach. If too many milestones are coming in late, then program management digs in and figures out why, fixes it and then adjusts the rest of the schedule.

And to keep things more fun, besides the normal buffer, put in some time at the end for creative new ideas and market course corrections.

Friday, November 2, 2007

PM Q: How do you prioritize features?

As many of you know, I'm interviewing for a new job. It's going really well. Yesterday I had to write up a screening document and I thought I would share some of my answers here.

I wish I had had a few more days to polish and simplify my answers, but they are still comprehensable. I start the document out with just about my favorite Mark Twain quote: “I'm sorry this letter is so long, but I did not have time to make it shorter”

-----------

How do you prioritize features? What criteria do you use?

At the highest level: Must have, Should Have, Could Have.

Although generally worked out long before a feature list, big items like business priorities, time to market, globalization, industry laws/standards, revenue models, applied laws, and other items at this level are the first stop.

And I like a very tight vision statement or mantra that the whole company believes about a release. It needs to be so clear that it is immediately apparent to everybody on the team if a feature moves the release in the right direction or not. For example if this release is all about making sure we find every document, we would prioritize supporting the Macintosh over features that go very, very deep into specific file types.

I like the feature team itself to make this call. I like for the developer and tester to sit down with the PM and talk about the features in context and make the first stab at it.

I also like good user and market research, based on science if at all possible. Things like usability testing, experimental releases, betas, etc. Periodic customer Strategic Design Reviews are great. I want to know the other products in our market space better than most of their employees do.

I like to do feature level SWOT analysis: Strengths, Weaknesses, Opportunities and Threats. This can keep the most important issues front-of-mind even if they are not that obvious. Sometimes it a feature looks very cuttable until you remember that this feature plugs a hole that could keep the company out of trouble in Indonesia.

If I’m pulling together a team wide prioritized feature list then I typically need to do some balance between the different feature teams’ prioritization. With all of the above data, matching these up is generally pretty obvious. Then I publish the list in an easy to understand manner and gather feedback and make adjustments. If possible, I would love to do a team offsite on this and get bottom-up buyoff and feedback. The more I can get the team on the same page here the easier the rest of the journey is going to be.

And one last thing I like is to have some space at the end of the schedule for a feature to come back. I create a mini-milestone that can be used as extra buffer if needed or for the team to sort through all the postponed features and new ideas and pick a few that are implementable. This takes the pressure off any one feature cut and also gives a way for the team to be more creative or more responsive to any late breaking market pressures.


-------

More soon...

Wednesday, March 28, 2007

James Burke Information Surge talk

James Burke came to Microsoft and gave this speech when I was on WinWord 2.0 (or so). It rocked my world. The whole Word team changed a bit of their focus away from adding more features and towards creating ways for people to re-order information. I just found this talk online and didn't want to risk such a treasure getting lost in the mists of time. I think you can still see the truth of this reverberating through society over the PC specifically.

---------------

Each time there was a major advance in the ability to generate, store or disseminate knowledge, it was followed by an "information surge" and with it a sudden acceleration in the level of innovation.

Thanks to information surge, each one of us in the modern world has more machine power available at a fingertip than any Roman emperor. A medieval king would have needed legions of horsemen riding for months to be able to deliver one-thousandth of the number of messages we can transmit in a few moments to the ends of the earth by phone or fax. A single CD-ROM can carry the whole of Renaissance science and philosophy.

When information surge happens, it sweeps through human society in a powerful, innovating wave that in some way changes everything everywhere. Surge brings together people and places and ideas in totally new ways. From these new relationships come new entities and new ways of living. Most important of all, information surge changes the way we think. We are experiencing a transformational surge of innovation and convergence of information technologies.

Three thousand years ago the Greek alphabet was the first truly transparent means of communication, because it could be used to express any language. But in the way left-to-right script was processed in the brain, the alphabet also triggered the analytical, step-by-step mode of thought that would give us logic. We could now cut up the universe the better to understand it. Before the alphabet, such an idea was, literally, unthinkable.

Today we stand on the threshold of another such revolution in thought. It is already happening in the most esoteric disciplines of science. Some of the most important equations in fundamental particle research, for instance, can now be attempted only because supercomputers can solve them in a few months. Before, since they would have taken more than a researcher's lifetime to complete, they could not even be attempted. Bringing this extraordinary aspect of knowledge manufacture to the service of society as a whole raises questions that will have to be answered. For example, can we accept and live with innovation that cannot be explained by the innovation machines because we do not live long enough to hear the whole explanation?

The answer to this kind of challenge may lie within the same systems that generate them, in the form of electronic agents. These surrogates are not new. Each time surge occurs (and with it, massive increases in the levels of innovation), society has delegated responsibility for handling the effects to filtering entities. After Descartes' scientific method triggered the scientific revolution of the seventeenth century, the avalanche of data was diverted into different management disciplines. Today there are over twenty thousand of them, from anatomy to zoomorphology.

Electronic agents will explore the treasure house of this specialist, arcane knowledge that will be made available to everybody by the next information surge, in order to find for us only what we need at the time and to translate the data into forms that are individually meaningful to each of us.

This new freedom of access to information through the networks spanning the globe will also change the social meaning of information. Up to now, the limitations of communication technology at any time gave special importance to all knowledge, irrespective of what it might have been, simply because it was inaccessible. What was not generally available was usually regarded as valuable.

The innovations produced by the few people who had access to this secret knowledge were, from time to time, let loose upon communities who had to adapt to it as best they might. Such esoteric innovation was impossible to prepare for because it was inaccessible, its effects were serendipitous. How could anyone have foreseen that Venturi's investigation of water-flow dynamics would lead to the perfume spray that would in turn make possible the carburetor?

The coming information systems will offer the chance for people to see these patterns of innovation even as they occur and to make judgments about them before their effect on society has to be accommodated. With open sources of information, technology assessment will finally be possible, unhindered by ideological half-truths. The same will be true of the process of political participation, suggesting a rapid end to the present representative system, designed for the eighteenth century and failing us today.

Institutions of many kinds will be changed or even removed by the next surge. When an American manager can, in real time, run automated factories in Argentina the way a Rome accountant says the Berlin headquarters requires, with software uplinked via a Japanese satellite from Korea, what happens to national sovereignty and the hundreds of items of domestic legislation that will then be obsolete?

This kind of networking is typical of the way in which information surge generates social complexity and, with it, diffusion of power outwards from the center. The fifteenth-century printing press broke the hegemony of Rome, gave political control to a hundred kings and princes around Europe, and brought the birth of the nation-state. The next surge will also shift power in much the same way, but at every level and in every place around the world.

(c) James Burke

Tuesday, March 27, 2007

Yea Seth Godin!!!! -- Doing the Basics Well!

I slammed Seth in one of my posts in January, so I thought it only fair that I promote him to almost godhood in another.

He says about upping your site's traffic --

Hey. It's not so hard. If you make great stuff, people will find you. If you are transparent and accurate and doing what's good for the surfer, people will find you. If you regularly demonstrate knowledge of content that's worth seeking out, people (being selfish) will come, and people (being generous) will tell other people. It turns out that it's easier and faster to do that than to spend all your time on the shortcuts.

I've been trying to tell my clients this for years. Like everything else in business, it's all about doing the basics well. When you finish that, you can move on to the fancy-shmancy things. The misleading part of that statement is that I don't know of anybody that has ever finished with doing the basics well.

Friday, February 9, 2007

How to be Remarkable & Is Your Boss an Asshole?

The Battle of the Asses

Blogger has made a mess of the formatting of this post, but I wanted the table layout more than anything else. The HTML is clean (except to blogger) and you can see a clear version of it here. I hate blogger. While reading this on blogger, be sure to scroll down a lot.


When I read Guy Kawasaki's post this morning, I couldn't help but recall Seth Godin's post from a few months ago.

Are these top marketing pundits describing the same person? (I didn't change the order of these, only published these side by side)

























































Seth Godin's
How to be
Remarkable



Guy Kawasaki's
Is your Boss
an Asshole?


Understand the
urgency of the situation. Half-measures simply won't do. The only
way to grow is to abandon your strategy of doing what you did
yesterday, but better. Commit.
Thinks that the rules are
different for him
For example, a parking space for handicapped
people is really for handicapped people plus him because his time is
so valuable that he can’t walk fifty additional feet. Or, the
carpool lane is for cars with multiple people, hybrids, and her
because she’s late for a meeting
Remarkable doesn't
mean remarkable to you. It means remarkable to me. Am I going to
make a remark about it? If not, then you're average, and average is
for losers.
Doesn’t understand the
difference between a position making a person and a person making a
position.
The vice-president of acquisitions for a big media
company is a big deal, but all her power, and therefore the ability
to act like an asshole, evaporates without this title. Assholes
usually don’t understand that their current position affords them
temporary privileges.
Being noticed is not
the same as being remarkable. Running down the street naked will get
you noticed, but it won't accomplish much. It's easy to pull off a
stunt, but not useful.
Requires “handlers.” This
means a personal assistant, appointments secretary/lover, public
relations flunkie, and chauffeur. It’s funny but if an asshole
didn’t have the position/money/status, he would probably be able to
answer the phone, make appointments, talk to the press, and drive
himself.
Extremism in the
pursuit of remarkability is no sin. In fact, it's practically a
requirement. People in first place, those considered the best in the
world, these are the folks that get what they want. Rock stars have
groupies because they're stars, not because they're good looking.

Requires the fulfillment of special
requests in order to be happy/productive/efficient.

For example, she needs a special brand of spring water from the
south of France bottled by chanting monks when she’s making
a speech. This type of actions represent flexing for the sake
of flexing—not because any of this crap is necessary.


Remarkability lies
in the edges. The biggest, fastest, slowest, richest, easiest, most
difficult. It doesn't always matter which edge, more that you're at
(or beyond) the edge.
Requires the fulfillment of
special requests in order to be happy/productive/efficient.
For
example, she needs a special brand of spring water from the south of
France bottled by chanting monks when she’s making a speech. This
type of actions represent flexing for the sake of flexing—not
because any of this crap is necessary.
Not everyone
appreciates your efforts to be remarkable. In fact, most people
don't. So what? Most people are ostriches, heads in the sand, unable
to help you anyway. Your goal isn't to please everyone. Your goal is
to please those that actually speak up, spread the word, buy new
things or hire the talented.
Relates to people primarily
in terms of what they can do for him.
In other words, “good”
people can do a lot for him. “Lousy” people aren’t useful. The way a
lousy person becomes a good person is by showing that he can help
your boss in some way.
If it's in a manual,
if it's the accepted wisdom, if you can find it in a Dummies book,
then guess what? It's boring, not remarkable. Part of what it takes
to do something remarkable is to do something first and best. Roger
Bannister was remarkable. The next guy, the guy who broke
Bannister's record wasn't. He was just faster ... but it doesn't
matter.
Judges people by her personal
values, not the employees’ or society’s values.
Assholes judge
people according to only what they think is important. For example,
a boss may value only professional accomplishments, so someone who
is “merely” a mom or dad with a focus on a family is therefore
inferior
It's not really as
frightening as it seems. They keep the masses in line by threatening
them (us) with all manner of horrible outcomes if we dare to step
out of line. But who loses their jobs at the mass layoffs? Who has
trouble finding a new gig? Not the remarkable minority, that's for
sure.
Judges employees’ results and
his intentions.
A boss never comes up short when he juxtaposes
his intentions (“I intended to do your quarterly review”) versus an
employee’s results (“You didn’t finish the software on time”).
Instead, a boss should judge his results against his employees’
results and never mix results and intentions
If you put it on a
T-shirt, would people wear it? No use being remarkable at something
that people don't care about. Not ALL people, mind you, just a few.
A few people insanely focused on what you do is far far better than
thousands of people who might be mildly interested, right?
Asks you to do something that
he wouldn’t do.
This is a good, all-purpose test. Does your boss
ask you to fly coach while she flies first class? Does she ask you
to work weekends while he’s off at a hockey tournament? I’m all for
using boss time effectively (for example, not making her drop off a
package at Federal Express), but were it not that your boss could be
doing something more valuable for the company, would she do what
she’s asking you to do?
What's fashionable
soon becomes unfashionable. While you might be remarkable for a
time, if you don't reinvest and reinvent, you won't be for long.
Instead of resting on your laurels, you must commit to being
remarkable again quite soon.
Calls employees at home or on
the weekends.
Rarely, as in once per year, this is okay, but any
more often and your boss is certifiable. His happiness is not your
problem 24 x 7. You are entitled to your personal time and space
because slavery was abolished a long time ago in America.
Believes that the world is
out to get her when faced with criticism or even omission.
For
example, bloggers don’t write about her because they are all jealous
of her. Frankly, it’s more likely that he’s not worth writing about
than the blogosphere is colluding against him. This boss needs to
learn that “it’s no always about her.”
Slows down or halts your
career progress.
One can forgive or ignore the previous nine
issues, but this one is by far the worst thing an asshole boss can
do. Usually it’s a matter of convenience: “How can you leave me? I
need you.” For doing this, a boss should go into the anals (sic) of
asshole-dom. God didn’t put you on this earth to make your boss’s
life better, so don’t hesitate to abandon a boss who holds you back.

The Platinum Rule

Over in the Seattle Biznik community, I got into a discussion about Squeezed Pages (see below). And I came up with a particularly clever turn of phrase, even if I do say so myself! Below are my replies from that discussion, edited a little to keep this as small as possible. But the phrase is:

Just goes to prove the Platinum Rule, which is “There is no Platinum Rule.”

It seems like there are all these rules of marketing and management. There is always somebody telling you that you should do X because of some rule. And then somebody else will come along and tell you that doing X will break another rule. I have always found that when people start quoting rules, it is really time to rethink the project. But now I have the the Platinum Rule to quote.

Ok, here is the phrase in context:
--
Squeezed .vs. Non-Squeezed Web Sites

Non-Squeezed world:
1) Visitors can explore your site without joining first
2) When they join, you gather just the name/email visitor information
3) You send out generic mass mailings

Squeezed world:
1) Site visitors must join your site before they can see anything
2) You gather email and as much other information as you think you can get from site visitors
3) You send personalized mailings to individuals.

How do I say this? A squeezed site is considered slimy by many people. Not that slimy is necessarily wrong, but there is a cost to be paid for employing those tactics.

Modern trends suggest implementing this using transparency and reciprocation.

Visitors are able to play around your site and get to know you before you ask them for their information. And when visitors do give you something (their information), you should give them something. So a more polite version of Squeezed Marketing would be an offer to email them one of four eBooks for signing up on the site. You can then make your response back to that user more personal by using something from the book they chose.

- - -

Overnight I thought of two squeezed sites that are good: The New York Times and LA Times are very quick to make visitors join and ask for a lot of information and they send targeted mass mailings. But somehow it's OK coming from them.

Just goes to prove the Platinum Rule, which is "There is no Platinum Rule". :-)

Sunday, January 28, 2007

Managing a Test Manager or Seeing the Big Picture

I was waxing nostalgic about my old career as a test manager and found a blog entry that was the same rant that I used to rant about all the time: http://shrinik.blogspot.com/2006/12/why-counting-is-bad-idea.html

I wrote comment on the blog, and although it’s written to other testers, I think its biggest value could be to those people that have to manage test managers.

When I was a test manager, almost without exception, I was managed by people who had no clue about a) the purpose of test b) what test managers and test teams could do for them and c) when or why test needed any of their time, except for ship weeks. I had to teach my bosses the answer to all three of those things, but it was often hard because they thought they had the answers.

One of the lessons I learned as a test manager combined with those I learned running my own business can be summed up as this: Achieving the big picture is more important than getting people to tell you about it. Yes, managers have to know the progress towards a goal, but there is a right way and a wrong way to achieve that. I think every manager needs to be reminded occasionally that the purpose of employees is not to make their job easier. And sometimes, like with a test team, it isn’t as straight forward as it seems. Understanding the underlying strategic purpose of each person or group’s job is really the key to success.


-------------------------------------


Ok, back to the post, "Why counting is a bad idea", basically says that anybody who thinks that they are getting good information when test is forced to produce reports that say things like: “Number of Test cases prepared: 1230, Number of Test cases Executed: 345, Number of Test cases Failed : 50” is wrong.


As an ex-test manager I disagree that numbers are bad, they are vital, but probably not why you think.

The purpose of testing is not to find a large number of bugs. I remember a project where I had two very different developers. Developer 1 was a little sloppy and did mostly UI type programming and his weekly large check-in was worth an easy 20 bugs. Developer 2, who was a god, did the deep architectural stuff and did a check in perhaps every month. We were lucky if we got one bug off of his code with a solid week of testing. Typically all the bugs from the testers of these developers were high risk bugs, but 80 bugs to 1 bug was no way to judge the productivity of the testers or the stability of the product.

Testing’s job is not about quality assurance, either. Everybody on the entire product team must own quality. If anything close to a “They will find this in test” attitude grows in your development team, that product is doomed to be low quality. This product will never feel right, it will never be smooth. No matter how much time and effort the test team puts on it. The old joke between Microsoft Test Managers was “I own quality for the length of time it takes my boss to walk to my office.”

So, if the purpose of the test team isn’t to find a large number of bugs (even high risk bugs) and it’s not to assure quality, what is it that they are asking us to do?

The purpose of the test team is to accurately communicate the status of the product.

The amount of testing applied and the number of bug reported are the best way to know the current status. But only when the status is communicated in context of the entire environment, which includes people, bugs and coverage, project goals and schedule. Those that try to simplify something thing this big and complex in to “500 cases run and 4 bugs” is very likely to have a huge surprise waiting for them at ship time.

Or to put it another way: A spec isn’t done when it hits 100 pages, why is it logical to think test is done at 100 test cases?

In the above example, I, the test manager, knowing what I know about the changes the developers are making and seeing the number, location and types of bugs, and by talking to the whole product team (especially testers), could make a very good educated guess as to accurate product status.

I could say something like, on a scale of one to ten, we are a three. Last week we were a two. But there is a lot of new code coming in, so I suspect next week we will be a two again. But after that, we are doing a stability drive towards beta, and if things go as planned, and we are mostly on track for it; right now I have a confidence level of nine. These are the numbers they really want, but don’t know how to ask for. This kind of roll-up needs to be done for all the different product areas, too.

If you do not give the rest of the product team that kind of black and white numerical status roll-up, they will find some horrid way to squeeze one out of you, and they generally go to test cases or worse.

One exception to numbers that I have seen work is pictures. I’ve known of some product unit mangers that were most happy with something as simple as a picture of a stop light. Green – Things were humming along as planned, Yellow – there were some storm clouds gathering that should be addressed now and Red – the product was blocked or there was some other huge catastrophe. It sounds simple, but it generally takes the test manager quite a few hours to accurately color.

The management team just wants some simple way to accurately know the status of the project. It’s not their desire for numbers that is wrong. In a void of anything else, they ask for what they think they want. It works out much better if the test team can supply them with the status numbers they really need before they think to ask for those other abominations.

Saturday, January 20, 2007

repost - Note to NBCU - How to use Social Networks

January 17, 2007

After I shreaded NBCU's press release, I've been asked what NBCU should do about social networking.

First I would spend a lot more than an hour or two thinking about it and I would make decisions based on research and not my gut. Also, I'm not assuming that NBCU should do anything about social networks. I think an overall NBC site would be almost worthless (but that's another post).

One "given" is that there will always be numerous communities that exist for every TV show. The least popular shows probably have a few thousand. There is no way to create a community that is so good that these other communities won’t exist.

And even trying is a mistake. Each of these communities represent approximately a few hundred people that love the show (or tens of thousands). These are your evangelists not your competition. It's never a good idea to squash your fans. The fact that there is a vibrant community on MySpace is awesome news. All the Network needs to do is augment these communities.

They should find every The Office community and figure out ways to make those communities better. They should give awards to the best The Office community. They should budget some of their stars' time to do chats on these sites. The more they make these sites successful, the harder these armies of evangelists are going to work to make The Office a success. Holding contests is great, but communities win, not individuals. You can still be the host of content (as opposed to YouTube), but you are not the "go to" place. Create the content so that 24 sites can do things like have scavenger hunts around the net for some mocked up terrorist pages. Touched by an Angel communities could have charity drives and good works goals.

I would have a team of people whose job would be making these communities a little better every day. Their jobs would range from programming a custom widget for a particular community to helping another community tune their Google search information. The average team should breakdown something like this:

• 1 Manager
• 1 Marketer (not a publicist, that’s done elsewhere)
• 1 PR person
• 3 Program Managers (technical project managers and marketers)
• 3 Code Programmers
• 1 Flash Developer
• 4 Testers
• 3 Editors/writers
• 3 Graphic Artists
• ----- 20 people (and some times larger depending upon the
show).


That sounds like a lot of people. And I don't think every social site on the web needs 20 people. Sometimes a half of one person is enough. But the overall number of viewers to be serviced here is huge. One of the biggest mistakes I see companies do is to make a push into this wacky world of social networking and then leave after they have "something" built. It’s like inviting a bunch of people to a party, decorating and leaving 10 minutes after the guests arrive. The guests are all going leave after a little while because they are just too uncomfortable. They will also be a little angry for having been lied to.

Every community you build (or even a community of communities) needs nurturing. To keep people coming back it needs to be updated often with very compelling content. Somebody’s got to create that content. It’s either going to be the network or a few overworked and harried community managers that are doing this “for fun”. It takes a lot of technical people and infrastructure to create excellent online communities.

I would staff these teams with creative people that are fans of the show from around the world. They should be little islands separate from the other little islands and the network mothership. They must feel uncensored ownership and creative freedom and have the charter to do what is best for their show. Then I would sit back and watch the scores of evangelists recruit new evangelists and a groundswell of new viewers watch the show.

Now, this assumes that all of this is about getting new viewers. If NBCU is trying to build a site to drive new ad revenue that's a different story. Maybe that's possible, but it's still not the best idea and a very, very different approach is needed (but that's a different post).