The three pillars of Scrum are transparency, inspection, and adaption. However, using documentation as the main way of achieving transparency is perhaps not as good an idea as it may seem. In this article, find out some of the reasons why documentation may still be propping up barriers between different departments and how to break down silos.
Is your Scrum implementation failing? We could know the reason why. Read on as we explore this different kind of agile software development framework.
Forget boring, stuffy meetings: this is your team’s daily synchronization tool.
A response to Gavin Kings Methodology Luddite Manifesto, in which the Ceylon creator disparaged certified scum masters.
Automation specialists arago have open-sourced their two-year-old internal project management tool, Rike.
A strangely active Sunday for stories can only be down to one thing – April Fools Day. Here’s a collection of the best japes…
Atlassian JIRA 5 has been released today, pushing the envelope for issue trackers. Jon Stevenson tells us more about what it can do
The latest issue of Java Tech Journal – the free PDF magazine that delves deeper into a topic from within […]
JAX London returns for its third installment, with a full timetable of tutorials, panels and sessions.
Roman Pichler discusses the role of the product owner in Scrum.
Karl Scotland explains why people and processes are equally important in software development.
Getting a real “team” is a massive competitive advantage, one that Scrum gives us the opportunity to harness, so why is it so hard?
We allow teams to fully define their own processes be they Scrum, XP, DSDM, Lean, Waterfall or some hybrid and then we allow them to regularly reflect on their processes, improve and change.
The latest issue of JAXmag sets out to answer those burning, Agile-related questions.
