7 ms·
I know this was intended with a good heart, but it seems very naive to me. At times I have hated agile & scrum. I have hated interruptions, I have hated meeting
by dahart 10y ago
I know this was intended with a good heart, but it seems very naive to me. At times I have hated agile & scrum. I have hated interruptions, I have hated meetings, and I have hated deadlines. I've tried to explain to management that they were shooting themselves in the foot by adding overhead with meetings and status reports. With hindsight, I now believe I was wrong.
As an engineer, this sounds like bliss. Sit quietly by myself without interruptions and solve the problems of my choosing in whatever way I consider the highest quality. It sounds like grad school.
As a manager & business owner this sounds like a nightmare. Engineers who refuse to make & meet deadlines, refuse to communicate & report status regularly, and work on problems of their own choosing, it adds up to people I can't make very good use of, and work getting done that doesn't contribute meaningfully to the bottom line.
There's a reason you need regular communication: because people walk out of planning meetings with different ideas in their head, even when everyone thinks they agree. If you don't follow up often, nobody will get what they expect. Realizing that as a programmer, even if it's painful, that I need regular checkins in order to be more useful to the organization, that is something that didn't happen early enough in my career.
- lupin_sansei 10y agoExactly. Pushing these ideas too hard gets your labeled as a troublemaker and uncooperative. I've learned to choose my battles very carefully.
- bjourne 10y ago> Engineers who refuse to make & meet deadlines, refuse to communicate & report status regularly, and work on problems of their own choosing But that is a straw man. No one is suggesting anything of the above is good behaviour.
- dahart 10y agoAre you sure? I was responding to: "Estimates are to be avoided at all cost." "Don't fear running late." "Having a meeting once in a week/month or other indicator based solely on time is meaningless." "Value quality over deadlines."
- bjourne 10y agoIf you read the manifesto it asserts that estimates are impossible to make. It's the difference between being unable to produce an estimate and refusing to produce one. I don't think the manifesto is very good, but it doesn't encourage subordination afaict.
- dahart 10y agoYou're right on the surface, in the literal sense, the manifesto is not directly saying engineers should disagree with managers. But, unless management wants to get rid of estimates and deadlines, it is advocating an antagonistic belief system. It is insubordinate and will cause people to act insubordinately merely to believe that estimates should be avoided at all cost, and that contact between engineers and managers should be minimized and not done on a regularly scheduled basis. Managers can't do their jobs if engineers believe those things. Programmers can't either, some of them just don't know it yet. You can't succeed as an engineer if you can't produce work on a deadline, and estimate and budget your time to meet the company schedule. Accepting that, and understanding why estimates and deadlines and scheduled communication are important to your manager and to the company, and learning how to better facilitate and participate in those activities will make you a better, more valuable engineer.
- discordianfish 10y ago> But, unless management wants to get rid of estimates and deadlines, it is advocating an antagonistic belief system. I agree that 'at all cost' doesn't seem reasonable. Yet I think they should try very hard to avoid them. Estimates, meeting and deadlines might be required some time. You might had to announce a release date for some new features. That's a deadline you can't always avoid. But you can avoid arbitrary deadlines that are just there to 'motivate' engineers and get them to ship "something". That leads to worse quality and technical debt decreasing overall productivity on the long term.
- bjourne 10y ago> You're right on the surface, in the literal sense I have a feeling that whoever wrote that manifest prefers if it is read literally. ;) I guess that is the heart of the issue, isn't it? The author thinks it would be better if companies adapted to how engineers prefer to work over engineers adapting to how companies prefer to work.
- sheepmullet 10y ago> There's a reason you need regular communication: because people walk out of planning meetings with different ideas in their head, even when everyone thinks they agree. If you don't follow up often, nobody will get what they expect. Regular communication is critical. Often developers forget that the reason this communication is heavily structured, and often in a less than optimal way, is because of the way managers are expected to operate. For example I have standard weekly meetings because they allow me to block out that time slot. Sure it might be more useful to meet with you tomorrow instead but if I don't have standard times I will be swamped myself
- dexwiz 10y agoAgreed. It seems like the manifesto is designed with the idea that engineers should not develop any soft skills, primarily communication. I find biweekly or monthly meetings with stakeholders to be extremely useful. I do not tie my work output to these meetings. They are just status updates, feedback, and plans for the future. I try to walk into them without a plan, just a set time for a conversation. Sometimes I don't have anything to show unless they "want to watch tests run." In which case I get a resounding, "No," and we move on. It is up to you as a developer to set the tone for these meetings. Frame it as a conversation, not a presentation. Most process breakdowns and anger are rooted in the fact that people don't understand each other's job. Sitting in an office, and passing "quality" work under the door irregularly does not help. Management has no visibility into this and will eventually lead to confrontation. Being open and honest with communication builds trust which will lead to longer lasting happiness than sequestering yourself away. I would agree that software estimates are hard. The simple solution to that is take whatever you think it will be and double it, triple it, quintuple it. Whatever works for you. Under promise and over deliver might be controversial, but I think it applies here. It's more about giving yourself room than wowing management. Sometimes those misestimations are because you are blocked by other team. No one develops by themselves, no matter how much of a 10x engineer you think you are. This is where the trust you built with management comes into play. Use them as a tool to get things done across teams. This manifesto is all about giving back the power to the developer to manage their own time. It basically says, "Developers do want you want. And management, stay out of their way." Its reactionary, because the author feels like Agile/SCRUM has been used against them. This is completely understandable. Feeling powerless is heartbreaking. But trying to implement something like this would never fly. And if it did, it would eventually be twisted just like Agile has. No manifesto will help you in this case. You need to learn how to communicate, and through communication reassert your power over your situation and the decisions being made by participating.
- cookiecaper 10y ago> And if it did, it would eventually be twisted just like Agile has. This is such an important thing to note. Almost everyone claims to be using an "agile development process" these days. I'm certain at least 75% of the people that claim to do this don't know there's an actual real process attached to that claim and instead just think it's a way to tell people they're a cool company to work at. The bosses are going to have their way. If they want a meeting, your "agile manifesto" is not going to block them, regardless of the promises made in their circulations and recruitment material. Some are more subtle about this fact than others.
- mathattack 10y agoThere's a reason you need regular communication: because people walk out of planning meetings with different ideas in their head, even when everyone thinks they agree. If you don't follow up often, nobody will get what they expect. Very true. And memories are faulty. And planning meetings can be inconsistant.
- mgiannopoulos 10y agoCommunication with management and clients is important. A developer does not work in a vacuum. The article contains some good concepts (like "don't micromanage"), but how is the engineer going to "keep thinking about long term goals" without communicating with anyone? And how can each engineer "pick his own tasks" as part of a team?
- discordianfish 10y agoI think the biggest problem isn't with having meeting or not, but with the quality of the meetings. I think we all know both: The ones you walk away with new perspective and the feeling that everyone is on the same page while wasn't before. And there are those you can barely keep your eye open because the things communicated are obvious, redundant or irrelevant.
- imagist 10y agoThis is a perfect example of the cognitive dissonance in business. The driving premise of capitalism is that various competing companies pursuing the bottom line will produce the best outcomes. Yet here we have a case that shows this premise to be a lie. The engineer in your story wants to produce a quality product, a good outcome. But the manager in your story won't allow a quality product because it conflicts with his bottom line. The bottom line is directly at odds with a good outcome. And sure, within the context of business there has to be a balance between seeking good outcomes and the bottom line. But to me, that means we should be seeking a better model than business, that allows better outcomes. Maybe the Longflow Manifesto doesn't work in business, but maybe that is because business is wrong, not because the Longflow Manifesto is wrong.
- johncolanduoni 10y agoNegative effects of lack of coordination can be seen in (non-commercial) open source projects as well, so this isn't as simple as "bottom lines can decrease quality". Wanting to produce a quality product doesn't guarantee that outcome, especially when there are trade offs that need to be made.
- imagist 10y agoIt is absolutely as simple as "bottom lines can decrease quality". Removing the bottom line from consideration doesn't guarantee a good result, obviously. But that doesn't mean that bottom lines can't decrease quality.
- johncolanduoni 10y agoI wasn't saying they couldn't, I was saying that they're not the only thing in play here because removing the bottom line doesn't suddenly make you able to avoid putting effort into coordination.
- imagist 10y agoObviously.
- dosethree 10y agoI've worked on Kanban agile teams that don't do estimates, and I strongly prefer it. I think it's still critical to demonstrate incremental value, but there's a deadline oriented culture at some places that just ends up hurting the business by causing people to make the wrong trade offs and short term thinking. Not so bad in some contexts, but terrible in others.
- raphar 10y agoOver the years I began to understand the business view of deadlines, meetings and estimations. The business needs new product changes, and need them asap every time. As an engineer you must understand that they are paying you for solutions. Said that, as an engineer you can and must plan for this and embrace it. You must design your software with enough flexibility to support continuous changes on your systems. You must also design your process. And if your are tech leading, you have this additional responsabilities: * Maintain a slow flow of changes (for core, architecture, ...) * Maintain a fast flow of changes (for business) With those on place perhaps you can give a not so frantic pace on the important places of your system (your engineers will thank you and will love working in these). And business will appreciate that you don't fight every proposed change. (fighting them is uphill and generally useless)