What is the scheme to develop a small Internet resource?

Question

Project management

Good time of the day!
Tell me, please, according to what scheme should the development of an Internet resource be organized "correctly"?
Scheme 1.
1.1. Functional development;
1.2. Design development;
1.3. Layout according to design for finished functionality.
Scheme 2.
2.1. Design development;
2.2. Design layout;
2.3. Functional development.
What is your option?
Thank you!

Answer 1

BDD, Agile.
We divide the development process into stages from a week to three.
We share the functionality and write the specification (in human language or in Gherkin). (this should be done by good business analysts in consultation with the product owner and then all this is given to QA who either add acceptance tests or simply write acceptance criteria). Based on our specifications, we choose the most important functionality for the upcoming release, implement it.
If we take all sorts of scrums, then we have a place to be a zero sprint. This is the stage where designers can start working on designs while developers deploy the project structure, CI server, and all the infrastructure they need.
Further, the developers will implement the functionality chosen for this period of time (the design for which the designers should have started preparing a little earlier) and release it (hand over to QA). They check and report what functionality is ready, what bugs, what violates UX, etc. Then, at the end of the sprint, a retrospective rally can be held to discuss issues and adapt the process.
After a couple of sprints, the predictability of everything and everything will improve. The development cycle of each team will be continuous and implies close communication with each other. Based on all this information, the next releases and new functionality are planned.
Here...
UPD: not a big one... If you can start working on functionality without design, you should start with this. We can say that first we do everything on twitter bootstrap and then the designers will better navigate the functionality and use the existing implementation as a prototype.

Answer 2

1. Gathering requirements
1.1 Writing a functional task
2. Designing
2.1 Interface
2.2 Architecture
3. Planning
3.1 Decomposing the project into tasks
3.2 Determining the necessary resources
3.3 Drawing up an implementation schedule
4. Coordination
5. Documenting
5.1 Writing technical specifications
6. Starting development
6.1 Separation of roles and responsibilities
6.2 Develop according to plan
6.3 Show demo 1
6.4 Adjust plan and requirements after demo 1
6.5 Develop according to plan 2
6.6 Show demo 2
10
_
_
_
_
_
_ Pre-release demonstration and approval for deployment
11. Documenting the code and the project
11.1 Commenting on the code
11.2 Compiling a help for deploying the project, setting up configs, enabling / disabling features not displayed in the CMS
12. Deploy
12.1 Installation on the release server
12.2 Load testing
12.3 Setting up backups and version control for updates
13. Support

Answer 3

Prototyping! Don't forget about prototyping. Because you will be doing the design - the customer will be seven Fridays a week with Wishlist (functionality). If you make it functional, the customer will tailor the design, which the wife did not like or the accountant criticized. With prototypes, more or less decide on the functionality, and then it will be clear what to decorate and where to hang the pictures.

Answer 4

for example, on small projects we have:
0. Writing technical specifications
1. Prototyping
2. Design
3. Layout
4. Integration + programming
On large ones, we launch programmers and designers at the same time, then a layout designer and then integration.

Answer 5

I will add to the previous speakers that between the stages of prototyping and design it is necessary to shove user testing of the prototype - a lot of annoying little things will definitely come up. Because of them, we finish the prototype, test it again, and then only give it to design.