1

I don't know why, but even though I have years of experience doing agile both in school and at work, I seem to have a hard time adjusting to the agile work method because I always seem to want to do waterfall.

I don't like the stress of having to rush out a product, nor do I like working on an unknown piece of software (framework/library) without knowing it fully; it just itches me and I get obsessive.

I don't like creating just a piece of functionality and rush it out the door, but I rather like doing it in an R&D type way where I get years to finish a product that I slowly work on, like a modern-age philosopher and scientist.

I know there are companies out there that have this approach, but sadly most of them are agile 'cause they all wanna be cool.. LoL

I'm an old mind in a modern world..

Comments
  • 0
    Question:
    Are you obsessive only when it’s your work? Like when it’s somebody else’s project and you’re getting paid for it are you fine?
  • 0
    I think we should understand the framework and library we want to use fully before using it. You can argue it into a sprint using the keyword 'spike'
Add Comment