Gerald Weinberg's Becoming A Technical Leader

1133 Words5 Pages

After studying both of these chapters, tell me in a written narrative how you personally would go about positioning yourself to be able to work effectively with both communities. What would be your strategy and how would you deal with the inevitable conflict that is bound to occur? The first problem that comes to my mind when considering how it will be like to work with the solution team is what Gerald Weinberg talks about in Becoming a Technical Leader. He calls it the "No Problem Syndrome"(NPS). Part of the issue with this is that programmers will most likely commit to any proposition you, as a BA, make. The problem is that they won't really try to fully comprehend all of the requirements made by the users. As a BA, the main problem with …show more content…

What are some areas that you would like to improve in to become more effective? When contemplating the issues that may arise, really think about how you would behave to achieve the outcomes that are necessary for success. Strength - The main strength I consider to have is that I like being as thorough as possible when gathering requirements. This will most likely help better manage expectations and provide in-depth requirements to the solutions team. Likewise, this trait helps me better estimate possible costs and have a more accurate timeframe, which would enable me to relate better with project managers. Area for improvement - Part of the expectation for any project, is what the end results will mean to the business. The issue is that sometimes I tend to generalize the outcomes instead of being specific. This might create false expectations, or the perception that no benefit is being provided by the final product because people might be looking for change in the wrong …show more content…

Blais) . Consequently, this may seem as overwhelming, but nevertheless it comes accompanied by benefits. Learning how to interact with everyone surrounding him should be one of the first things the BA should focus on. Since, they are in a position where it is possible to interact and exchange information with different segments of a company. Any changes that take place in the organization will have either the BA spearheading the initiative or at least involved to an extent. In these cases, the BA will most likely be a mediator and more often than not will facilitate different processes among diverse entities. Whenever problems arise, the BA will similarly be in the center of it all. He/she will pay attention to the concerns from everyone involved (business side, IT segment, and/or stakeholders). At that point, the BA will probably be the individual with the deepest knowledge of a problem or concern. As a result, the BA will act as a solution provider trying to work along with the solution team in order to craft a final product that most adequately fulfills the needs of the company. The center position can really put a lot of pressure in the BA, but also locates him in the position where he is able to serve various roles

More about Gerald Weinberg's Becoming A Technical Leader