It Architect

IT architects design IT solutions. They understand how to structure software to accomplish specific objectives. They understand the organization’s technology strategy and current environment. They are aware of upcoming technical initiatives that may impact business projects. They ensure that new applications will integrate with the existing infrastructure. IT architects should be involved with every project at its inception. They will review the high-level business objectives and requirements to determine how technology can best solve the business problem and assess the feasibility of solution alternatives. The PM, BA, and IT architect form the critical project planning trio.

Case in Point

One of our students related an experience which shows the critical role played by the IT architect. She had elicited business requirements from her business stakeholders using a structured process template that included metrics for the current process and desired metrics for the solution. She asked her stakeholders for their ideal performance requirements for a new Web application. Once her high-level business model was complete, she reviewed it with the IT architect to assess the feasibility of the solution. He immediately noticed the performance requirements and told her that a Web application could never deliver on those constraints. She was able to go back to the business stakeholders and help them rethink the project objectives, saving the project team hundreds of wasted hours.

It Developer

IT developers build IT solutions. They are the ultimate consumer of requirements and will be the people who make your solution vision a reality. To work effectively with IT developers, familiarize yourself with IT terminology and concepts (see Chapter 5). BAs who have an IT background will easily be able to converse and work with IT professionals. The one thing that you will notice is how quickly your technical skills become obsolete once you step out of that world. Things change very quickly in the development area. Don’t feel bad; your basic understanding of software and development will always be relevant.

IT professionals are people who are very interested in making/building things. They are similar to engineers, artists, and builders. They enjoy coming up with ideas for new products, and they enjoy seeing those products come to fruition. Some developers are more interested in building new products, while others enjoy fixing/improving old products. Some would rather design, while others would rather code. A few rare individuals enjoy doing both. As a BA, it will be helpful to you if you get to know your IT people individually and understand their individual interests. The better you understand these technical stakeholders, the easier it will be for you to explain the business needs and work with them to design effective solutions.

Some developers will want to understand the business reasons for the products that they are building. These individuals may eventually choose to become BAs themselves. If you find yourself working with a developer who is frustrated working in a technical requirements vacuum, include that person in SME meetings if possible. You can really look at this developer as a BA-in-training and you can mentor him or her on communicating with the SMEs. Don’t feel threatened by this direct communication between the SME and development team. The role of the BA was invented because some developers don’t communicate well with business people, but don’t assume that all IT people are poor communicators. As with all human beings, get to know people individually and work with each in the way that they will be most comfortable.