SCRUM
-
You must understand that this new crap has been developed to occupy managers with no software developement background. There is a new class rising, the MBA class, they have invented SCRUM just to mix with developers and take advantage of them.
They are taking advantage of you because you allow it. Don't take crap from MBAs! Fight back! SCRUM/Agile is very flexible set of guidelines. Every company's implementation is different. If you let the MBAs pick the implementation rules, they will naturally pick rules whcih best serve them. This worked for me: Study scrum/agile on your own. Find as many web sites/videos as you can with differing views and note the rules/practices which YOU like. Once you are an expert, use those sites as references to justify doing what you want and suggest process changes. Over time, you will become the "scrum expert" and can force the MBAs to obey your evil bidding. Once YOU are the acknowleged SCRUM expert, you don't need the external references. You will be able to make up new rules and proclaim them to be "process improvements". I am currently working on a "process improvement" which gets me a real office. :) Used properly, SCRUM can be a powerful tool which you can exploit to improve the working conditions of you and your fellow programmers. Good luck!
-
You must understand that this new crap has been developed to occupy managers with no software developement background. There is a new class rising, the MBA class, they have invented SCRUM just to mix with developers and take advantage of them.
Interesting, at my last job we did SCRUM and it worked really well. It certainly isn't for every group but if you don't like it, maybe you are doing it wrong. :)
There are only 10 types of people in the world, those who understand binary and those who don't.
-
You must understand that this new crap has been developed to occupy managers with no software developement background. There is a new class rising, the MBA class, they have invented SCRUM just to mix with developers and take advantage of them.
According to my process development experience, people who claim that: 0. either did not understand the concept, 1. or do it wrong. (0. often leads to 1.) Every process model and corresponding methods have pro and cons, and what works somewhere does not necessarily work elsewhere. Process requires intelligence, Agile processes even more.
~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus Do not feed the troll ! - Common proverb
-
You must understand that this new crap has been developed to occupy managers with no software developement background. There is a new class rising, the MBA class, they have invented SCRUM just to mix with developers and take advantage of them.
What would you like to compare it to? One of the great waterfall methods, like SSADM, where you need to know everything before you write any code? Or do you subscribe to the undesigned code and hope school of application development? This is the second thread today where SCRUM has been questioned without addressing any actual, or perceived fault. SCRUM relies on short, timeboxed development cycles and allows for comparisons of effort across sprints. Developers and users regularly interact to reduce wasted effort on unnecessary or unneeded deliverables. The non-code artefacts are kept to a minimum so that great code can be delivered quickly and due to the rapid cycles without to many bugs. So what don't you like?
Reality is an illusion caused by a lack of alcohol
-
What would you like to compare it to? One of the great waterfall methods, like SSADM, where you need to know everything before you write any code? Or do you subscribe to the undesigned code and hope school of application development? This is the second thread today where SCRUM has been questioned without addressing any actual, or perceived fault. SCRUM relies on short, timeboxed development cycles and allows for comparisons of effort across sprints. Developers and users regularly interact to reduce wasted effort on unnecessary or unneeded deliverables. The non-code artefacts are kept to a minimum so that great code can be delivered quickly and due to the rapid cycles without to many bugs. So what don't you like?
Reality is an illusion caused by a lack of alcohol
Quote:
to reduce waisted effort
are you saying all good Scrummers are fat?
- Life in the fast lane is only fun if you live in a country with no speed limits. - Of all the things I have lost, it is my mind that I miss the most. - I vaguely remember having a good memory...
-
Quote:
to reduce waisted effort
are you saying all good Scrummers are fat?
- Life in the fast lane is only fun if you live in a country with no speed limits. - Of all the things I have lost, it is my mind that I miss the most. - I vaguely remember having a good memory...
I see nothing. #whistle#
Reality is an illusion caused by a lack of alcohol
-
Quote:
to reduce waisted effort
are you saying all good Scrummers are fat?
- Life in the fast lane is only fun if you live in a country with no speed limits. - Of all the things I have lost, it is my mind that I miss the most. - I vaguely remember having a good memory...
Forogar wrote:
are you saying all good Scrummers are fat?
They used to be[^], although those at the top end no longer are.
Every man can tell how many goats or sheep he possesses, but not how many friends. Shed Petition[^]
-
Forogar wrote:
are you saying all good Scrummers are fat?
They used to be[^], although those at the top end no longer are.
Every man can tell how many goats or sheep he possesses, but not how many friends. Shed Petition[^]
I'm thinking of taking up rugby.
Sort of a cross between Lawrence of Arabia and Dilbert.[^]
-Or-
A Dead ringer for Kate Winslett[^] -
What would you like to compare it to? One of the great waterfall methods, like SSADM, where you need to know everything before you write any code? Or do you subscribe to the undesigned code and hope school of application development? This is the second thread today where SCRUM has been questioned without addressing any actual, or perceived fault. SCRUM relies on short, timeboxed development cycles and allows for comparisons of effort across sprints. Developers and users regularly interact to reduce wasted effort on unnecessary or unneeded deliverables. The non-code artefacts are kept to a minimum so that great code can be delivered quickly and due to the rapid cycles without to many bugs. So what don't you like?
Reality is an illusion caused by a lack of alcohol
Nagy Vilmos wrote:
SADSM
FTFY! :laugh:
Sort of a cross between Lawrence of Arabia and Dilbert.[^]
-Or-
A Dead ringer for Kate Winslett[^] -
Actually, it was invented because so many managers have no software developement background. It stops them making so many decisions about something they know nothing about.
I wanna be a eunuchs developer! Pass me a bread knife!
Which is why you shouldn't allow people to manage IT projects that do not have a technical background: recipe for disaster. (Seen it too many times)
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair. nils illegitimus carborundum me, me, me
-
You must understand that this new crap has been developed to occupy managers with no software developement background. There is a new class rising, the MBA class, they have invented SCRUM just to mix with developers and take advantage of them.
Leslie Nielsen said so yesterday. Seriously, you are saying exactly what I said. ;P : [^] Re: Wow.. SCRUM is **horrible**... wizardzz 21 Feb '13 - 10:15 Project management ideologies were created to, and continue to exist to, give PM's and other noncoder a**holes jobs. This industry is diluted and hurt by people wanting to be part of it, simply because it pays well, and there is still some growth. These people don't want to, or simply can't code, so they take any other approach to gain entry. If, nay, when I start my company, everybody will have the ability to code, if you are in a non coding position, that one of your previous jobs will have been coding or you are currently learning. Everyone should understand the love affair with coding, the frustration, the rewards. Everyone. Lawyers, sales, human resources. Everyone.
-
What would you like to compare it to? One of the great waterfall methods, like SSADM, where you need to know everything before you write any code? Or do you subscribe to the undesigned code and hope school of application development? This is the second thread today where SCRUM has been questioned without addressing any actual, or perceived fault. SCRUM relies on short, timeboxed development cycles and allows for comparisons of effort across sprints. Developers and users regularly interact to reduce wasted effort on unnecessary or unneeded deliverables. The non-code artefacts are kept to a minimum so that great code can be delivered quickly and due to the rapid cycles without to many bugs. So what don't you like?
Reality is an illusion caused by a lack of alcohol
-
Which is why you shouldn't allow people to manage IT projects that do not have a technical background: recipe for disaster. (Seen it too many times)
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair. nils illegitimus carborundum me, me, me
mark merrens wrote:
Which is why you shouldn't allow people to manage IT projects that do not have a technical background: recipe for disaster. (Seen it too many times)
The opposite can be true too... "Hey, you're a great programmer, we're putting you in charge of all these other programmers" It took about two years for me to realise it, but this was the worst day of my career so far.
-
mark merrens wrote:
Which is why you shouldn't allow people to manage IT projects that do not have a technical background: recipe for disaster. (Seen it too many times)
The opposite can be true too... "Hey, you're a great programmer, we're putting you in charge of all these other programmers" It took about two years for me to realise it, but this was the worst day of my career so far.
True indeed.
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair. nils illegitimus carborundum me, me, me
-
mark merrens wrote:
Which is why you shouldn't allow people to manage IT projects that do not have a technical background: recipe for disaster. (Seen it too many times)
The opposite can be true too... "Hey, you're a great programmer, we're putting you in charge of all these other programmers" It took about two years for me to realise it, but this was the worst day of my career so far.
That's the thing. Management skills and programming skills are completely unrelated; being fantastic at one doesn't imply any competence at all in the other. If you're a good programmer, you need a manager to handle the things that you shouldn't be spending your time on, but those things don't include designing the code or deciding what needs to be done to make the product meet customer requirements. Agile puts the responsibility for those in the hands architects and developers, which is where it should be.
I wanna be a eunuchs developer! Pass me a bread knife!
-
Which is why you shouldn't allow people to manage IT projects that do not have a technical background: recipe for disaster. (Seen it too many times)
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair. nils illegitimus carborundum me, me, me
mark merrens wrote:
Which is why you shouldn't allow people to manage IT projects that do not have a technical background: recipe for disaster.
I'm not convinced there is any such thing as an "IT project". There are loads of "business projects" which include IT components, though.
Currently reading: "Sundiver", by David Brin
-
mark merrens wrote:
Which is why you shouldn't allow people to manage IT projects that do not have a technical background: recipe for disaster.
I'm not convinced there is any such thing as an "IT project". There are loads of "business projects" which include IT components, though.
Currently reading: "Sundiver", by David Brin
Brad Stiles wrote:
I'm not convinced there is any such thing as an "IT project". There are loads of "business projects" which include IT components, though.
After 25 years I'm convinced there are IT projects that may, if completed, serve a business need. Really doesn't matter which way around you frame it, all the successful projects have been technology led, all the bad ones, business led. That is, where the manager, for instance, is from the business side and has no technical competence at all; the expectations go from unrealistic to demanding to desperate as they struggle to understand what it is they are supposed to be managing. The problem always appears to be that the non-technical manager simply has no idea how any of this works, what the real complexities and issues are or, in particular, how to manage the people. By the time they figure it out, for the most part, it's too late. Pardon my cynicism, been around too long to believe that there are any magic bullets or that one way of doing things is the best. That is why I still think that projects that are technology led and people (that is, the team players) focused work the best, regardless of what flavor of management-speak you color it in with.
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair. nils illegitimus carborundum me, me, me
