3 Added additional relevant tag.
| link
2 Try to fix grammar
source | link

Requirement Cut Offgathering cut off when the time offor requirement collection is too long

I am doing a small project. Users can only provide a part of requirements. The period of user requirement gathering has lastlasted for two months. But it seems not feedbackwe will receive no information for the rest of the requirements.

Should the project separatebe separated into two phasephases? One phase is to launch the system for the existing requirement. The second phase could be the reset requirement"reset requirement" and start the second requirement when user thinkthinks the reset requirement"reset requirement" is ready.

Is this a common practice if requirementrequirements cannot be collected for a certain period?

Requirement Cut Off when the time of requirement collection is too long

I am doing a small project. Users can only provide a part of requirements. The period of user requirement has last for two months. But it seems not feedback for the rest requirements.

Should the project separate into two phase? One phase is to launch the system for the existing requirement. The second phase could be the reset requirement and start the second requirement when user think the reset requirement is ready.

Is this a common practice if requirement cannot be collected for a certain period?

Requirement gathering cut off when the time for requirement collection is too long

I am doing a small project. Users can only provide a part of requirements. The period of user requirement gathering has lasted for two months. But it seems we will receive no information for the rest of the requirements.

Should the project be separated into two phases? One phase to launch the system for the existing requirement. The second phase could be the "reset requirement" and start the second requirement when user thinks the "reset requirement" is ready.

Is this a common practice if requirements cannot be collected for a certain period?

1
source | link

Requirement Cut Off when the time of requirement collection is too long

I am doing a small project. Users can only provide a part of requirements. The period of user requirement has last for two months. But it seems not feedback for the rest requirements.

Should the project separate into two phase? One phase is to launch the system for the existing requirement. The second phase could be the reset requirement and start the second requirement when user think the reset requirement is ready.

Is this a common practice if requirement cannot be collected for a certain period?