At work, from time to time, there will be an e -mail wandering asking about what it requires to define a specific role, in our company. Here in ThinkWorks, this question extends to what this role also means in projects. Everything is good and specific for developers, architects and project managers alike, but what about Analysts? We were recently asked to provide a definition of this role, when someone wants to join Two as a business analyst. What do we say in response to the question, “What does an analyst at Thoughtworks do?”

How do I describe what I do? I know that I can discover one when I interview one, but how do I tell others what are the definitions or criteria you use? There is no specific clear way to distinguish what is “Ba”. There is no rule or accurate formula. Each is different. It is the art of more than the result of the false scientific definition … but this is the sermon:

Listen skills. There are many roles and personalities in the TW Tw’s Twarian team that provides advice / opinion / comments in the drop of the hat, so the analyst sometimes needs to follow a complete reverse approach, retreat, and listen to what customers say. This, as well as Be good notes (In itself with a large cheap) that would help in obtaining a huge amount of information during the project, from the start of the start, to delivery and delivery. People laugh when they hear the comment, “BAS should be good applicants”, and they thought this is a sound that everyone can do well; In fact, it is not so simple. Ask any member of the team about the teams that will make it if he is at the recipient of a good set of notes in exchange for badly written scribbling. Then ask one of the team members on a distributor project what the difference will happen to them.

Understanding and appreciating technology, without having technical knowledge As a pre -condition. Bas here to help find ways to solve a problem, here to suggest and present the educated judgment based on their previous experience and what their analytical minds tell them. We need them to participate in discovering what they can achieve with customers, and helping to appoint the way for them. BAS in principle is not present to tell you how easy or difficult to implement this feature in this way or another. We have our wonderful developers and technical leadership for that.

Ask whyAnd ask again. Are they naturally curious people? Do they take information in its nominal value, without questioning the reason that things are the same now? We want to not be the matter of the applicants. Imho is a path that destroys the soul anywhere and reduces your entire presence in the project.

Last and not another, the presence Raw skills from being naturally comfortable in any field. We do not want to employ analysts who can only prosper in one area, and we want to stick to only one sector. In particular in TW projects, for practical reasons, analysts are to be adaptable to the largest possible number of fields. From investment banks to commercial floors, and media publishing companies to fashion houses, they must be as a barrier that threatens the bachelor’s event.

Stop reading now if you think the role of Agile business analyst begins and ends in writing stories.

In short, business analyst Agile is not the same as a systems analyst, systems development analyst, and a technical analyst, and is still different from the business analyst that you find in traditional thinking to develop software. But of course there is more than just a name and address. As with this post in this blog, it is just the beginning. Meanwhile, what do you think of a graceful business analyst?

About Jenny Wong

At work, from time to time, there will be an e -mail wandering asking about what it requires to define a specific role, in our company. Here in ThinkWorks, this question extends to what this role also means in projects. Everything is good and specific for developers, architects and project managers alike, but what about Analysts? We were recently asked to provide a definition of this role, when someone wants to join Two as a business analyst. What do we say in response to the question, “What does an analyst at Thoughtworks do?”

How do I describe what I do? I know that I can discover one when I interview one, but how do I tell others what are the definitions or criteria you use? There is no specific clear way to distinguish what is “Ba”. There is no rule or accurate formula. Each is different. It is the art of more than the result of the false scientific definition … but this is the sermon:

Listen skills. There are many roles and personalities in the TW Tw’s Twarian team that provides advice / opinion / comments in the drop of the hat, so the analyst sometimes needs to follow a complete reverse approach, retreat, and listen to what customers say. This, as well as Be good notes (In itself with a large cheap) that would help in obtaining a huge amount of information during the project, from the start of the start, to delivery and delivery. People laugh when they hear the comment, “BAS should be good applicants”, and they thought this is a sound that everyone can do well; In fact, it is not so simple. Ask any member of the team about the teams that will make it if he is at the recipient of a good set of notes in exchange for badly written scribbling. Then ask one of the team members on a distributor project what the difference will happen to them.

Understanding and appreciating technology, without having technical knowledge As a pre -condition. Bas here to help find ways to solve a problem, here to suggest and present the educated judgment based on their previous experience and what their analytical minds tell them. We need them to participate in discovering what they can achieve with customers, and helping to appoint the way for them. BAS in principle is not present to tell you how easy or difficult to implement this feature in this way or another. We have our wonderful developers and technical leadership for that.

Ask whyAnd ask again. Are they naturally curious people? Do they take information in its nominal value, without questioning the reason that things are the same now? We want to not be the matter of the applicants. Imho is a path that destroys the soul anywhere and reduces your entire presence in the project.

Last and not another, the presence Raw skills from being naturally comfortable in any field. We do not want to employ analysts who can only prosper in one area, and we want to stick to only one sector. In particular in TW projects, for practical reasons, analysts are to be adaptable to the largest possible number of fields. From investment banks to commercial floors, and media publishing companies to fashion houses, they must be as a barrier that threatens the bachelor’s event.

Stop reading now if you think the role of Agile business analyst begins and ends in writing stories.

In short, business analyst Agile is not the same as a systems analyst, systems development analyst, and a technical analyst, and is still different from the business analyst that you find in traditional thinking to develop software. But of course there is more than just a name and address. As with this post in this blog, it is just the beginning. Meanwhile, what do you think of a graceful business analyst?

About Jenny Wong