Engineering Management
Micro-Scrum
Decide on one thing to ship, then ship (or learn).
#30 ·
Utilization
Why don’t we talk more about queueing theory.
#29 ·
DORA, SPACE, DevEx, DX Core 4
Key metrics of and casual thoughts on four engineering productivity frameworks.
#28 ·
When We Need Systems, Processes, and Conventions
Oh the bore.
#27 · · development
Results = ƒ(Competence × Time)
On a model that can tell us something about how we work, and how we could work.
#26 ·
Untrained Engineering Managers
Web development has always had a developer training issue, but it also has one on the management and leadership side. On a challenge we’re all familiar with but rarely talk and do something about.
#25 · · development
On Ticket Management
Issue tracking tools like Jira, GitHub Issues, or Bugzilla are essential for managing bugs and tasks (that is, issues). However, not everyone finds ticket management convenient or convincing. A perspective on why tickets matter, and how they can be used well.
#24 · · development
The Assessment Paradox
For any individual or group we may think that it can assess itself best because it knows itself best. Yet this is not reliable. We may then think it’s other individuals or groups interacting with that first individual or group who may be able to assess it. This is not so, either.
#23 · · philosophy
AI Paradox
Have you outrun your headlights yet?
#22 · · development
Death by Experience
It’s possible to hire too much experience, and it costs diversity and culture.
#21 ·
The Great Tech and People Hypocrisy
When we value people so much that we “rif” them even with cash in the bank, maybe we don’t value them as much as we say we do. On a two-faced industry that needs firing standards as much as it needs hiring standards.
#20 ·
Critical Feedback: Four Approaches and One Twist
Feedback is important so that we can learn and improve. Critical feedback is important to expose, validate, and address areas of growth and development. I believe that fundamentally, there are four approaches to critical feedback.
#19 · · misc
On the Gift of OKR for Company Culture
“OKR,” short for aspiration, candor, and accountability.
#18 ·
Why I Like Scrumban
Over the past years, I’ve become a fan of Scrumban, a mix of Scrum and Kanban. But what is Scrumban here, and what is there to like about Scrumban?
#17 ·
Performance and Stay Questions in 1:1s
On a set of questions that are useful to ask every few weeks, for close alignment and connection, as well as well-being.
#16 ·
Incident, Mitigate, Learn
We can’t just pick two.
#15 · · development
On Working on Vacation
Working while on vacation can be a sign of extraordinary commitment and initiative. But—it can also be a sign of disorganization and poor prioritization. A few thoughts.
#14 · · misc
Website Issues: On the Relevance of Audience Size and Impact
Website issues—relating to conformance, security, accessibility, performance, content, others—are usually treated with a particular priority, but that priority may not always be understandable, and may also be off. On the perspective we obtain when we consider and chart audience size and impact.
#13 · · development
Two Underused Arguments for Writing Documentation
Validating our thinking and allowing to scale may not get enough attention.
#12 · · development
Speed Up Your Org: When to Require Approval
Organizations can be slow. One thing that makes them slow is process. One part of process consists of approvals. But approvals aren’t always needed. On default answers, and the severity and probability of failure.
#11 ·
Reduce the Pressure on Young and Inexperienced Developers
Lower the expectations on young and inexperienced developers, and raise the expectations on their mentoring and coaching: on running gags, unrealistic expectations, and healthier hiring.
#10 · · development
Not Releasing Late on Fridays, a Matter of Courtesy
Why don’t we, in engineering departments, prefer not to release late on Fridays—or late on others days? Occasionally, developers and stakeholders believe that’s because of a lack of confidence in our code and our systems. The true reason is not that:—
#9 · · development
Thoughts for the Aging Web Developer
There may come a time when you feel “too old” for web development. When you begin to feel that, here are a few thoughts. They might not be all you need but—maybe they are of use.
#8 · · development
Engineering Management ×12
Ideas and principles for managing engineering teams: From “googliness” and “competence, caring, conviction” to systems and processes to communication and delegation to team focus and health to trust and humility.
#7 ·
5 Tips for Your Next Promotion or Salary Raise
How do you approach promotions and salary raises? Are these tied to a cyclical event or do they depend on your initiative? Do you invest into building your case, or do you wing it? Here are a few ideas on what can improve your position and chances.
#6 ·
Professional Agile Leadership (PAL) Reminders and Resources
Notes, refreshers, as well as an alternative overview over Scrum.org resources for PAL certification.
#5 ·
On Leadership
Leadership is important, and it can be learned.
#4 ·
13 Leadership Mistakes and How to Avoid Them
We’ve all seen approaches to team management and leadership that work, and others that don’t. A brief and scrappy list of the mistakes I’ve witnessed (or committed), together with thoughts on how not to make them.
#3 ·
On Enforcing Coding Guidelines
Surprisingly a snippet from The Little Book of Website Quality Control, not the one of HTML/CSS coding guidelines, a few thoughts on enforcing coding standards.
#2 · · development
What We Should Teach Up-and-Coming Developers
Evidently, learning is important, and learning strategies are, too, and how to generally work on ourselves, absolutely, but what else to aim for apart from understanding computer science fundamentals, reading the specs, and—coding?
#1 · · development