Business requirements gathering and writing works best when the business analyst doesn’t throw the requirements over the cubicle wall to IT!  Using collaborative requirements gathering sessions for scoping, high level requirements and detailed requirements should be conducted.  If you involve the technical team in the detailed requirements sessions, you will have less churn and less chaos.  Below is a description of the focus group sessions the Business Analyst can conduct:

• The first step would be to review the requirements use cases from the requirements sessions previously conducted.
• Once you have reviewed the high level requirements, you are ready to identify how the system will work with the SMEs, and Technical Leads.  Using the requirements use cases, develop the detailed steps of the flows on the use cases.  Using a ping-pong method, identify what the user will do and what the system response should be and document.  The Business Analyst can use an Activity Diagram with swimlanes technique to help identify the detailed steps in the use case.
• While you are identifying the detailed steps, you can also note where you have screens and reference them on the use case.  The Business Analyst should lead the Subject Matter Experts (SMEs) and the Technical Team in a brainstorming session using the storyboarding technique to collaboratively build screen mock-ups.
• The Business Analyst should then further define the screen specifications by capturing the details of the data fields on the screens with the team. 

A good article that supports the importance of collaborative detailed requirements sessions as described above is as follows:  http://advice.cio.com/jim_vaughan/10442/project_managers_need_to_engage_it_at_the_right_time

The term outsourcing has become on that people feel negatively about. However as a business owner the concept is hugely profitable and helps the global economy.

Simply put the idea is that you can put some of your call centers and the like in countries where labor is cheaper than it is here in the states. The families able to procure employment from American businesses in poorer areas are able to make far and away more than what other families in the area are. By providing jobs you are truly changing the face of people who have been impoverished for as long as most can remember.

The Pierson Website explains:

Pierson Requirements Group, Inc. has divided the services into three phases of tasks. The phases are preparation, workshop and follow-up.

During the Preparation Phase, Pierson Requirements Group, Inc. will include the following activities:

• Interviews and orientations of key stakeholders (SMEs) from each business unit to review and uncover seed material and identify project issues for the session
• Teleconference and on-site interviews to review the current documentation practices and templates used for business requirements
• Review of sample documents for a similar project
• Planning the session logistics, deliverables and agenda with the project team
• JAD Facilitator and JAD Documenter prepare the JAD Documentation to be used in the session

Contact Pierson Requirement Group for a full and complete explaination and the steps toward making this type of situation a reality.

Starting a business of any kind can be a very different experience depending on the amount of help you get and how muc experience that help has. With the current economy it is difficult to strike out on your own, but the consultants and methodology used by Pierson Requirements Group can really help you understand what you are getting into and the best steps to take toward success.

They use Joint Application Development or JAD. This is a technique used for gathering business software requirements. The purpose of JAD is to bring together the technical/creative team and the business community in a structured workshop setting to extract consensus based software requirements. This is accomplished by using a trained JAD facilitator and customized, planned agendas to assist the participants in arriving at complete, high quality requirements.

Another method employeed frequently by Pierson Requirements Group is Rapid Application Development or RAD which is a process that speeds the delivery of functionality to end-users by segmenting software into pieces for delivery rather than delivering all of the software functionality in one large implementation. It is an iterative process utilizing a spiral methodology and is also customer driven following an evolutionary process using continuous application engineering in a time-boxed fashion with a dedicated professional team. The goal of the iterative approach is to reduce the time between requests and delivery of Business Application Software.

Pierson Requirements group can take some of the sting and frustration generally associated with the start of a company out of the equation. Contact their offices for more information.

Having a person on staff with the training to be able to identify any issue and point out all opportunities for growth in your company is an invauable asset. However, most companies, especially smaller companies looking to grow, do not have the resources to make such a position available full time. Instead they find it prudent and economical to hire a business analysis company to do these things for them.

Pierson Requirements Group offers a multitude of ways to do just that. This company will assess every single area of your business and find out if there are any gaping holes or even small leaks so that any problem is found and corrected as soon as possible. This may mean hiring more staff, letting some go, re organizing who does what and almost always involves more focused training.

Trusting a company like Pierson to have your best intrests in mind is the key to a good working relationship, Pierson will answer any questions you or your staff may have before, during, and after your analysis begins. Find out if the methodology used by Pierson is something your company can benefit from by contacting them today

Some of the companies that have taken advantage of Pierson’s experience are:

Nationwide - “Pierson provided the 4-day Requirements Gathering & Writing Training Seminar using JAD, Use Cases and UML. The Business Analysts, Project Managers and Quality Assurance Testers were trained. Also conducted was the User Acceptance Testing Training Seminar for the Testing staff.”

Prudential - “Pierson trained over 40 Project Managers, Technical Leads and DBAs in JAD Facilitation & Requirements Gathering using Data Techniques.”

Business Analyst Training is a way of targeting learning for exactly what your employees need. Pierson Requirements Group is a company who will provide business analysis training courses either on or off site to aid you in making your company as effective as possible. In order to take your business’ services to the next level you have to pinpoint your weaknesses and then create training classes and software to strengthen those areas.

Their Joint Application Development (JAD) which is used as a way to bring together the teams your company uses to design technical and creative aspects and the realities of the business world to create a round-table type discussion forum workshop to find out exactly what is needed in your field and make sure that your software is going to cater to those needs. This process saves time and money that is valuable during the upstart of any business.

They aim to cover every area of:

• project management
• business analysis
• system specification
• and more

Trusting a company like Pierson to have your best intrests in mind is the key to a good working relationship, Pierson will answer any questions you or your staff may have before, during, and after your analysis begins. Find out if the methodology used by Pierson is something your company can benefit from by contacting them today.

The Pierson Requirements Group has been a consulting and training company since 1990 and they’ve helped many businesses realize their potential by using practices to uniquely steer your company down the road to success. Their business analysts can help you take your idea from inception to full fruition in a clear and concisely planned way which will aide the smooth running of your ship.

1. Hallmark
2. Experian
3. Dell Professional Services
4. The US Department of Energy
5. the list goes on!

Detailed Use Case

Quality Assurance Checklist

Use Case Name:                    Verb/noun 

Use Case Number:                Follow current standards? (i.e. references to related systems) 

Iteration:                                Is iteration level noted? 

Description:                            Does the description:

1.      Begin with “the purpose of this use case is…”

2.      Clearly state the value provided to the actor

3.      Clearly state the purpose/goal of the use case                                 

Generic Scenario:                  The generic course of events should:                 

1.      Clearly state how the use case starts and ends (i.e. this use case starts when and ends when)

2.      Be written in the appropriate perspective (system perspective)

3.      Have a minimum of 3 steps identified

4.      Be consistent with description and within the scope of the description

5.      Use the active voice to describe the end user or system interface performing the steps

6.      Document the system solution, using ping pong, to identify the system interface responses clearly

7.      Identify links to other use cases, by underlining the use case name and reference the use case number

8.      Not document GUI but instead attach a prototype or an activity diagram

9.      Have no more than 9 or so steps

10.  Provide a step by step flow of events from the actor’s perspective.

Actors:                                    Are the correct actors identified?

1.      Are the users and/or systems that communicate with the solution identified?

2.      Are the actors a person or system other than the support system under development?

3.      Are the actors identified only involved in this use case? 

Alternate Scenario:                Are the alternate paths identified correctly?

1.      Is the path intentional by the actor and within the actor’s control?

2.      Does the title of the alternate describe the alternate path and tell why it is an alternate.

3.      Is the alternate using the appropriate numbering scheme and is referenced in the basic course of events section? (A1)

4.      Does the alternate successfully complete the use case?

Exceptions:                             Are the system exceptions identified?

1.      Do the exceptions result in a different outcome of the use case?

2.      Is the exception unintentional, an anticipated failure that needs a recovery plan?

3.      Is the exception using the appropriate numbering scheme (E1) and is referenced in the basic course of events section?

Trigger:                                 

1.      Is the event that causes the use case to occur present?

2.      Is the active voice used?

3.      Is the trigger a business event, not a system event? 

Assumptions:

1.      Is the item outside the control of development (including the out of scope) AND must be in place before the use case can run? 

Preconditions:                       

1.      Ensure the precondition is not the first step of the basic course of events.

2.      Is the item inside the control of development and in place prior to the execution of the use case?   

Post conditions:

1.      Ensure post condition is not the last step of the basic course of events.

2.      Does the post condition declare the state after the use case execution?  

Related Business Rules:

1.      Are the business rules specific to this use case?

2.      Is it a business related rule rather than a system rule?

3.      Should be written as a declarative statement

Issues:                                               

Should be NONE

Business Analysts are responsible for facilitating requirements analysis, requirements validation and business process improvement.  Below are some qualities and traits of a good Requirements Lead and Business Process Improvement Facilitator that a Business Analyst should develop to be effective.

·        Communicates well

·        Processes ideas from people

·        Shows a natural interest

·        Listens well

·        Maintains control

·        Empowers the group

·        Handles uncertainty

·        Is quick to connect with the group

·        Focuses on the business not their own solutions

·        Communication skills

§         Negotiating

§         Group dynamics

§         Listen/draw conclusions

·        Business Savvy

§         Running meetings

§         Systems Analysis & Design

§         Relates well to people

·        Management skills

§         Project Management

§         Manages people’s expectations

·        Reputation

·        Impartial

·        Devoted to the process

§         Understands and constantly sells the process

Pierson Requirements Group provides training in effectively leading requirements and business process improvement initiatives.  Some popular classes for improving the Business Analyst facilitation skills are the Business Requirements Gathering & Writing Seminar using JAD, Use Cases and UML Techniques and the Business Process Management Facilitation.   

To learn more about training that is available for these collaborative techniques and methodologies click on Pierson’s Requirements Group’s agendas for JAD Facilitation & Requirements Gathering using Use Cases and Business Requirements Gathering & Writing Seminars.

3 Step Method

This is a good technique for identifying risks and issues.  Use this technique for the beginning of the session.

1.                 Individual- Write ideas and thoughts on flip chart paper/whiteboard.  Be creative and draw pictures.

2.                 Small Group- Break up into groups of 3 – 5 people.  Each person in the group should present their results.  As you listen to the presentation note the common themes.  Each group creates a consolidated group list.  Each group presents their results and gets feedback from the larger group.

3.                 Large Group- Facilitator leads the group and consolidates decisions from each group getting consensus for the final lists.

Implementation of the process change

Prepare an Implementation Plan-

·          Recommend a specific course of action

·          Identify the potential problems and risks

Measure the success

Identify how you would measure the success of the new business state (new process).  What mechanisms would you put in place to monitor the success? (Follow-up with customer, questionnaires, etc.)  How will you ensure the performance measurements were “fit for the purpose’? (Use the business intent)

Monitoring the performance and effectiveness

What is the effectiveness of the new systems or procedures through the appropriate control mechanisms?  Identify the procedures to a standard sufficient to achieve the defined objectives by routine checks, and corrective action.