I blame the fanatically religious following of Agile (virtually zero actual design process) software methodology, and massively bloated "frameworks" that add 100's of megabytes of code so some lazy ass developer can accomplish a task with 1 line of code instead of 2-3. :/
Do you know embedded systems well? If you do, may I contact you next year with a firearms-related project I'm working on? I will soon reach the stage where I need a formal meeting with an embedded systems expert who has some basic knowledge of shooting.
Another current developer I have, works incredibly well with nothing more than a concept. This person can gather end user requirements, digest them, apply them to business processes, identify areas for improvements, design, develop, test and deploy a complete app in very short order. This person's end user followup is also incredibly good. A unicorn.
Where process analysis and design fail, money gets wasted no matter how good the developers are. Along the lines of your guy -This person can gather end user requirements, digest them, apply them to business processes, identify areas for improvements, design, develop, test and deploy a complete app in very short order. This person's end user followup is also incredibly good.
The long and short of the "Agile" buzzword, is that it's really the same thing businesses have been doing forever anyway. Used to be called "just get the shit done" though. Some people work very well in an "Agile" environment, some just can't do it. Probably why in modern buzzworld it's such "a big deal."
The long and short of the "Agile" buzzword, is that it's really the same thing businesses have been doing forever anyway. Used to be called "just get the shit done" though. Some people work very well in an "Agile" environment, some just can't do it. Probably why in modern buzzworld it's such "a big deal."
I've only had experience with Agile since 2005, spanning several industries and organizations (from public health to start-ups), so I'm not any sort of export (although I did say at a HolidayInn Express).
IMHO, the traditional Agile as taught by it's "creators" is very light on design, and heavy on "stories" and narratives. The "Just get it done" franetic throttle-to-the-firewall, nature of startups is the antithesis of Agile and all it's overhead (aks ceremonies). Management told me to stop keeping track of how much of our sprint was spent talking about our sprint, not actually producing any work.. LOL.. ignorance is bliss I guess).