Yes, though I think it's possible to fix the requirements, but then you have to live with a potentially unlimited timeline. Thus, it's wiser to fix timelines and have loose user stories instead.
I talk briefly about this in my upcoming book: edaqa.com/on_programming/ Though I image it's a topic that will need a book all on its own -- just to cover the idea! :)
You’re right. But the common way to plan projects, that I refer to as an anti-pattern, suggests fixed scope AND fixed project end date. I actually experienced a project where money wasn’t a thing once - there, I could have applied what you said. :-)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Yes, though I think it's possible to fix the requirements, but then you have to live with a potentially unlimited timeline. Thus, it's wiser to fix timelines and have loose user stories instead.
I talk briefly about this in my upcoming book: edaqa.com/on_programming/ Though I image it's a topic that will need a book all on its own -- just to cover the idea! :)
You’re right. But the common way to plan projects, that I refer to as an anti-pattern, suggests fixed scope AND fixed project end date. I actually experienced a project where money wasn’t a thing once - there, I could have applied what you said. :-)