And they need to start out implementing the whole package, not just bits and pieces that they like or feel comfortable with.Half-assing an Agile methodology is no better than half-assing a database architecture — if you don’t think it through from the beginning, you’ll get bit by some fault or failure shortly down the line.Again, if you come across a broken link, we want you to let us know.

I expected to have this working in 5 minutes but it's been over an hour. It is not a solution but I have had success with the tor browser bundle.

Unless you have a good reason to route all your traffic through tor then i wouldnt really recommend it as speed is severely reduced.

This blog is devoted to providing tips, tricks, and hacks to make people better, more clever Product Managers.

I followed instructions found at this question (but since the config file was 404, I used a config from Tor Polipo 5 Minute Install Guide Ubuntu 11.10). I set my network to manual proxy & added the for all but socks (which is 9050). Still, neither Google Chrome nor Firefox are using Tor when I browse.

Project management is not always the biggest core competency of a development team — solving problems is usually their core competency, and more often than not, project management comes in second place (or third, or fourth).

The single biggest failure that I’ve seen in Scrum teams is simply a lack of real understanding about why Scrum says to do things the way that they do.

If you’re one of those people for whom either Agile or Scrum doesn’t seem to be working, here are some hard questions to ask yourself and your organization — “The fault…is not in our stars.

It is ourselves…” I’ve touched on this topic in a couple previous posts — Agile is not just something that organizations just “do”, it’s something that they are…or that they aren’t.

It seems that lately Agile (and Scrum in particular) have become the latest targets of non-stop complaints and criticism in the Product Management and Development worlds.

I’ve read articles that talk about how “Agile is destroying the business” or where “Scrum is a career-limiting methodology that only creates generalists.” Neither of these are necessary conclusions from the data provided, nor are they necessarily a reflection of weaknesses of the Agile principles or of a specific methodology — more often than not, they’re a reflection of a certain culture or work environment that itself is fighting against the fundamental tenets of Agile and Scrum.

And that this is a baseline set of practices that one should try out first, and then adjust as needed to fit the needs of the team and of the organization as a whole.