-
Test cases are here for a long time. Used equally willingly by these who work with heavy-weight processes and those who choose the agile way. They can be stored in an appendix to documentation in BDUF (Big Design Up Front) project or be written on yellow cards along with user stories. Where’s their main value […]
-
That’s the old story: we suck at estimating. Our schedules tend to be wrong not only because there are unexpected issues but mostly because we underestimate effort needed to complete tasks. There’s one simple trick which allows improving quality of estimates. It’s simple. It’s reliable. It’s good. On the minus side you need some time […]
-
It’s always a difficult situation. The last project was late and I don’t mean a few days late. People did a very good job trying to rescue as much as they could but by the time you were in the half you knew they won’t make it on time. Then it comes to these difficult […]
-
Unit testing is such a nice idea. Developers create tests as they develop working software. Then they (tests, not developers) are executed during every build and it’s verified whether something hasn’t been broken over the way. Unfortunately unit tests very often doesn’t work well even when team formally boast they employ this practice. Why? 1. […]
-
Vast majority of people working on software products contact their customers directly or indirectly. Yes, software developers included. Each time we do it we play a role of salespeople. Of course customers don’t see us making product presentations or negotiating prices. What do they see then? In my case answer is pretty easy since my […]
-
A developer who sends an email to a customer to elucidate some details of proposed solution. He is a salesman. A project manager who goes on biweekly status meeting. She is a saleswoman too. A support engineer who answer for ticket submitted by one of clients. Guess what, he’s a salesman. A manager of software […]
-
It is said that formal agreements are for bad times. As far as everything goes well we can forget about papers even when there are some of these. Either way it’s all about trust. A question: what happens when a subcontractor doesn’t do their work well? Do you take a signed papers and count forfeits? […]
-
Somehow my recent discussions are mostly about estimating. Last discussion on PM Clinic happens to be on the very same subject. It reminded me about great technique which can improve your software estimates. It is called Evidence Based Scheduling and I’ve learned this from Joel Spolsky’s article. The basic concept is pretty simple. Jack the […]
-
OK, this one is controversial. Software estimating. How to do it good, or good enough? First of all, when talking about the subject we all can learn a lot from Glen Alleman who bring quite an uncommon perspective to the area as he’s based in industries which tolerate missed deadlines with much less patience than […]
-
Who should be a leader of a startup? An easy question. One of founders. Or even better each of them. They are naturally predestined to leading role. They got the idea. They own the company. They keep all things running. Now the more important question: what kind of leaders are they? Why is it so […]
Hi, I’m Pawel and I’m your host.
Leadership in Technology is a blog dedicated to wide variety of topics related to running a technology business.
Among others you will find here: product management, agile and lean, leadership, organizational design and more.
Search
Subscribe
Recent comments