Posted on 04/18/2017 5:19:37 AM PDT by Mechanicos
bookmark
The fundamental problems are the same: poorly thought-out business requirements and business focus on short-term gains over longer-term (but more risky) change.
The only place I ever worked with the software development process being good was where the software team leader was also a partner, so when the business side came flapping in with a new requirement, he would say, "Sounds good-- you'll see it in the next planned release coming next quarter, not earlier."
I worked in a big company where we'd have meetings with a program manager, team leader and several developers. I used to giggle inside about the hourly rate at which money was being pissed away in such meeting when the same company suffered significant losses because it reused a NIC card in an important server to save money. LOL
The fundamental loss of status for programmers is brought about through the introduction of outsourcing and 'consulting' services themselves, where the presence of the consultants (unless they are brought in for narrowly tailored expertise) is both a reproach and a threat to the permanent IT staff.
I’m lucky that in my current position, I can wear all the different hats of being the business analyst, project manager, and the programmer.
No kidding, and I appreciate your user story in the correct syntax.
Btw, people just started copying and pasting "As a developer..." into requirements at my last project. Unthinking automatons...
If I was a QA manager I’d quit. It must be the absolute worst job in the universe. Thank goodness QA types are almost always unusually calm people.
The older terms, "sweatshop" and "boiler room" come to mind.
Ya, "boiler room" was my first thought when I heard of shared work spaces. But at least in a boiler room you get the same seat, phone, monitor every day.
When everyone else fails, its somehow the QA manager and his team that is somehow supposed to make it all happen automagically. Believe me, I understand it.
That’s exactly what I told them. Our customers are not going to pay us to hold scrum meetings.
Besides many of my stuff I do in my career, I am Agile certified, for whatever that is worth.
The most productive of these type of meetings I had was a once a week- everyone went around the room and had to say
1) what did you do last week
2) what are you planning to do now and
3) what problems/needs do you have
You HAD TO give a good 5 minute answer or they would find more work for you or something
He's a non-professional with a blog.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.