Dmonstration is a good way to show proposed solution, progress update, or even business process, Demonstration can be done by delivering a similar product, prototype, or proposed software. This article will discuss how to prepare demonstration for your customer. This is five steps to create great demonstration.
Ask yourself, what vision that you want to share to the customer. Showing your product that already fulfill the business process, pretending the current solution for a specific business process. you need to know what your demo purposes
Preparing demo script or drill down agenda. Write some notes what you want to show to them
Reproduce your demo, based on your script do your demo and finds some bugs or flaws
Refine your demo based on the bugs or flaws that you find
Prepare the demo infrastructure before the date. do your best
medianet_width = "600";
medianet_height = "250";
medianet_crid = "858385152";
medianet_versionId = "3111299";
Proposal is the first important things that we should prepare to bind between customer and our team. Comprehensive proposal will clarify any vision, mission, and solution that we need to provide to the customer. On this post, we will show you four steps to create proposal.
Collaborate with the Team
Proposal is a document that is created by the entire team. Not only, business analyst but also other team members such as project manager, coach, or even customer. The team should contribute for the proposal. on this step, we should provide
Proposal template
data and log book from the meeting notes
proposed solution and basic knowledge about the solution and problem
Create a draft document
Creating a draft of document is an essential steps for business analyst. In order to do that you should consider several things that you need to include in your proposal which are:
//
Customer business need
Customer Vision on the need
Proposed Solution
Project Roadmap (Iteration and release)
Project management. it includes communication plan, changes management, and conflict resolution procedure
Project organization
Project budget
Project assumption. Things that need to consider the successful of the project.
Get a feedback from customer
Send your first draft to the customer and get a feedback from them. By obtaining a feedback you will:
Revise your proposal. it includes scope, resources, budget, etc.
Request additional meeting to clarify the feedback
Align the capability of the team with the proposal
Creating a SOW
Statement of work (SOW) is the end of the commitment between customer and the team. SOW will be emailed to the customer and agreed with the both parties.
//
Today, I am having goo d conversation with some people that has a background as business analyst. This post will tell you about three things that business analyst needs to be done when meeting the client.
medianet_width = "600";
medianet_height = "250";
medianet_crid = "858385152";
medianet_versionId = "3111299";
Before meeting
Having a knowledge is a mandatory activity. Here are some tips for you.
Understanding the basic business process of your customer. Learning from their website, tasting their product, and joining their presentation will give you the idea of their business process.
Finding their basic problem from the existing business process. You can do a short call with the customer, plan a conference call
Finding their existing solution to face problem (if there are exist)
Looking for the similar solution from the others. It will be good to do a short review about the existing product.
Creating a list of potential questions to understand more their problem.
On the meeting
We will divide it into three meeting classes
First Meeting
Hearing the customer. On the first meeting your mission is to get a
Shared vision between you and your potential customer
Listening the key problems and hopes from your customer.
Listening their constraint. Budget, Place, and Resources constraint you should know
Understanding their current solution.
Second Meeting
Proposing a solution. On the second meeting your mission is to
Proposing your solution idea.
Hearing their feedback about their idea
Comparing your solution with the existing solution
Third Meeting
Finalizing the contract. On the third meeting your mission is to
Refining your solution based on their feedback
Telling a good story about your proposed solution
Grabbing their concern and budget.
After meeting
The third meeting series are finished, your mission is to
Documenting their business model. This is optional step, if you create a product that become their main income. For example, an e commerce site for a commerce customer. If you build a backend information system you can't skip this action.
Documenting their business process. You can use UML, narration, or Business Process Modelling notation.
Documenting their information architecture. You can use sitemap, storyboard, or even wireframe to give them an explanation how the solution will be.
medianet_width = "600";
medianet_height = "250";
medianet_crid = "858385152";
medianet_versionId = "3111299";
On this Indonesian video, we show you to understand what requirement engineering in a software product. And how to make sure you can build better software by applying requirement engineering. This video describes 5 things do and dont in requirement engineering.
//