Project
Blastoff:
· The key purpose of the project blastoff
is to build the foundation for the requirements discovery that is to follow,
and to ensure that all the needed components for a successful project are in
place
· Defines the scope of the business
problem
· Confirms the goals of the project
Trawling for
Requirements:
· Means discovering the requirements
· Uncovering the essence of the system
· Decide the best product to improve
this work
Writing the requirements:
· Major problem in system development
are misunderstood requirements
· Ensure that parties at either end of
the development spectrum
· Ensure that the essence of the requirement has been captured and communicated and that the delivered product can
be tested
Quality Gateway:
· To ensure correctness, the quality
gateway tests the requirements
· Check each requirement for completeness,
relevance, testability, coherency, traceability, and several other qualities
Reusing Requirements:
· Can reuse dozens of requirements without
alternation
· Can start with a specification from
one of the previous projects and use it as a checklist
Reviewing
Requirements:
· This final review checks that there
are no missing requirements
· Confirms that the specification is
really complete and suitable
· Offers an opportunity to reassess the
costs and risks of the project
· Have a much more precise knowledge of
the scope and functionality of the product
· Estimate the cost to construct the
product
Iterative and
Incremental Processes:
Requirements
Retrospective:
· Can be very formal
· Publishes a retrospective report
Evolution of
Requirements:
· Deploy models of varying degrees of a formality to help them
· Learn what the work is, and what it
is to be
· Helps enormously when coming to an
understanding of the work
· Specify what the product has to do
for the work
The Template:
· Is designed to serve as a sophisticated
checklist
· Here is the content:
o
Project
Drivers: reasons and motivators for the project
o
Project
Constraints: the restrictions on the project and the product
o
Functional
Requirements: the functionality of the product
o
Non-functional
Requirements: the product’s qualities
o
Project
issues: issues relevant to the project that builds the product
The Snow
Card:
Formality Guide:
· Rabbit: small, fast and short-lived
o
Rabbit
projects are usually iterative
o
Do
not spend a great deal of time writing the requirements
o
Always
co-locate the business knowledge stakeholders with the business analysts and
the developers
· Horse: fast, strong and dependable
o
Most
common corporate projects
o
Need
some formality
o
Have
medium longevity and involve more than a dozen stakeholders
· Elephant: solid, strong, long life
and a long memory
o
Need
for a complete requirements specification
o
Have
a long duration
o
A
large numbers of developers, necessitating more formal ways of communicating
Implementation of the new CRM tool will be a critical decision which has the potential to improve the company processes upto a great extent. The project will be a horse sized project with maximum of 1 year implementation time. The blastoff for this project shall set the foundation which will essentially list out what all processes are we aiming to improve, which includes the teller process, the advising process and the way we interact with our clients. Having open conversations with the teams will help in identifying the non-functional requirements of the project.
ReplyDeleteAs we are implementing a new CRM tool in our company IG Wealth Management, so it will help us to improve our relation between customers. Before implementing our tool, we should decide the project blastoff. As this is a horse sized project and more than dozen stakeholders would be involved. We have to take care of their needs and requirements.Moreover, we also have to have an eye on the risks and constraints. The basic improvements with this project will be reduction in cost, improvement in products, services and performance.
ReplyDeleteImplementing CRM tool in IG wealth management helps to make the work easy and effective. On some search, i came to know that it is a horse size project. it is fast to use and has cloud storage.It has many stakeholders and it needs proper documentation before implementation so that it would be successful.
ReplyDelete