Loading presentation...

Present Remotely

Send the link below via email or IM


Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.


Project Development

Projects are the planning, designing and production of solutions to problems.

David Fenwick

on 26 May 2010

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Project Development

Analyse the problem Evaluate the solution Produce the solution Design the solution Define the problem MANAGING AND DEVELOPING PROJECTS Methods of analysis
Top-down analysis or refinement breaks a problem into parts. This may require a
number of steps - called a hierarchy - in which each step down is less important than the step above it. Refinement is a common technique as it makes solving problems easier. The smaller parts can be solved separately and then combined to solve the whole problem. Bottom-up analysis is also used to solve some problems. This will occur when the project has a number of parts that need to be constructed into a whole. For example, information on many different types of hardware or physical devices could be collected separately. Once the concept of networking has been thoroughly researched, the hardware could then be sorted and those devices useful in networking separated out and then combined into the project. Projects and project work are an
important part of the information
and communication technology
(ICT) industry. Projects usually
require a team of people who work
together to develop solutions. I Use problem-solving techniques to develop possible solutions
Select and plan the best solution to the problem Construct the solution from the document design Check that the solution solves the problem and meets the user's requirements
When a project is initiated, it is important to identify clearly the problem to be solved. This requires information that can be collected from:

· documentation about an existing system, such as technical documents or evaluation forms

· the client or end user through interviews, observations and questionnaires

· a design brief or problem statement.

Identifying the problem Documentation of a problem is
an in-depth description of the
problem and what needs to be
solved. It can include the
objectives, goals, scope and needs
of the problem. This
documentation could be in the
form of a design brief, problem
statement, feasibility report or
needs analysis. At this point, you
could also develop criteria to use
later when evaluating the
completed solution.
The documenting process
often helps you to clarify the
problem. It also supports better
communication between the
developer and the client and end
user. Feedback from the client or
end user can stimulate further
refinements to the project
manager's understanding of the
identified problem. Documenting the problem

A detailed investigation involving the following activities.
1. Collecting data about the problem, such as:
· reviewing existing documentation about the current system or problem
· using interviews, questionnaires or surveys to determine the client's or end users' needs and requirements
· identifying the factors that may affect the solution.
Questions that could be used to help identify and pinpoint the problem include:
1. Is there a design brief or problem statement that outlines what is needed?
2. What information is there about the identified problem?
3. Is there any existing documentation of the problem or need?
4. Is there an idea which can be exploited?
5. Is there an opportunity?
6. Is there a task that needs to be created?
7. Who is the solution for?
8. Is there a client?
9. Is there an identified end user or a target audience?
10. Who can provide information and feedback about the problem? 2. Analysing the problem and its requirements, such as:
· developing a good understanding of the problem to be solved and the existing systems
· collating data about the problem
· determining the limitations and constraints of the solution
· analysing possible alternative solutions
· documenting the problem to be solved. Problem solving
Asking questions
Who, What, When, Where, Why, How?
Finding answers


Attention to Detail
Check errors

Honour & Excellence
What does the school motto mean to you?
Are you applying the motto to your work?

It's up to you
You get out what you put in
Take responsibility
Find out for yourself
Be certain

Honour & Excellence
What does the school motto mean to you?
Are you applying the motto to your work? * Economic/Financial feasibility compares the costs of developing the new system with the expected benefits.
* Technical feasibility determines the information technology requirements of the new system and the technical demands that will be placed on the new system.
* Schedule feasibility determines whether time is available to implement the new system.
* Organisational feasibility determines whether the new system will fit into the
organisation and meet the current goals and objectives.
* Ethical feasibility could involve a team abandoning a project plan as its solution involVes breaking copyright.
One solution to a problem may be found to be more acceptable than others.
For example, a project requires the use of a scanner and there is no access to this hardware.
Another solution is discovered using a digital camera (which is available) to capture images. Identify the problem
Investigate and understand the problem
Determine the constraints on the solution
Investigate possible solutions
Document the problem to be solved
Full transcript