welcome to this session on the business vision document in this session we'll
discuss the various sections of the business vision document that need to be
created which include the goals the vision statement describing the personas
creating process diagrams and then finally we'll finish up by discussing
how the document should be validated so let's go ahead and get started the
vision document will be the first deliverable we create its main purpose
is to gather context and help us describe the business and validate our
understanding of it it's just like a vision document that is created for many
agile projects it'll consist of the vision statement the personas the top
user stories and a description of the business processes the main purpose of
the vision document is to provide an accurate understanding of the business
and the problem that needs to be solved to do this we need to understand the
context including the business strategy the business vision needs to align both
the tactical and strategic goals of the business a vision statement should be
inspirational but must also be actionable and have objectives in its
goal so here we can see an example outcome is the system that centralizes
service requests information requests and complaints to allow a seamless
communication with clients and flow control of operations sometimes not only
a vision statement but it can also be helpful to create what we call a vision
cloud along with that statement a vision cloud is a tool that can be helpful to
create the vision statement itself it's not mandatory but it's a good tool to
align the goals and assure the correct understanding of the business's
priorities to build a vision cloud just lists all the goals and priorities as
stated by the business stakeholders order them by importance using the
stakeholder feedback and then just the world a word cloud where each goal
size depends on its importance n build a vision statement making sure to point
out the most important goals so it may sound like the business vision is very
similar to a project initiation so what's the difference a business vision
is focused on the business goal and can be more long-term and broad in a project
initiation one of the goals is to prepare the iteration development which
is starting right away so project initiation is mostly project oriented
and business vision is mostly business oriented but in the business vision we
take the top-down approach and we're focused on a high-level overview we
don't want to get lost inside the details and we constantly will be
validating things with the business now to create personas we need to see the
users in action in person's analysis with the key users is very important
when we do this we need to register statistics and the contextual
information about each persona which are things like how many of each user are
they how often will they or do they use the current system and how proficient
are they with using technology we also need to understand the importance of
each persona toward the strategic goals and that takes us to process diagrams
process diagrams are a great form of visual communication they should be
created in a way that everyone can understand and discuss them this means
that part of the validation process is to make sure that the business users can
understand them for instance it may help to depict the personas together with the
activities where they intervene in the process also it can help to adapt the
process diagram to the use cases for instance if we have a call center
process we might represent it in two different views one represent how the
customer sees it and another one to represent how the back-office will
actually handle the case
process diagrams can also have different types of scopes and level of detail this
can depend on the target solution that we're trying to create for more specific
processes each of the activities may be a specific step but for a system
covering a broader process each activity may actually encompass a complex user
story make sure to cover the entire business process and not only what will
be covered by the application this way we'll have the full context to
understand how each activity is really related to the overall process finally
once the business vision document is done it needs to be fully validated with
the business each aspect of the document from the vision to the personas to the
processes should be understandable by each role of the business if needed
review the vision document and schedule additional analysis meetings and updates
to make sure that everything is fully understandable so that's it for this
session on the vision document thanks for watching and have a great day