Flexible website development: programming + design

There is quite a lot of information about agile methodologies for developing software products. But, I have never come across information (in Russian) about the use of agile for website development. I mean fairly large projects, such as social services, which implies continuous product improvement and where early launch of the beta version is important. In particular, I am interested in the question of planning parallel development of the design and the program part of the project.

Consider a typical situation. We have a project idea. Then there are 2 ways:

• Traditional: first, we write a detailed TZ for the whole product, then at the same time we program strictly according to the TZ and draw not strictly according to the TZ;), and then we painfully cross everything;
• Alternative (based on the Scrum methodology): we write the specification for a part of the project, we program, we evaluate the result and the cycle repeats, the functionality is increased.

Stop. And where is the design? How to develop a design for a part of the project? Yes, as part of the sprint? After all, in order to develop a so-called. design concept, you need a holistic vision of the functionality of the project. And the incremental approach (first programmed and drawn the user profile, then the publication mechanism, etc.) contradicts the basic principle of design development - from the general to the particular.

After the basic functionality of the project, sufficient for commissioning, has been developed, it is quite possible to develop and refine the design of individual interfaces as part of the sprints, without going beyond the scope of the design concept or style solution of the project. But how to plan the development of a style decision in the conditions of iterative development?
')
Here is what I got in theory:



For clarity, the decomposition of the design concept development process is not displayed. It is traditional.

Thus, in the closed phase of development, the created functionality is displayed in technological templates, without any design. And in parallel, based on the idea and taking into account the intermediate releases, a design concept and project interfaces are being developed. In the framework of the latter, before the publication of the draft sprint, the design and the program part are reunited and presented to the public. This solemn moment is marked with a red line in the diagram.

But, this is a theory. It would be nice to know the opinion of practitioners.

And a little more theory in the review of the methodology of Scrum Askhat Urazbayev (500 KB, .pdf). Highly recommend.