Build your Credibility
A Business Analyst acts as a face of Customer to the Development team, most of the time. A Business Analyst should be credible enough and the team should have absolute faith in him. Development team should be able to ask any question regarding the system and they should believe in the answers that BAs provide. If they start having doubts on the answers BAs provide they may get tempted to develop something that is not needed by the business or spend extra time in clarifying the doubt from various sources.
Advance From Business Analyst to Business Architect
The wilderness between IT and business is our realm. We wrestle semantics and drive out definitions. We begin as Analysts and advance to Architects.
We’re not strictly tech and we’re not strictly business. The definition of what we do is usually written in semi-tech language (we write requirements). But how do we write those requirements, what makes us different? How do we see things and why do we see them in the way that we do? What is the potential of the Business Analyst profession? What do senior managers want that causes them to listen to us? How do we move from Business Analyst to Business Architect? How do we advance ourselves in our positions and advance the profession as a whole?
Customer Rights and Responsibilities
Software success depends on developing a collaborative partnership between software developers and their customers. Too often, though, the customer-developer relationship becomes strained or even adversarial. Problems arise partly because people don’t share a clear understanding of what requirements are and who the customers are. To clarify key aspects of the customer-developer partnership, I propose a Requirements Bill of Rights for software customers and a corresponding customer’s Requirements Bill of Responsibilities. And, because it’s impossible to identify every requirement early in a project, the commonly used—and sometimes abused—practice of requirements sign-off bears further examination.
Building a Requirements Foundation through Customer Interviews
“Our customer doesn’t know what he wants,” complained Sandy. “I try to get him to talk about the product and tell me what he wants, but it’s like pulling teeth.”
Whether you are building a brand new product or working on evolving an existing product, understanding customer business needs is the foundation of a marketable product. But few of us are experts in interviewing techniques, and few customers talk about their tasks, needs, and context in neat, concise statements about product requirements.
Navigation
Last articles
- Six Sigma and the Business Analyst
I began my career at Cap Gemini Ernst & Young where doing business analysis and implementing large scale systems was my job - The Rise of the Business Analyst — Again
When I got into the IT business years ago, I thought the business analyst was the most pivotal person in the whole profession. - Maintaining and Keeping Your Edge: 5 Tips to Landing a Job
In 2001 I found myself “in-transition”. A year prior I had accepted a position with a small Internet start-up firm in New Jersey - Objectives of management: mastering complexity
Do you feel that your work as a manager is getting more and more complicated? You are almost certainly right. - The Evolving Role of the Business Analyst
Video material
Newsletter
About
Be always abreast of developments in the business world with us. Our blog - the best information base for analysis and business plans. Every day we publish new and interesting articles for beginners and for those businessmen who have their business for many years. Subscribe to our newsletter and be always in touch with us.
Business analysis
Business analysis is the discipline of identifying business needs and determining solutions to business problems. Solutions often include a systems development component, but may also consist of process improvement, organizational change or strategic planning and policy development. The person who carries out this task is called a business analyst or BA. (info from wikipedia)