Skip to main content
16 events
when toggle format what by license comment
Oct 3, 2018 at 23:27 comment added BitsOnBitsOff Thanks everyone, all of these responses are good and you’ve all raised some interesting points.
Oct 3, 2018 at 23:25 vote accept BitsOnBitsOff
Sep 21, 2018 at 13:22 answer added dom_michalec timeline score: 0
Sep 20, 2018 at 21:12 answer added Vicki Laidler timeline score: 1
Sep 18, 2018 at 19:40 answer added Shawn Adams timeline score: 0
Sep 18, 2018 at 0:24 comment added Todd A. Jacobs @Erik I think you're making some good points, and think you should expand it into an answer. YAGNI and "the last responsible moment" are often conceptual stumbling blocks for organizations that are new to agile. You're definitely on to something by pointing out the risks of over-engineering, especially early in the product lifecycle.
Sep 18, 2018 at 0:17 answer added Todd A. Jacobs timeline score: 4
Sep 16, 2018 at 22:35 answer added Daniel timeline score: 3
Sep 16, 2018 at 12:00 history tweeted twitter.com/StackProjects/status/1041295878005436416
Sep 16, 2018 at 8:01 answer added Barnaby Golden timeline score: 2
Sep 15, 2018 at 14:59 comment added Todd A. Jacobs "Value" isn't just customer-facing value. It's value to the project. This whole question is based on a false premise, which is why your stakeholders are confused and need to be educated.
Sep 15, 2018 at 9:19 comment added Erik 60 days sounds like a lot of time to set up basic architecture. Do you really need all that architecture, just to deliver the first feature? Are you sure you're not just over-engineering?
Sep 15, 2018 at 9:13 comment added BitsOnBitsOff @Erik it varies, but an example of a ratio feature:infrastructure of 1:4+ Example 15 days for a feature + 60 for infrastructure.
Sep 15, 2018 at 9:05 comment added Erik How much time/effort in terms of architecture are we talking?
Sep 15, 2018 at 7:45 review First posts
Sep 15, 2018 at 9:20
Sep 15, 2018 at 7:41 history asked BitsOnBitsOff CC BY-SA 4.0