Why Agile Often Fails

Why Agile Often Fails

To be honest, I've always looked down on Agile and such methodologies, it's so hard to be just when you've been bombarded with buzzwords from a long time. Even terms like "iterative" or "incremental" feel like buzzwords to me - even though they are very useful ideas. It felt like boring management stuff. But it turned out Agile is pretty good, but how people implement can differ, and it can go wrong.

Same goes for teaching best practices, some teachers like to follow rubrics: "top 10 things to do as a teacher". But often it fails and it turns students off because the teacher isn't focusing on the values behind the practices, they just implement them mindlessly. For example you see many teachers starting is lecture (in classroom or online course) by stating the objectives of the lecture. The problem is that they treat it as a item in their checklist and it often ends up being boring and souless and you just feel like skipping it.

In my country we have an old wisdom that is loosly translated as: "judging a thing is a reflection of one's perception of it."

And how we perceive something can affect how motivated we are. For example, two people can perceive studying differently, and hence it can change how much they do it. It's part of being a human. Ideas can have a huge impact on our emotions and actions. The problem with many meetings is that not everyone in the team see the value in them. Devs for instance often find meetings annoying and take a lot of time that could have been used for "real work" and build software. They perceive meetings as a chore, they think of it as a tool for the PM, management stuff - the PM wants to see if things are going well and if it's according to the plan. so the devs will probably speak as little as possible and just get it done to go back to "real work". - which sadly reduces the meeting's value. They think of it as a status sync. And that's how most stand up meetings are honestly. No wonder many people hate them.

But it doesn't have to be that way, if you can show your team that it can actually be useful for them, by actually designing useful meetings: if the meeting becomes a planning tool for everyone, a meeting that makes sure everyone is taking good decisions (and not just following the plan), not just a mere status sync. Devs might suddenly find it useful. If the devs start to think of it as a way to understand how the project is going and coming up with ways that make everyone work better. Suddenly it becomes important to them.

Yet changing someone's mindset about something is not easy or a simple process. And it's not just about throwing buzzwords or -ities. In fact even a term like "mindset" and "motivation" can be a turnoff to many people - including me. Human beings are complex, it's not a simple equation, thoughts affect emotions and behaviors, and behaviors will affect the thoughts again. And it's not as simple as changing how you percieve something, if something is truly useless no matter how one tries to think of it postively it would shatter when it faces the real world.

One final important idea is that we often try to seek perfection. As if we need to be passionate about everything! People don't need to love everything they do. It's okay if the meeting is a bit boring, it can have some value to the PM nevertheless. But we can do better.

Discussion 0 comments · 2 points · ghassenfaidi · 10m
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com. Type a domain, or paste a link to block its site, and press Enter.

New collection

Delete this collection?

About YAVCHN

YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

Created by Paul Parks and built with PUDL.

YAVCHN source code on GitHub

Privacy policy · Terms of use

Help

Keyboard

j / k
Move down and up the story list. The arrow keys scroll whatever has focus.
Enter
Read the marked story in the article reader.
[ / ]
Read the story above or below in the list, in the same article reader. Back returns to the story you came from.
p
Pin or unpin the marked story, which keeps it in Pinned.
n / N
Move to the next or previous top-level comment in the window in front.
c
Collapse or expand that comment.
f
Hide or show the story list.
Esc
Close a menu or this help.
Access key m
Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
?
Show this help.

Windows

Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or Story > Open in new reader window to open another reader for the current article. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Previous and Next buttons read up and down the list in the same window.

A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Previous and Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

The list

The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

Collections are named lists of stories. Story > Add to collection files the story in front into one or more of them, and the Collections feed shows them all or one at a time; the menu that chooses collections also creates, renames, and deletes them. A note is your own text on a story. Choose Add note in a story's toolbar to write one; it saves as you type. Rows with a note carry the note mark, and the Notes feed lists every noted story and searches the text of your notes.

Browsing view

View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page is a one-off action that does not change your saved default. Use the Windowed selector to return an article to a window. Direct page links always open as pages.

Applets

The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser anonymously and is included in retained applet state when signed in.

Find

Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

About

YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Without a YAVCHN account, your data stays in this browser. When signed in, pins, collections, notes, blocked domains, and retained reading state are stored with your account and synchronized across devices. Hidden stories and layout stay in this browser. The privacy policy has the details.

Open source: github.com/paulmooreparks/yavchn. Built with PUDL.