HN user

tanylak

49 karma

https://www.teamhq.app

Posts10
Comments44
View on HN

Kanban is most often used for tracking inventory, so you can technically use it to track your tasks with it. It kinda gives you a big picture view. And one of the reasons why Kanban is effective in the inventory process is because it provides you a visual signal to replenish you inventory.

As a process for tracking work, it is lacking for a number of reasons. There is too much information on the board at any one time. It is too open, meaning, you can create as many columns as you need, which leads to unnecessary complexity.

Finally, the Kanban system works well for moving physical items (completed items) from one station to next. It is not used for changing states of items. We use it to change state on incomplete tasks (i.e from Blocked to Todo to Inprogress), which not what Kanban is for.

Originally Kanban was designed to visually track inventory. It is useful in that context because you could easily spot the items that need refilling.

I've been doing project management for a over a decade now and from my experience, and interviewing people, reading, I realized that people work best in lists. Top to bottom, most important tasks at the top, least important at the bottom. It helps us focus and get more done.

So that's the primary idea behind it.

Thank you, I've been wanting to build something that works well for myself. After reading Jeff Sutherland's book, my ideas came together to the new layout and the design.

I don't know how far this will go or if it'll be successful, But I gotta give it a go.

Just put the page together this week. Will be adding more detail to it. The idea is to get away from the kanban board look and to help you track your sprint flow. Capture standup notes, sprint planning notes, manage backlog more effectively.

I just wanted to see if there was interest. Looks like there is. That's awesome.

I'll spend some time this week adding more details to the page.

Hey Hacker News crowd. After a year or so toying around with my idea, thinking about the new approach and talking to people, I have decided to build a new scrum based project management app. It's going to revolve around a new board layout and concept and include the important bits of the scrum process.

If you're interested, sing up to be notified when I have the beta version ready. Hopefully in a month or two. If not, tell your friends.

Thank you Terry

I agree. The over reliance on technology is making us less aware of our innate abilities to reason things out.

Easy access to information might make us "smarter" in a sense that we know how to find this information. But let's face it, we don't actually know how to find stuff. Google does that.

We just type simple questions that any 10 year old can do.

I've had plenty of experience in dealing with people who don't respond to criticism well. I was one of those people myself.

Mostly, the people who had a hard time responding to constructive feedback were young. They might have listened to what I had to say, but not really heard me.

After 5-7 attempts on my part, I considered them a lost cause. And they'd have to learn on their own. I was probably giving them too much respect.

I'd say, let this colleague be. If you still have to provide PRs, then just provide it on Approve/Not approve basis. If your manager requests that you more specific, then provide your honest feedback and kick it up to the manager to decide whether to approve or not approve.

But if you manager is unwilling to deal with this problem, maybe explore your options