The Real Voyage of Discovery Lies not in Seeking New Landscapes, But in Having New Eyes – Marcel Proust
Monday, 14 July 2008
Mamma Mia ! Dancing Queen ! :)
Saturday, 12 July 2008
Business Analyst Job Description Template
The following job description may be tailored for use by a Business Analyst without any people management responsibilities:
Business Analyst Role Description:
1:To develop a sound knowledge of
2: To liaise with business managers and low-level users to understand and document business requirements across affected business areas.
3: To understand, document and prioritise business requirements across affected business areas.
4: To work with business owners and delivery workstreams to develop optimal solutions.
5: To develop complete and accurate business models including process, data and organisation.
Business Analyst Working Relationships:
Work with project sponsor to understand and document project objectives and scope.
1: Work with business owners from affected business areas to understand current processes and to document and prioritise requirements.
2: Work with delivery workstreams to communicate business objectives and requirements, make decisions on delivery options and produce delivery costs and timescales.
3: Work with
4: Work with project manager/s to plan analysis work and highlight risks and issues.
5: Work with Finance to define accurate, meaningful and measurable business cases.
6: Work with the business owners to define acceptance criteria.
Business Analyst Deliverables:
1: Project initiation documents defining high-level scope.
2: Business requirements document describing the project's objectives, how the work was done and listing the requirements for each business area prioritised into mandatory, desirable and optional categories. Desirable and Optional requirements will have an associated business case which will allow the project sponsor to make informed decisions about delivery of the project.
Detailed requirements that enable the chosen solution to be developed and tested with minimal analysis support.
3: Business cases defining the costs and benefits associated with requested changes.
4: User Acceptance test plans.
5: Business models incorporating process and data models.
Business Analyst Reporting:
Weekly reports will be produced for the project manager showing progress against outstanding milestones, status, resource requirements, issues, risks and dependencies.
Business Analyst
Business Analysis is the process of understanding business change needs, assessing the impact of those changes, capturing, analysing and documenting requirements and then supporting the communication and delivery of those requirements with relevant parties.
Who is a Business Analyst?
"Today's Business Analyst may reside within any part of an organisation and this has a direct effect on the way they work and the deliverables they produce"
"Business Analysis is the process of understanding business change needs, assessing the impact of those changes, capturing, analysing and documenting requirements and then supporting the communication and delivery of those requirements with relevant parties."
A Bit of History: Requiring straightforward automation of repetitive administrative tasks and conversion from paper to electronic data storage, IT projects of the seventies and early eighties could not fail to be successful and reap financial rewards.
Systems Analysts took responsibility for documenting existing manual paper based processes, identifying problems and new business requirements, and then automating these processes through computerised systems. This provided significant savings in staff as well as improvements to customer service through access to electronic information in fractions of a second.
Throughout the late 1980's and 1990's, companies started to evolve their IT systems to take advantage of new technology as they attempted to make further savings or improvements in service. However, IT projects in this era continually failed. They either failed to deliver at all, or were delivered without providing any significant business benefits.
The reasons for failure were that projects became unfocussed, receiving (sometimes conflicting) demands from different business departments. Systems were developed with unrealistic business cases, without clear objectives, with unmanaged expectations of performance or merely to follow the 'emperors new clothes syndrome' of jumping on the latest technology bandwagon.
Business users became increasingly frustrated with the barriers that limit their ability to implement change promptly and effectively. As PC and server technology evolved, business users became wise to IT and started to purchase and build their own localised systems. This has left many companies in a position where as well as their existing 'legacy' systems, they have hundreds of different systems which often link in an uncontrolled fashion with no real documentation to explain the links.
The Business Analyst has Evolved:
Throughout this period, the role of the Systems Analyst evolved into the Business Analyst. This role encompasses more than the ability to document processes and apply technological expertise.
While the Systems Analyst belonged to the IT department, Business Analysts can now be found within a number of places in organisation structures:
1: Within the IT department acting as a conduit to and from the business
2: Within individual business units with responsibility for identifying business needs
3: Within a change management department coordinating and managing change across the whole business.
But wherever they sit, Business Analysts must be great communicators, tactful diplomats, problem solvers, thinkers and analysers - with the ability to understand and respond to user needs in rapidly changing business environments.
We define the purpose of the role of the Business Analyst as being ultimately responsible for ensuring that organisations get the most from their limited IT and change management resource.
Business Analysts are responsible for identifying change needs, assessing the impact of the change, capturing and documenting requirements and then ensuring that those requirements are delivered by IT whilst supporting the business through the implementation process. Business Analysts should not just write specifications and then leave them to be delivered. The development lifecycle is an iterative one and the Business Analyst must be involved from initial concept through to final implementation.
Business Analysts are likely to be the key change facilitators within your organisation. They must deliver effective solutions which provide tangible business benefits usually within short timescales.