TrainingConferencesAbout UsContact UsAdvertiseSQE.comRSS Feed

StickyMinds.com: brain food for building better software

Log In
 Clarify Your Search Criteria

Tips on Using Our Search Feature(s)
 
StickyMinds.com Home
ResourcesTopicsCommunityPowerPass
Home  >  Detail: Hurdling Roadblocks



A StickyMinds.com Original
Article Picture
Hurdling Roadblocks

By Danny R. Faught

Send This Content to a FriendGet a Short Link to This ContentPrint This ContentSee User Comments About This Content

Summary: We all encounter things at work that impede our progress. Having the skill to effectively deal with the roadblocks makes a big difference in your overall productivity. Will you get a reputation as a whiner or as someone who pushes through obstacles? In this week's column, Danny Faught offers help with two common types of roadblocks and gives suggestions for reducing the chances that any barricade will impact your schedule.


Borland
I'm working on a project that is littered with roadblocks, yet I'm still making progress. I'll share with you how I take a positive approach to clearing roadblocks and staying productive, even when I have trouble getting the things I need. Though the solution requires getting managers involved, I should point out that my role on the project is technical, not managerial.

Someone You Need Help From Isn't Helping You
There will be times when you'll depend on someone else's help to complete a task--for example, acquiring or setting up test equipment, creating network accounts, or fixing bugs that block your testing. When you ask the person you're waiting on when he'll have the task done, he either may give you a date that's later than what you need or may not commit to helping you at all.

Look at it from the other person's point of view. His manager has asked him to get certain things done, and your task might not even be on his to-do list. Tell your potential helper that this is a problem for you and that you're going to ask for help from management. Your attitude is very important; you're not tattling on this person, just pointing out that you can't get done what you've promised because of priorities that you can't directly control. The person genuinely may want to help you but can't meet his current commitments if he does. If you approach the situation from a constructive point of view, while keeping in mind that your potential helper takes direction from someone other than you, you're much more likely to succeed.

Explain to your manager how your commitments are in jeopardy because of dependency on helpers who have separate things to do. Discuss whether it makes more sense for your helper's priorities to change, for you to adjust your own commitments, or for you to embrace another creative solution.

If the person works for a different manager than yours, the problem needs to be discussed with that manager. It's most effective if you and your manager talk to the other manager together. If you already have a good relationship with the other manager and have trouble finding a meeting time that can include your manager, you may want to talk to the other manager alone. Or your manager may decide to tackle the issue alone, in which case your dependency has now shifted to your manager.

Remember, this is not a process of complaining. Your goal is to explain the situation matter-of-factly and discuss the consequences of not taking action. Think beyond your own responsibilities, and be ready to discuss things from the point of view of the organization as a whole.

You Aren't Getting the Guidance You Need
Sometimes you need a decision from someone in order to guide you in the right direction. It can be very frustrating when you can't get a straight answer. Here are a few ideas to help get the answers you need to move forward.

Find out when is a good time to talk to the person you need an answer from. Some will grumble about how busy they are until you offer to schedule a meeting. Scheduled time is easier for people to accept than unplanned interruptions. Keep the meeting length to thirty minutes or less if possible. It might give you some anxiety to have to wait a few days to get in to see them, but most decisions you're seeking answers for aren't actually emergencies. When you demonstrate that you use people's time wisely, you start building relationships that will give you quick cooperation in the future.

In one extreme case, I wanted feedback on my testing strategy from the director in charge of the product under test. The director said he had no time available to schedule a meeting. So I carefully formulated a list of questions to elicit the feedback I wanted--still, no response. I then filled in the answers myself, labeled them as "assumptions," and shared them with the director. These assumptions represented my best guesses about what the answers would be. I made them crisp and unambiguous, so it would be clear to the reader if they weren't right. Even this didn't generate a response from the director, but it did create a paper trail showing the direction I was taking and gave my manager a succinct summary of my plans that we could discuss.

You might be tempted to tell someone "I assume that we don't actually need to do this work at all." That might be the most reasonable assumption in some cases or at least the most likely provocation to get a response, but be careful not to unnecessarily escalate emotions. My documented assumptions helped cut out large swaths of scope, but didn't suggest that we abandon testing entirely.

Avoiding Roadblocks
If you've been able to get the wheels in motion to demolish a roadblock, you may still have to wait until the roadblock is fully cleared. Here are some tips to mitigate that wait time:
  1. Anticipate what roadblocks may lay ahead. Get started on clearing them early, before they're in your critical path.
  2. Use scarce resources wisely. When you see an opportunity to use some resource that's not always available, adjust your priorities to use it when you can.
  3. Keep a to-do list with more than one item on it. When one task gets blocked, shift temporarily to a different task. I keep a Scrum-inspired, personal to-do list, with items ranging from an hour or less up to a day or two of effort, even when the project I'm working on does not use an agile process. I share this list with my manager regularly and discuss the priorities, so I'm always prepared to make a brief shift without needing immediate feedback from the manager.
Don't think that you shouldn't have to work with managers if your own work is more technical than managerial. Managers need to know as soon as possible when you have tried all the avenues within your power and you're still stuck. You should enable them to help keep your work on track or modify your commitments if necessary.

Encountering roadblocks is frustrating. We'd like for everything we need to be handed to us, but then our resourcefulness wouldn't be needed on the job. Don't be afraid to invoke the services of the managers in your organization. Work from the premise that everyone is generally doing what they've been told to do, but you're providing crucial new information that might indicate that priorities should change. Develop the discipline of tackling roadblocks calmly and constructively, and you'll quickly gain a reputation as a highly effective contributor to the organization.

Further reading
  • Becoming a Technical Leader, Gerald M. Weinberg
  • Agile Software Development with SCRUM, Ken Schwaber and Mike Beedle


About the Author
Danny R. Faught is an independent consultant focusing on load testing, agile test automation, and exploratory testing. You can contact him at faught@tejasconsulting.com or www.tejasconsulting.com.

Danny thanks Johanna Rothman for her help with this article.

Back to Top
 

StickyMinds.com Weekly Column From 10/2/2006 

Member Comments
Add Your CommentExpand Comments
 
Comment:    
by Geoff Plumstead 4/25/2007

My 'top tips' would be ...

1. Prefix any verbal / email request with something like "I know you must be very busy at the moment, but I need your expertise to ..."

- I know it sounds a bit toadying (feel free to change the wording!), but it acknowledges 2 important things. One, you understand they have other work items & you are asking to add something else to their 'to do' list. Two, they have skills / expertise that you need. Hey, a little flattery / praise never hurt anyone (providing it's deserved!).

2. Tell them clearly what you think you need. Give them as much information as possible to be able to make...Read On

 
 
Comment:    
by Sidney Snook 3/7/2007

There is also the nautical approach to "roadblocks":
"Damn the torpedoes, full speed ahead!" - Admiral David Farragut
...or "I'd rather beg forgiveness rather than permission."
I have used these approaches to project "roadblocks". While these appraoches usually have lead to project success they often have also lead to a lot of extra effort doing more effort or someone elses's job...and a lot of "dead or wounded bodies" (relationships) along the way. However,sometimes on ultra-critical, high-risk projects these appraoches are justified...and necessary.

One day at a time, friend!

Author's Response:
3/7/2007    
Hi, Sid. Yes, I often wait to ask for permission until after I've done the action in question. Only rarely do I have to ask for forgiveness afterward, so it sounds like this approach has been more successful in my case.

By the way - does it matter if you do something that's "someone else's job?" If you do it right, helping the person who should be doing it but can't adjust their priorities to make the time for it, it can be a successful way to shuffle resources. I agree that sometimes you'll ruffle feathers if you can't get the cooperation you need, but still from the point of view of your sphere of influence, you've successfully gotten your job done the best way you could.

In practically all of my projects, there's some amount of "damn the torpedoes," i.e., choosing to work in a minefield, at least at the point they bring in consulting help. Some people like these projects and others don't; fortunately, you have a broad range to choose from out there.

 
 
Comment:    
by Jered Biard 10/10/2006

What would you suggest is the proper course of action if your manager is the one putting up roadblocks to your progress? In this case it is not intentional, but the manager in question is entrenched in the development of a new product. The test team needs a complete set of requirements and other documents to be completed, but human resources are limited. Development deadlines are fairly tight, and apparently time was not allocated to handle proper documentation. I am sure the QA team will be held accountable for the release of "working" software, but without proper doc, we are hunting the proverbial needle, but without knowing what a...Read On

Author's Response:
10/10/2006    
It's quite possible to find problems the developers will want to fix, even without having any documentation about the system. You might miss some important bugs, especially missing features, and it's important that your manager understands this and agrees that that's not your fault. Don't accept responsibility for the quality of the software--that's dangerous to do even when you do have solid requirements. Find out what your manager expects of you and determine now whether you can meet that expectation with the resources you have available.



For more about this topic, see the classic article "Testing in the Dark" -- search for the title (including the quotes) on StickyMinds.

 
 
Comment:    
by Chris Hansen 10/4/2006

Very interesting article. My take on management is that a manager is there to ask you the question: "Are there any roadblocks in the way of your doing your job? How can I help remove them?" My experience is that in business, personality often gets in the way of getting others to do what you need them to do. Internal politics often intrudes as well. Thus, it's not as clearcut as it might seem to get assistance from someone else whom you yourself do not work with or manage. I have had experience with a manager who, in fear of his own job, did not back me up in this type of situation. How would you deal with that? I ended up moving laterally in...Read On

Author's Response:
10/4/2006    
The manager should ask about roadblocks, but the people on the team shouldn't wait for the manager to ask. When the manager asks the question, it serves as a reminder to ask for help when needed, and often it prompts a response not at the moment but a few days or weeks later when someone hits a roadblock. In the difficult situation you mentioned where your manager isn't being helpful, what you have to do is renegotiate his expectations. Does he admit that there's a roadblock that is difficult to clear, and thus change what you're expected to get done? You should be proactive in trying to influence other people in the organization to help you, but if your manager expects you to do this successfully every time without his help, you will eventually fail to meet his unreasonable expectations and will need to make a move at some point.

 
 
Comment:    
by krishna kumar 10/3/2006

Your article has very valuables inputs and tips to tackle roadblocks.

Author's Response:
10/4/2006    
Glad to know it was helpful. Here's one more tip that helped me on the job yesterday - offer to help your manager when she encounters a roadblock that affects your work. My manager needed me to investigate why we encountering a reliability problem in production that we weren't seeing in the test environment. She needed to get access to resources from another manager before I could get started. I offered to work with this other manager myself to get it done. So even though my manager was in meetings most of the day, we were making progress on the issue.

 
Back to Top


Marketplace

Web based bug tracking - AdminiTrack.com
AdminiTrack offers an effective web-based bug tracking system designed for professional software development teams.

BugSplat - Automatic Crash Analysis
Fast online exception analysis. Capture customer crash data online.

Six Sigma Certification
100% Online-Six Sigma Certificate from Villanova - Find Out More Now.

Census: Web-based Bug Tracking and Defect Tracking
Track software bugs, defects, enhancements, support calls, and more. Issue tracking software that is scaleable, fully customizable and integrated with VSS. Includes e-mail notifications, role-based workflow, change history, and Crystal reporting.

Need Agile Test Cases?
Create statistically complete test cases simply and quickly.

Get your product or service listed here.
Subscribe to Better Software Magazine
Subscribe to Better Software Magazine

First Name:

Last Name:

Email Address:


Home   |   Resources   |   Topics   |   Community   |   PowerPass



© 2008 StickyMinds.com. All rights reserved.
StickyMinds.com is a division of Software Quality Engineering.
Privacy Policy    Terms & Conditions    Link to StickyMinds.com    Feedback


Software Quality Engineering

Borland



STARWEST 2008

 
Agile Development Conference 2008