Mitch Pronschinske04/07/13
3303 views
0 replies
More about asm.js from John Resig and also some amazing benchmarks for comparing a ton of different web frameworks. Plus Rackspace is suing patent trolls and a blogger explores what is really necessary in a programming language.
Kane Mar04/07/13
2181 views
0 replies
This is the second issue of James Brett‘s 5 Questions. From the first issue of 5 Questions ”The ideas was to ask five specific questions to members of the Scrum community and post the their replies.” In issue 2 of the five questions series we hear from one of the godfarthers of Scrum Ken Schwaber.
Johanna Rothman04/07/13
232 views
0 replies
When a Product Owner wants to change the iteration contents mid-sprint, and the Product Owner realizes this is a no-no, look deeper for systemic forces at work. It won’t be an easy answer, and will likely be a combination of answers. If you are lucky, it will be a relatively easy-to-diagnose problem
Esther Derby 04/07/13
1631 views
0 replies
I have no doubt that retrospectives that are too short, don’t result in action / experiment, or fail to delve beneath the surface are a waste of time. But what about earnest retrospectives that focus on an area of concern, examine data, analyze underlying issues and result in action?
Tobias Mayer04/07/13
1089 views
0 replies
Knowledge work is not linear. It is chaotic, and rife with feedback loops. It swirls. I believe the activity of software development is more storm-like than it is stream-like. Why does this matter? Maybe it doesn’t, but I sometimes worry that the metaphors we choose guide the work that we do.
Johanna Rothman04/06/13
2474 views
0 replies
For programs, don’t you want longer iterations, so people don’t have the overhead of planning, of retrospectives, of demos, of all of that?
Anders Abel04/06/13
1260 views
0 replies
A year ago, during the startup of a new project, I wrote a series about scrum and the context around a scrum project. The project is now finished and it’s time for a retrospective, evaluating what worked well and what didn’t.
Johanna Rothman04/05/13
1196 views
0 replies
When a Product Owner wants to change the iteration contents mid-sprint, and the Product Owner realizes this is a no-no, look deeper for systemic forces at work. It won’t be an easy answer, and will likely be a combination of answers. If you are lucky, it will be a relatively easy-to-diagnose problem
Leigh Shevchik04/05/13
3879 views
0 replies
In his prestigious career, Ward Cunningham has worn many hats: inventor of the Wiki, co-creator of Extreme Programming, Code For a Better World Fellow, CTO, published author, and more. But we think he may have save the best for last — Staff Engineer at New Relic.
Wayne Beaton04/05/13
4098 views
0 replies
Almost all Eclipse Git repositories are mirrored at GitHub. The mirrors were initially set up two years ago by the nice folks at GitHub with relatively little input from us.
Hamid Shojaee04/05/13
5517 views
0 replies
Here are 10 articles from 10 different authors that provide valuable advice for Scrum teams. These articles are in no particular order, so feel free to skim down the list and start with the ones that are most relevant to you.
Johanna Rothman04/04/13
893 views
0 replies
I once led a workshop for real estate project managers about how to define success and manage some of the early-in-the-project risks. We discussed issues such as the Hudson Bay start, context-free questions, release criteria, iterative planning, interim milestones, and inch-pebbles.
Esther Derby 04/04/13
1341 views
0 replies
There is much more to empowering a team than simply stating “You’re empowered.” Consider the three Ws of empowerment: “what,” “when,” and “why” when creating boundaries that define which decisions are the team’s and which need management approval.
Paul Hammant04/04/13
3773 views
0 replies
Simply put, Maintained Divergence is where you have two branches that have a common origin, and while merges may happen in either direction, there are differences that remain over time.
