3 ms·
The business has a need for a regular status update from everyone. You can call it a standup or not. You can call it not agile, but in the end the business has
by bluGill 2y ago
The business has a need for a regular status update from everyone. You can call it a standup or not. You can call it not agile, but in the end the business has needs and you cannot ignore those needs.
The business needs to know when something will be done as they need to make promises to customers. The business also needs to know when things will be done as that is a proxy for cost - they need to make sure they are not spending more creating a thing than it will deliver (this is a hard problem as some sales will not happen until it is done and there is typically a competitor customers could go with). That is nearly impossible to say how long engineering will take doesn't mean we don't need to know how long it will take!
- stetrain 2y agoSure. I'm not saying there shouldn't be status updates. I'm just saying that those status updates aren't because they are "doing Agile." There isn't really any such thing as "doing Agile", it isn't a prescribed process to follow. And saying that you use Agile instead of Scrum but dislike the invasive status meetings isn't actually congruent with the actual definitions of Agile or Scrum.
- seadan83 2y agoAgile is meant to be a collaborative process with a user or customer to discover the truly desired objective. Baked into agile is the notion of changing courses. A business that wants a deliverable by a certain date wants a contract - not Agile. How can a route be predictable look with a process that explicitly seeks to regularly change course. We could also get into the theory of whether it is actually possible to say how long software will take at all. Business might bevroutineky asking for the impossible using the wrong methodology for what they think they want
- jiggawatts 2y agoSoftware with business utility is never "finished" unless the business is finished. Trying to estimate when software is finished is tantamount to asking when the last light will be turned off forever in the warehouse. I keep trying to tell PMs that around the release date is when developers are the most busy, including afterwards. It's not some magic deadline after which developers are no longer needed.