know plenty of people who prefer more advanced source control system, but my belief is that many agile practices diminish the importance of advanced features like branching. Its not that the idea behind them is wrong, but I think agile team-building practices make scheduling per se much less important. Please leave feedback!) for H. MORE >>

much prefer Agile methods like Scrum over Waterfall because of how much less weight is given to “requirements” in Scrum. I’m not the first person to come to this conclusion, but over the years, I’ve really come to dislike the entire concept of a “requirement.” MORE >>

This is very similar to the role of the Scrum master in agile development. Today, I had the good fortune of sitting in on a lecture by Verne Harnish on how to increase the value of fast-growth companies. Verne is the author of Mastering the Rockefeller Habits and CEO of Gazelles Inc. Good point. MORE >>

Use Solid Agile Process for Estimating Development Timeline. At my last startup we eventually started using a process called "scrum," which is basically a framework for managing agile engineering projects. In scrum, however, after the first day you would say, "How much time do I think it will take to finish this widget?" MORE >>

And one of the reasons I advocate for Scrum is that as a process it values this role of project manager as “impediment remover” (known as the Scrum Master role). also see Scrum Masters being policeman pushing by-the-book agile (at least by the books they've read) - which haven’t been adapted for product organizations.” MORE >>