We have a web project going on and there are several use cases and we're now busy scheduling the development of the project.
We're wondering what the best practices are about scheduling a project. Should we schedule our project based upon use cases or technical tasks? I know that scheduling based upon use cases is interesting for business because they can determine what each use case costs.
However, for developers this mindset is usually not very easy to follow (they think in technical tasks). Let's say they have a technical task "Setup Java projects", this is a requirement for each use case, so it's hard to "convert" this into the functional aspect of the project.
They can divide the story points for each use case, but let's say that business puts a specific use case on hold, then the project schedule wouldn't be correct anymore.
So my question; what's the best way to schedule a project? Should it be based upon the functional part, the technical part or both?