Category: dev to pm

If you were hit by a bus tomorrow would your project be dead in the water?

If you were hit by a bus tomorrow… If you were hit by a bus tomorrow (knock on wood) would your project get stuck? I still remember when one I worked on did. Well, I wasn’t exactly hit by the bus, but from the project standpoint, it was close enough. We worked on an important

Continue reading

Estimates & different points of view. Business vs developers

I made an estimate… I took part in many projects, but there is one I particularly remember… As soon as I joined the team technical lead gave me a white paper with requirements and asked for estimates of a new functionality. Totally new. I was asked to estimate a chunk of the system (I had

Continue reading

Developer under time pressure ? work faster : work better

Mind reading and predicting future techniques aren’t fully developed yet. So lot’s of software development projects is late. It get’s better when the agile processes are successfully adapted but it’s not always the case. There’s always more work to be done in the project than we initially predicted. Business needs change, we misunderstand the expectations, estimation

Continue reading

What should you know about a human side of code review?

Imagine yourself sitting in front of a compiler, tasked with fixing a small bug. But you know that as soon as you say “I’m finished,” another developer – or worse, your boss – will be examining your work. How do you feel? Anxious or encouraged? As software engineers, we take pride in our work (as well

Continue reading

The Benefits Of Kanban board (even) outside an agile project.

My company uses IBM DOORS connector for JIRA to simplify requirements tracking process. However, the way requirements are transferred to JIRA from DOORS makes it hard to say what the requirement is about. So when I was looking for a way to view the actual requirement my project manager told me about a possibility to

Continue reading

IT allergens: Agile.

Here I go creating 2-people Kanban board for our current project efforts so that we can easily see how our work goes and share it with my Junior (he’s a Junior Dev, but he’s got more IT experience than I in fact… he did a career sidestep just recently).  And the first thing I hear is:

Continue reading