Excellent idea, for the reasons mentioned and for another:
Projects can assume such broad scopes that they're often looked at in terms of "all or nothing", or "pass/fail".
Whenever possible, I like to see project design and implementation segmented such that the project is delivered in plateaus. Your example of a 30 day deliverable would be the first plateau in such a scheme.
When it's possible to deliver results this way (and of course, it's not always possible, but I think it's a strategy too-seldom used), it's also possible to ensure that, no matter what happens in later stages, usable value remains behind.
Rating:
Excellent idea, for the reasons mentioned and for another:
Projects can assume such broad scopes that they're often looked at in terms of "all or nothing", or "pass/fail".
Whenever possible, I like to see project design and implementation segmented such that the project is delivered in plateaus. Your example of a 30 day deliverable would be the first plateau in such a scheme.
When it's possible to deliver results this way (and of course, it's not always possible, but I think it's a strategy too-seldom used), it's also possible to ensure that, no matter what happens in later stages, usable value remains behind.