……………………………………………….Expertise in .NET Technologies

Software Project Team

Posted by Ravi Varma Thumati on March 16, 2009

Explain the organization of software project team.

Software Project Team Organization

A project team, no matter what size, needs to differentiate among the various roles played by team members. On small projects, several roles may be performed by one person.

Project manager

The project manager is responsible for orchestrating the detailed technical work of the project, including development, quality assurance, and user documentation. The project manager is responsible for developing the project’s software development plan and is usually the development team’s link to upper management.

Product manager

The product manager is responsible for integrating project work at the business level. On commercial software products, this work includes marketing, product packaging, end-user documentation, end-user support, and the software itself. On in-house projects, this work includes working with groups that will use the system to define the software, setting up training and user support, and planning for cut over to the new system.

The architect is responsible for the conceptual integrity of the software at the design and implementation level.

User-interface designer

The user-interface designer is responsible for the conceptual integrity of the software at the level visible to the user. On in-house projects, this role can be played by someone from end-user support, user documentation, development, or product management. On commercial products, it should be performed by a user-interface specialist.

End-user liaison

The end-user liaison is responsible for interacting with end users throughout the project walking them through the prototype, demonstrating new releases, eliciting user feedback, and so on. This role can be performed by a developer, product manager, or someone from end-user support.

Development Lead

The development lead is the mid-point in the path between being a developer and being the solutions architect. They are still rooted in the reality of the code and the capabilities of the developers they have working on the project. They were once developers themselves and instead of spending all day every day coding their own tasks they now lead and mentor developers as the developers have problems that they don’t understand.

Developers are responsible for the detailed design and implementation of the software. Developers are responsible for making the software work.

The quality assurance personnel plan and manage test activities, create detailed test plans, and perform tests. They are responsible for finding all the ways to make the software break. If the project is large enough, these people may have their own QA lead or manager.

Tool smith

The tool smith is responsible for developing build scripts, maintaining the source-code control system, developing specialized utilities needed by the project, and so on. Build coordinator. The build coordinator is responsible for maintaining and running the daily build (discussed in Chapter 14) and for notifying developers when their source code breaks the build.

Risk officer

The risk officer is assigned to watch for emerging risks,

End-user documentation specialists

These specialists are responsible for generating help files, printed documentation, and other instructional materials that end users will use.


What are Stakeholders?

Stakeholders are an integral part of a project. They are the end-users or clients, the people from whom requirements will be drawn, the people who will influence the design and, ultimately, the people who will reap the benefits of your completed project.

It is extremely important to involve stakeholders in all phases of your project for two reasons. Firstly, experience shows that their involvement in the project significantly increases your chances of success by building in a self-correcting feedback loop. Secondly, involving them in your project builds confidence in your product and will greatly ease its acceptance in your target audience.

There are different types of stakeholders and each type should be handled differently:

Executive: Executive stakeholders are the guys who pay the bills. Typically they are managers or directors who are involved with commercial objectives for the project. They should restrict themselves to commercial considerations and be actively discouraged from being involved in technical design, their experience and skills are vastly different to that of ‘typical’ end-users.

End-user: These are the guys that are going to use your product.

Expert: Sometimes you need input from experts in other fields. People like graphic designers, support reps, sales or lawyers and accountants.




Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: