What is the ideal project management algorithm?

Question

Project management

How to properly manage a project so that it is guaranteed not to overwhelm it?
A programmer doing a freelance project.
The customer is new.
Project - layout + programming site.
Term month.
What are my steps from start to finish to ensure that the project is delivered in a month?

Answer 1

What is the ideal project management algorithm?

Does not exist.
* Agreement with the customer
* Prepayment for iteration 0 in full.
* Iteration 0: TOR. TOR should be as detailed as possible. All members of the team can participate in its compilation. Do not use abstract words / phrases and their derivatives in TK: bad, beautiful, good, the same, different, simple. Phrases without qualifications: parameters, settings, information. Instead: parameters: A, B, C. Settings: price (real[0,∞]),...
* Signed by both parties of the TK.
* Prepayment of iteration 1 in full.
* Iteration 1: design. As soon as the customer says "yes, that's exactly what I want"
* The customer receives a copy of the design as a result of the first iteration.
* Prepayment of iteration 2 in full.
* Iteration 2: layout. As soon as the customer says "yes, that's exactly what I want"
* The customer receives a copy of the site as a result of the second iteration.
* Prepayment of iteration 3 in full.
* Iteration 3: programming. As soon as the customer says "yes, that's exactly what I want"
* The customer receives a copy of his site AND installs it on the server as a result of the third iteration.
* Iteration 4: support. Its initiator is the customer. Terms of cooperation are negotiated separately.
You work with people, what guarantees can there be?))
Wow-wow-wow, the timing is determined on the basis of the TOR, not a whim.

Answer 2

The algorithm is simple - work honestly, quickly, efficiently!

Answer 3

Break it down into small pieces and do it. You set yourself a period of half a month (so that there is another half a month for improvements). You can split it page by page, for example, if there are several different display templates for different pages, then split it. First, download the face, then the page with the side column, then the news, and so on... The same for layout. Then we look at what it needs - content. Well, in general, it’s bonal, what can I say. Write down everything that needs to be done and cross off what is done.

Answer 4

1. phasing of the project
2. list of works for each of the stages with a binary indication: ready / not ready (green / red).
3. risk
areas 3.1 risk areas for EACH of the stages.
3.2 risk zones for the WHOLE project (on the example of frequently occurring works):
green: from 30-50% of the time scale: at least a made-up template, "stretched" on the site frame, the minimum basic functionality in the user's personal account.
yellow: from 50%-70% of the timeline: at least all visualization and data exchange with the database
red: from 70-90% of the timeline: polishing and checking for bugs
4. making a secure deal on the freelance site (or contract).

Answer 5

So this is not your project?
As an intermediary with a freelancer on the implementation side is very difficult, the only method is not to take on urgent projects in such conditions.
If your site can really be done in 10 days, then the situation is approximately under control.
If programming and layout is now done by one person, then it would be better to separate them. Work on interfaces is very important for customers, and if they are completed on time, the Customer may be sympathetic to the improvements of the backend, but this, of course, depends on the essence of the project.
All other methods are standard, task trackers will help. But we must remember that the total estimate of the project time is not the sum of the task time.

Answer 6

It is logical that if you know how to manage a project, you can correctly and clearly set tasks for a programmer in the task manager, then your main risk is the competence of the programmer multiplied by the likelihood that the programmer will simply disappear.
It is logical that you need to have a good interview with the programmer in order to be sure of his skills, and the second thing is to have a second programmer.
After reducing the risks, we sit smoking bamboo and see that the programmer complies with the deadlines from the task manager, well, at the first danger, beat the programmer

Answer 7

Nothing is perfect, of course, but you can start with https://ru.atlassian.com/software/jira/agile using the Scrum methodology.
As an option to read: www.books.ru/books/scrum-gibkaya-razrabotka-po-422...