This essay is inspired by Ken Schwaber’s unSAFe at any speed blog. While I’m very much with Ken Schwaber on the subject of heuristics, thinking for yourself and sticking to the principles of agile, there are some deeper things to that than management vs. software developers, or RUP vs. agile oppositions.
Tasktop Mik Kersten, Tasktop’s CEO presented: “As distributed as it gets: 10 Agile best practices from open source” and Dave West, our Chief Product Officer presented: “Agile ALM – A horror/feel good/fantasy story“.
Ted Neward become something of a resource on programming interviews. Here are five pieces of advice he's compiled that will help your company improve its programmer interviews.
Given-When-Then is a style of representing tests - or as its advocates would say - specifying a system's behavior using SpecificationByExample. It's an approach developed by Dan North and Chris Matts as part of Behavior-Driven Development (BDD).
Check out this week's Developer Humor Comic: Technically Correct! A bitingly insightful look into the tendencies of IT folks and business managers.
DZone speaks with Ebba Kraemer from Hansoft to ask about how far Agile has come in the last year, and where it will be going in the next year
Recently I learned many things about comments, making me ashamed of my own code and comments. Many people may already know much about comments, if you are not among them, read on.
A long time ago in a galaxy a dozen or so miles away, I learned about Extreme Programming. I was actually doing Pair Programming when I heard about this crazy XP concept, so it wasn't really a stretch to do it on a regular basis.
I found a blog post introducing an interesting beta app called WorkPlace.io. I haven't gotten my invite to join it yet, but it seems pretty interesting. It's a mobile office management and metrics app.
In this video, DZone speaks with Hamid Shojaee from Axosoft. DZone.com attended the Agile Conference 2013 in Nashville to speak with industry leaders about how far agile has come in the last year.
Every so often, managers want to compare teams. But comparing teams is not useful. There is no reason to do so.
If I’m being honest, I feel as if I don’t know much about scaling agile. But when I think about it, I think the issue is really: What do you mean when you say “scaling agile?” It seems to me you might mean one of three things...
This is not a new topic for sure but I have to write few words about it. The main reason for this article is the abuse (wrong understanding) of agile I have noticed while talking with various project managers in the past two weeks.
This was the final week of AccleratorHK, the hardest week of them all. The teams had to run their businesses, review and sign all of the investment paperwork from Telerik, and prep for Demo Day!
It takes more than talent to make a great product. You also have to focus on the right things, in the right order, with the right people at hand. Learn the key points for successfully developing product so you can make the most progress on your big idea.
Here is the talk that Dennis Stevens and Mike Cottmeyer did at the Agile2013 conference. The talk basically went over how to create safety and visibility for management when doing an enterprise wide agile transformation.
Selected quote: agilists believe that a process should be grown throughout a project, beginning with a bare minimum of a few practices. RUP tried the opposite approach, defining many practices and then suggesting that the unneeded ones can be removed. (I have often compared this approach to the purchase and subsequent dismantling of a Boeing 747 with the purpose to turn it into a bicycle for shopping.)
John Esposito, editor at DZone.com, attended Agile Conference 2013 in Nashville to speak with industry leaders about how far agile has come in the last year. In this video, John speaks with Dave West from Tasktop.
As agilists continue to deliver deliver on the principles and promises of the 2001 Manifesto, developers and managers often debate the definition of 'done'. Urbancode's Eric Minick uses concepts and methods of DevOps to clarify and concretize the problem, offering his thoughts on the current state of software development methods, metrics, and tools.
This talk intends to show the real-world cost of high technical debt and an agile approach to debt reduction, based my experiences from a product development project that fought actively against the huge accumulated debt.
Michael Sahota and Olaf Lewitz talk about their newest venture, Temenos - The Healing Container: a way to deepen trust, interaction and health of team members.
Jim Bird went to Agile 2013 last week in Nashville to look for answers on how Agile development ideas and practices could help more with high integrity, high assurance development; scale to handle large projects and programs; and improve the working environment for mature, high performance teams.
This is an interesting read with the main value being in the links to these old papers that show how many of the ideas behind Agile are not new. It gives you a good idea of the problems we keep encountering throughout history.
Check out Peter Verhas' article outlining his own experiences with UML. If you use it properly, it can be integrated into an agile workflow.
DZone's coverage of Agile 2013 continues in this video as we speak with Jonathan Thorpe from Serena Software about the trends in agile principles and practices.