It's pronounced Diane. I do data architecture, operations, and backend development. In my spare time I maintain Massive.js, a data mapper for Node.js and PostgreSQL.
If you don't know at any given time whether the thing you're working on is going to live out the week, you have problems that aren't going to be solved by adopting this or that development methodology. In this situation, the best methodology is as little as possible: sort tasks into 'now' and 'not now' piles, pick something off the 'now' pile, execute, repeat, reevaluate when you're almost out of 'now'. No point putting more effort into it than that until things stabilize. That's the major concern here: if your business plan depends on basically aleatory external factors not just to succeed but for people to know what they need to be doing at all, why aren't you all just trying your luck at the casino instead?
If you don't know at any given time whether the thing you're working on is going to live out the week, you have problems that aren't going to be solved by adopting this or that development methodology. In this situation, the best methodology is as little as possible: sort tasks into 'now' and 'not now' piles, pick something off the 'now' pile, execute, repeat, reevaluate when you're almost out of 'now'. No point putting more effort into it than that until things stabilize. That's the major concern here: if your business plan depends on basically aleatory external factors not just to succeed but for people to know what they need to be doing at all, why aren't you all just trying your luck at the casino instead?
I was thinking the same thing, I can't imagine working where two week sprints are not flexible enough.