When
you are working on a project to make or better a system to help
people at your college or workplace to find jobs, then the system
should be made for the student and work for the population and
should be simple so people can work their way around it. You can
use these following techniques.
- Interviewing is a good way to have face to face
and more interactive ways to communicate with your colleagues and
clients. Unlike the next one which is a survey, this can be more
personal and you'll get better answers than a computer program
could.
- Surveys are a great way to collect data and get
people's opinions! It is also faster and more efficient if you're
on a tight schedule.
- Document analysis is the last one to mention here.
You can see how an already existing system is working and make a
study based on that.
Five
requirements in a traceability matrix that I would use are the
following:
- Plan meetings with stakeholders who may want to
work with your system development because they'll be the first ones
that are upfront and into the project.
- Make more meetings and surveys to help people who
are using your system do its purpose of finding people jobs at the
workplace and college.
- Study your system to make sure it works and then
do an analysis
- Make sure you do effective system documentation
preparation and make sure to also have nice and helpful guides and
other things that can help you and your system
development.
- Have a team of Business Analysis visits
stakeholders who will show them the ropes of the business
requirements and how the system is being made and what design is
going to be put out of the system.
Managing a project includes identifying your
project’s requirements and writing down what everyone needs from
the project. What are the objectives of your project? When everyone
understands the goal, it’s much easier to keep them all on the
right path. Make sure you set goals that everyone agrees on to
avoid team conflicts later on. Understanding and addressing the
needs of everyone affected by the project means the end result of
your project is far more likely to satisfy your stakeholders. Last
but not least, as a project manager, you will also be balancing the
many competing project constraints.
On any
project, you will have a number of project constraints that are
competing for your attention. They are cost, scope, quality, risk,
resources, and time.
- Cost is the budget approved for the project including
all necessary expenses needed to deliver the project. Within
organizations, project managers have to balance between not running
out of money and not underspending because many projects receive
funds or grants that have contract clauses with a “use it or lose
it” approach to project funds. Poorly executed budget plans can
result in a last-minute rush to spend the allocated funds. For
virtually all projects, the cost is ultimately a limiting
constraint; few projects can go over budget without eventually
requiring corrective action.
- Scope is what the project is trying to achieve. It
entails all the work involved in delivering the project outcomes
and the processes used to produce them. It is the reason and the
purpose of the project.
- Quality is a combination of the standards and criteria to
which the project’s products must be delivered for them to perform
effectively. The product must perform to provide the functionality
expected, solve the identified problem, and deliver the benefit and
value expected. It must also meet other performance requirements,
or service levels, such as availability, reliability, and
maintainability, and have acceptable finish and polish. Quality on
a project is controlled through quality assurance (QA), which is
the process of evaluating overall project performance on a regular
basis to provide confidence that the project will satisfy the
relevant quality standards.
- Risk is defined by potential external events that will
have a negative impact on your project if they occur. Risk refers
to the combination of the probability the event will occur and the
impact on the project if the event occurs. If the combination of
the probability of the occurrence and the impact on the project is
too high, you should identify the potential event as a risk and put
a proactive plan in place to manage the risk.
- Resources are required to carry out the project tasks. They
can be people, equipment, facilities, funding, or anything else
capable of definition (usually other than labor) required for the
completion of project activity.
- Time is defined as the time to complete the project.
Time is often the most frequent project oversight in developing
projects. This is reflected in missed deadlines and incomplete
deliverables. Proper control of the schedule requires the careful
identification of tasks to be performed and accurate estimations of
their durations, the sequence in which they are going to be done,
and how people and other resources are to be allocated. Any
schedule should take into account vacations and
holidays.