In a practical software world, when you’re working on a big project; one of the hardest thing is Software Estimation. Team members generally can’t predict what to estimate from stories. And also PMs (Project Manager) or SMs (Scrum Master) often get confused about estimating and committing. Anyway, since I couldn’t find direct information about this topic, I wanted to share my thoughts about Software Estimation.
Agile Processes, Flaccid SCRUM and Debt Metaphor
Today I was reading an article that Martin Fowler has recently added to his blog like couple months back. The article was about Lean (Scrum) process and its poor applications by missing the point.
What is This Code Coverage Thing?
Good question if you really don’t know what it means :) I’ve more than 7 years of software development experience and to be honest, I’ve never seen a company who uses code coverage as a metric unfortunately. We’re developing a lot of beautiful software and in most cases we’re ending up with lots of code messes :( You can argue on why it happens like this, but I’m not gonna go into that today. Let’s get back to the main topic:
