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 Process

After all, how else is stuff going to get done?

Adam Yoder

on 8 January 2013

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Project Development Process

Things just don't come into being all of a sudden. (that's called Spontaneous Generation, and that's been disproved for a few hundred years) Neither do projects. To get anything done, you need to utilize the... PROJECT DEVELOPMENT PROCESS (By Adam Yoder) Brainstorming "First comes thought; then organization of that thought, into ideas and plans; then transformation of those plans into reality. The beginning, as you will observe, is in your imagination." - Napoleon Hill Ideas, ideas, ideas. Nothing ever was created without an idea. Everyone, from great scientists ("how will we figure out how matter has mass?") To your average, everyday teenager ("what is this history topic going to be about?") has come up with all sorts of ideas. Projects are no different. Before beginning a project, you need ideas and a plan. Start brainstorming by writing down any potential topics you have. Then, with the help of peers or simple process-of-elimination, narrow down the potential ideas until you have the best possible option. The idea process is inherently fluid and easily changeable. Don't be afraid to start over or add more potential topics to your list. EXAMPLE This project started out as a free-selection project for a web design class. Naturally, there were a wide variety of topics: image gallery, essay, animation, or Prezi. In the end, there was only one choice, and this was one of the best-sounding ideas. After some time of debating, the rest was history. (think, think, think!) Review Specifications (what are we capable of) Planning (so, what's the plan?) Testing (1,2,3) Polishing (putting on the finishing touches) The P.D.C. involves seven steps: Brainstorming Review Specifications Planning Creation Testing Demonstration Let's begin. START EXAMPLE After the type of project was selected, there needed to be a topic. There are a ton of topics, so naturally narrowing it down was mandatory. An idea of detailing the development process was one prominent idea, due to having it been talked about prior to creating this project. That idea seemed good, so it was chosen. Everything has a limit, capabilities, and style, and it must be harnessed properly to be used to its fullest extent. "I know who I am, I know what I can and can't do. I know what I will and won't do. I know what I'm capable of and I don't agree to do things that I don't think I can pull off." -Dolly Parton Start off by understanding what your medium is. Web program presentation? Animation? Essay? Know its limitations and methods of creation, as well as your own skills, creativity, and other personal resources. It's not just the programs you have to worry about- methods of publication, file type, and even platform are all little things that make a big difference. Artwork? Example With the topic and medium decided, the important little details needed to be addressed first. After reading several Prezis for reference (some of which were tutorial-based), I had a general idea of what Prezi could do- images, zooming, rotating, and a great deal of clip art. why is there a potato here And after a short amount of toying around, it was almost time to get to work. Naturally, planning can be easy or difficult, depending on medium and experience. It also is very involved, although not as much as the next step. Plans can come in many varieties. Blueprints, storyboards, sketches, concept art, flowcharts, writing down a basic list... "For me, you have to not have a formula. You have to not even sit down and say, 'I want to write right now.' It has to just kind of come out. It's not something you can plan." -Christ Daughtry Planning is basically the act of putting ideas down so they can potentially be used, to make creation much easier. Having a plan, even if it is not much, is vital to all of this. Example All while the project was being assembled, I had to assemble the whole process. By going off some notes and a former project, I gathered the main points. The visuals, in keeping with the theme of creation, were mainly to suggest the color of blueprints. A "flowing" layout would work well, as the development process is obviously linear.
(besides, that's how Prezi functions) And while I could have made a rough drawing or design or layout of the project, admittedly I didn't. An example of how this project was made sounded like a way to demonstrate all this. Polishing Demonstration (let's take a look) Creation (let's get to work) Undeniably, the most difficult and highest effort-usage of the project development cycle is the actual creation aspect. This portion requires placing down all the assembled ideas, plans, and assorted stuff into a concrete and complete idea. Expect to change whatever original ideas didn't work, or whatever new ideas pop in during this phase. There's not much to say about this, it's self-explanatory. To ensure that the project is at the best of its capabilities, the "finishing touches" must be applied. Testing and polishing are these touches. Testing is the technical and interior aspect of the project, while polishing is the visual aspect. Sometimes the two overlap. Testing is basically ensuring that everything on the inside is working properly. Like the human body, every internal organ must function at its best in order to keep the external and total package working well. This can be done in various ways, such as scripting, (HTML5, Java, Flash, etc.) Prezi slideshow and timeline functions, and various other methods. Example All while the project was being assembled, I tested the slideshow functions, sometimes going into presentation mode to ensure that things were aligned properly. Applying transitions and frames were also an important aspect of the whole thing. Not all of this was done at once, keep in mind. The visual aspect of a project, for the average viewer, is the most important aspect. Therefore, it must look its best. Little details can mean a lot in projects like this. By putting in details, improving based on input, and following the plan, it is simple but vital to turn a project from average or mediocre into something better. "The creation of something new is not accomplished by the intellect but by the play instinct acting from inner necessity. The creative mind plays with the objects it loves." -Carl Jung Running the program itself is one of the best ways to test something. "Building technical systems involves a lot of hard work and specialized knowledge: languages and protocols, coding and debugging, testing and refactoring." -Jesse James Garrett "I don't write a quick draft and then revise; instead, I work slowly page by page, revising and polishing." -Dean Koontz "I'm looking to evolve the concept of the new renaissance artist, taking the world by storm through the art of public display and demonstration, with technical savvy, using cell phones and computers." -Perry Farrell So it's finally complete. Everything's been done. You've come up with ideas Seen what you can do Created an outline or plan Created your project Ensured everything worked properly and polished up your project. At this point, there's only thing left, and that's to show it to others, the class, or the world. End.
Full transcript