Skip to main content
Tweeted twitter.com/StackProjects/status/650795267046944768
Clarify question; grammatical and semantic edits; retagging.
Source Link
Todd A. Jacobs
  • 50.7k
  • 7
  • 60
  • 181

How do you handle a situation of endschedule delivery datedates in agileScrum?

I've run into a constant issue. When a project starts, the client typically has a list of functionalities to be built in to the application. As a team we would like to follow Agile's scrumScrum. But the next thing the client asks is for a go live-live date.

The client has his own deadlines to gotogo to the market. So it's valid that he needs to know a date so that he can tell the rest of the business when the application arrives.

Since the team can't plan out more than one sprint at a time, there is typically no visibility on the end date. The client says -, "I've already told you what exactly are thewhat functionality I need, tell. Tell me when you can build this app"app."

How do you deal with a situation like this in agile or Scrum?

How do you handle a situation of end delivery date in agile?

I've run into a constant issue. When a project starts, the client typically has a list of functionalities to be built in to the application. As a team we would like to follow Agile's scrum. But the next thing the client asks is for a go live date.

The client has his own deadlines to goto the market. So it's valid that he needs to know a date so that he can tell the rest of the business when the application arrives.

Since the team can't plan out more than one sprint at a time, there is typically no visibility on the end date. The client says - "I've already told you what exactly are the functionality I need, tell me when you can build this app".

How do you deal with a situation like this?

How do you schedule delivery dates in Scrum?

I've run into a constant issue. When a project starts, the client typically has a list of functionalities to be built in to the application. As a team we would like to follow Scrum. But the next thing the client asks is for a go-live date.

The client has his own deadlines to go to the market. So it's valid that he needs to know a date so that he can tell the rest of the business when the application arrives.

Since the team can't plan out more than one sprint at a time, there is typically no visibility on the end date. The client says, "I've already told you exactly what functionality I need. Tell me when you can build this app."

How do you deal with a situation like this in agile or Scrum?

Source Link
John
  • 648
  • 2
  • 7
  • 10

How do you handle a situation of end delivery date in agile?

I've run into a constant issue. When a project starts, the client typically has a list of functionalities to be built in to the application. As a team we would like to follow Agile's scrum. But the next thing the client asks is for a go live date.

The client has his own deadlines to goto the market. So it's valid that he needs to know a date so that he can tell the rest of the business when the application arrives.

Since the team can't plan out more than one sprint at a time, there is typically no visibility on the end date. The client says - "I've already told you what exactly are the functionality I need, tell me when you can build this app".

How do you deal with a situation like this?