riskymagemerge

9 ms·

1.
by riskymagemerge 5y ago
Stupid title.
2.
by riskymagemerge 6y ago
Weekly doesn't work for us because we're running a kanban-style process and things change a lot for us. But our meetings are super short most days.
3.
by riskymagemerge 6y ago
We switched to a hybrid live/async stand-up. We use an automation to post status updates to Slack then jump on to discuss blockers and priorities.
4.
by riskymagemerge 6y ago
Agile is old. A bunch of the ideas from the manifesto, like f2f communication being best, don't hold up in 2020. We basically made up our own style based on agile, scrum, kanban and a bunch of personal experiences.
5.
by riskymagemerge 6y ago
I like the "unfocused" part. Constant context switching and lack of understanding priorities is a silent killer. As a lead I try to protect my crew from working on too many different types of projects concurrently because it makes
6.
by riskymagemerge 6y ago
I agree some internal, non-production alerts can be both important and urgent. If we merged a big branch without review for some reason, the team needs to have a conversation about it right away.
7.
by riskymagemerge 6y ago
I know. The bot sucks!!! Sorry... it's my fault. My boss, Dan the author, just yelled at me and I turned it off :-)
8.
by riskymagemerge 6y ago
Sorry! We know the bot sucks and we just turned it off. Lame marketing people.
9.
by riskymagemerge 6y ago
Shots fired! It's true though. Using Jira is a struggle.
10.
by riskymagemerge 6y ago
You have to be an expert in every person on your team job in order to be an effective manager? Not so sure about that part. But I love the hands on automation work he did when he started the team. More managers should do that.
11.
by riskymagemerge 6y ago
Love this part... “Early on, I figured out that while we have awesome technologists, probably among the brightest in the world, no one knew how to manage development, release, and write good code. So I took charge. Part of leading, especial
12.
Journey from Israeli military intelligence to VP R&D(linearb.io)
5 points by riskymagemerge 6y ago|1 comments
13.
by riskymagemerge 6y ago
"Keep your instincts. Change your behavior." Great point. The best dev leads know what their people are dealing with but respond as a leader versus a hands-on dev.
14.
by riskymagemerge 6y ago
Great article! Thanks for sharing.
15.
by riskymagemerge 6y ago
Maybe it is time to recognize that Scrum (and other variants) didnt really learn anything from Waterfall and need to be revamped altogether. I.e. this makes me cry - "If they do take time to talk, it's to describe the customer exp
16.
by riskymagemerge 6y ago
I like the thing about "dude and a half". It's very true. I can't tell you how many times I had a sales rep ask me when a feature that was supposedly on the roadmap was going to be ready and I had to be like "that t
17.
by riskymagemerge 6y ago
What's an example of a metric that engineering and product contribute to equally?
18.
by riskymagemerge 6y ago
I'm not sure I'm buying the argument that PRs are a repository for institutional knowledge. But I do think thorough reviews are important if you work at a company that has a lot of customers and cares about quality.
19.
by riskymagemerge 6y ago
Very true! The article doesn't mention that individual teams can't agree but that's another reason velocity is sketchy. Java-man, I take it you don't track velocity? What metrics do you like to track?
20.
by riskymagemerge 6y ago
Are VPs really sharing velocity with the CEO? I've never seen that. But I agree it doesn't make sense to try to use story points completed to do comparative performance measurement.
21.
by riskymagemerge 6y ago
Assume positive intent is one of the most important ideas for teams. Especially right now when we are never in the same room and many of the non-verbal communication clues are gone. I also like heroic courage - never thought of it in a deve
22.
by riskymagemerge 6y ago
Risky? You sound like an agile coach :-)
23.
by riskymagemerge 6y ago
Code changes are up and coding time is up... I think developers are taking more time to work on tasks. We get pressure to merge when we're in the office. Now we have more time to experiment and invest in quality.
24.
by riskymagemerge 6y ago
What's wrong with measuring velocity? I find it useful.
25.
by riskymagemerge 6y ago
You mentioned middle management do not normally add value to remote development. How would you fix this? Besides removing the layer :-) is there any model where they could add value?
26.
by riskymagemerge 6y ago
Panda Zoom background... all time.
27.
by riskymagemerge 7y ago
How do you calculate cycle time?
28.
by riskymagemerge 7y ago
I don't know if "dozens" of developers constitutes the right sample size. Otherwise, good article.
29.
by riskymagemerge 7y ago
Haha. That's worse than loser leaves town.
30.
by riskymagemerge 7y ago
It looks a little high up there. I would not get anywhere near that window.

More ›