How is it right to divide the development of a web project into the arts?
inna last edited by
We're trying on the team to introduce a flexible web design methodology. Before that, they were working on classical waterfall (Cascode Model), but projects are lengthy.
The challenge now is to move a large project from one platform(asp.net) to another (php). And I had a question about how to approach the project's story.
The project shall in any case pass through:
- Interface development
- programme part
Colleague, please help me:
The methodology was fully operational, it's the back of the story.
morde last edited by
Using history is not the end-of-life tasks that you, as project manager, should form, balog, assess with the team, and then pull into a sprint.
User's story is written by analysts, a customer, anyone but not a P.M. You should be given a complete, concrete artisanal history, after which it is divided into tasks (diseine, development, co-piercing, etc.).
It is quite often that one user story coincides with one sprint at a time.