How to deal with early projects states where serious deadline agreements cannot be made yet?
We are in an early stage of the project with new people.
The team is small and everything is new (technology and people): In short. A lot of dynamic factors.
We are still in the phase were we find out how much we can do in a single sprint
A lot of important things are not yet defined in the Backlog (just exist as some vague marketing statements)
At the same time some Stakeholders already want to set deadlines or milestones.
But I would need these two things to seriously agree on something:
- Having some more experience in how fast the team performs
- Backlog with every feature that the Stakeholder wants to define the date or deadline for.
- Seriously agree on something would mean for me that between expectation and reality are not factors like two times longer or higher.
My question is how such situations can be handled or should be communicated to Stakeholders (from a Product Owner perspective).
Update Regarding Comment of Jeff: It is very interesting to have these two kinds of aspects: Date-driven and scope-driven. I guess a combination would be best. I mean a date-driven goal would mean, that you make the release at the given date no matter what happens, right? (We are still in the learning process of Scrum methodologies. So I guess hints in the direction of Roadmaps and Scrum help us in general.)