Agree with the first part. I was mainly referring to why is it ok to out him because he's a billionaire - doesn't seem to be in the public's best interest, regardless of one's status. Similar to the argument Gawker made…
I happen to merely be a hundred-aire, so take this FWIW, but I don't understand what Thiel being a billionaire matters. It seems natural for someone to want to use the power within their means to right a wrong (in their…
> It sounds like you dont really know what the purpose of scrum is. Agreed. People lose sight of this being a "framework" far too often. Make it fit your needs and run with it.
I don't see any comments from the Jobs' camp about inaccuracies, falsehoods, etc. that came about with Zuck. They seem to just not like that his lesser known (to the greater public at least) side is being publicized.
It just depends on the process you put around it. Our team wasn't huge - ~13 if you include QA - but effective use of labels and "task" state management made it great.
We use vanilla Jira and I find it painful - over-reliance on modals, slow JS calls, etc.; I do enjoy Source Tree. As a PM, Pivotal Tracker (used in a previous life) is one of the best work-tools I've ever used.
One of Uber's architects talking about how they're handling that over via InfoQ http://goo.gl/bAoFHi
Agree with the first part. I was mainly referring to why is it ok to out him because he's a billionaire - doesn't seem to be in the public's best interest, regardless of one's status. Similar to the argument Gawker made…
I happen to merely be a hundred-aire, so take this FWIW, but I don't understand what Thiel being a billionaire matters. It seems natural for someone to want to use the power within their means to right a wrong (in their…
> It sounds like you dont really know what the purpose of scrum is. Agreed. People lose sight of this being a "framework" far too often. Make it fit your needs and run with it.
I don't see any comments from the Jobs' camp about inaccuracies, falsehoods, etc. that came about with Zuck. They seem to just not like that his lesser known (to the greater public at least) side is being publicized.
It just depends on the process you put around it. Our team wasn't huge - ~13 if you include QA - but effective use of labels and "task" state management made it great.
We use vanilla Jira and I find it painful - over-reliance on modals, slow JS calls, etc.; I do enjoy Source Tree. As a PM, Pivotal Tracker (used in a previous life) is one of the best work-tools I've ever used.
One of Uber's architects talking about how they're handling that over via InfoQ http://goo.gl/bAoFHi