Micro Focus | Borland

How do members of the
project team see each other?

Discover the lighter side of software collaboration

Micro Focus helps improve
software collaboration

Get your free eGuide »

Click on a
team member

DESIGNER

PROGRAMMER

TESTER

PROJECT
MANAGER

BUSINESS
ANALYST

AS SEEN BYDESIGNER

Designer as seen by designer
Close

Designer

Who else around here starts with a blank canvas and paints a masterpiece? Let's face it, this is all about concepts–and we've got them.

Programmer as seen by designer
Close

Programmer & Designer

It's all about the quality of the user experience. Strike that, it's all about the quality of the code. Do we need this chicken and egg debate? How about we ensure requirements, designs and code are well understood and communicated to our teams.

Tester as seen by designers
Close

Tester & Designer

Isn't it best to graft testing on after the design is complete? And isn't the purpose of testing to find bugs? Err no and no. Far better that we test earlier and more often to ensure we're designing what the business needs.

Project managers as seen by designers
Close

Project Manager & Designer

What's the delivery status? Repeat, what's the delivery status? Without real-time status across your Agile planning and tracking tools you'll be hearing this a lot. What's needed is single source of information–so projects can be planned and re-planned in flight.

Business analysts as seen by designers
Close

Business Analyst & Designer

One prepares neat business needs and expectations (nice job Business Analyst). The other scatters them across Agile stories and tasks (thank you Designer). Result? Neither side really understands the other. Time we talked the same language?

AS SEEN BYPROGRAMMER

Designers as seen by programmers
Close

Designer & Programmer

It's all about the quality of the user experience. Strike that, it's all about the quality of the code. Do we need this chicken and egg debate? How about we ensure requirements, designs and code are well understood and communicated to our teams.

Programmers as seen by programmers
Close

Programmers

Anyone with a brain can see our code is a thing of beauty. What you create is a hand-crafted work of brilliance. End of.

Testers as seen by programmers
Close

Tester & Programmer

One believes their coding is to die for. The other wants to kill it off, test it to destruction. But this is not about throwing bugs back and forwards, surely? Let's get the best possible product delivered according to the requirements.

Project managers as seen by programmers
Close

Project Manager & Programmer

They say programming great code is an art. And that's the problem–it's a black art to many Project Managers. How about finding some common ground? Participate together in managing the quality of your product.

Business analysts as seen by programmers
Close

Business Analyst & Programmer

The latter just wants peace to write code. The former wants to keep the peace and meet the requirements of a dozen stakeholders. What could possibly bring you two closer together? Surprisingly, it's sharing the same software.

AS SEEN BYTESTER

Designers as seen by testers
Close

Designer & Tester

Isn't it best to graft testing on after the design is complete? And isn't the purpose of testing to find bugs? Err no and no. Far better that we test earlier and more often to ensure we're designing what the business needs.

Programmers as seen by testers
Close

Programmer & Tester

One believes their coding is to die for. The other wants to kill it off, test it to destruction. But this is not about throwing bugs back and forwards, surely?? Let's get the best possible product delivered according to the requirements.

Testers as seen by testers
Close

Testers

Eliminate all other factors, and the one which remains must be the–defect! Like any good Sherlock Holmes you're a man of genius.

Project managers as seen by testers
Close

Project Manager & Tester

At last, two people with a common issue: the clock is ticking. There's no time left to test, and no time left to deliver. Probably because 50% percent of development effort is being spent testing. Automated testing anyone?

Business analysts as seen by testers
Close

Business Analyst & Tester

Who's mostly likely to say: "It's not my job to test the requirements?" Let's hope it's neither of these fine individuals. Just checking the requirements are satisfied is different than testing them. And now everyone can make that happen.

AS SEEN BYPROJECT
MANAGER

Designers as seen by project managers
Close

Designer & Project Manager

What's the delivery status? Repeat, what's the delivery status? Without real-time status across your Agile planning and tracking tools you'll be hearing this a lot. What's needed is single source of information–so projects can be planned and re-planned in flight.

Programmers as seen by project managers
Close

Programmer & Project Manager

They say programming great code is an art. And that's the problem–it's a black art to many Project Managers. How about finding some common ground? Participate together in managing the quality of your product.

Testers as seen by project managers
Close

Tester & Project Manager

At last, two people with a common issue: the clock is ticking. There's no time left to test, and no time left to deliver. Probably because 50% percent of development effort is being spent testing. Automated testing anyone?

Project manager as seen by project managers
Close

Project Managers

Costs, schedules, individual deliverables–mere mortals can only imagine how you keep it all together. Without you, the world is a more dangerous place.

Business analysts as seen by project managers
Close

Business Analyst & Project Manager

Here's where a shift in business needs or expectations can really hit quality and deadlines. Do you have the agility to change plans between iterations and have everyone understand the impact? Of course you do–if you have dynamic portfolio and release planning.

AS SEEN BYBUSINESS
ANALYST

Designers as seen by business analysts
Close

Designer & Business Analyst

One prepares neat business needs and expectations (nice job Business Analyst). The other scatters them across Agile stories and tasks (thank you Designer). Result? Neither side really understands the other. Time we talked the same language?

programmers as seen by business analysts
Close

Programmer & Business Analyst

The former just wants peace to write code. The latter wants to keep the peace and meet the requirements of a dozen stakeholders. What could possibly bring you two closer together? Surprisingly, it's sharing the same software.

Testers as seen by business analysts
Close

Tester & Business Analyst

Who's mostly likely to say: "It's not my job to test the requirements?" Let's hope it's neither of these fine individuals. Just checking the requirements are satisfied is different to testing them. And now everyone can make that happen.

Project managers as seen by business analysts
Close

Project Manager & Business Analyst

Here's where a shift in business needs or expectations can really hit quality and deadlines. Do you have the agility to change plans between iterations and have everyone understand the impact? Of course you do–if you have dynamic portfolio and release planning.

Business analysts as seen by business analysts
Close

Business Analysts

Your analytical ability is second to none. They seek the truth, the real requirements, and it's you who provides.

Share