into Software Projects
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
How to divide a resource? Wood Take the wood Take 50% to build dollhouse Take 30% to build a garage Take 20% to build a toy car Now you have 3 pieces of wood and you can quickly deliver three wooden toys. Software developer Take software developer Assign 50% to project A (head) Assign 30% to project
Thanks everyone for attending my presentation. If you have any questions or just want to talk over a cup of coffee don’t hestiate to contact me via your favourite means (I’m social!) Here are the slides from my presentation (avilable also on Speaker Deck)
Imagine what happens when you approach the developer in a middle of that task? Now, if you think he/she can pick up where he/she stopped you couldn’t possibly be more wrong.
When your dev don’t want to follow the process he’s incompliant, isn’t he? But what if the process is killing creation and innovation?
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
Recently I wrote how to deal with requirements in the process of a software development. Requirements are often customers expectations but those aren’t always the same. And not only your customers have expectations. In reality, every person included or interested in a software project has her/his own interests and expectations. And even as a simple developer you
Have you ever worked on something for a long time, only to realize in the end that you’ve completely missed the point? Probably. this is how to ensure you know what’s about to be built.
We didn’t become programmers because we like working with people. But most of a software is created by teams. So like it or not, you must effectively communicate with others.
Here’s how.
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:
