The #NoProjects meme is catching hold, mostly as a rejection of forming project teams. Meanwhile I’m intrigued by the ideas put forth by Carmen DeArdo of Nationwide Insurance during a webcast on DevOps on Tuesday. Ok, #NoProjects people, tell me what you think of this approach.
Because Agile development teams work from a backlog of stories, one way to inject application security into software development is by writing up application security risks and activities as stories, making them explicit and adding them to the backlog so that application security work can be managed, estimated, prioritized and done like everything else that the team has to do.
Ever been a part of or observed just a really terrible Daily Scrum? Tobias Fors has, and he tells the story of it in his blog post "The Worst Daily Scrum Ever."
Every week here and in our newsletter, we feature a new developer/blogger from the DZone community to catch up and find out what he or she is working on now and what's coming next. This week we're talking to Sean Hull, author, speaker, and web performance and scalability expert.
I had a meeting with a stakeholder who stated “I bet you wish I wasn’t in these meetings”. My reply was that it would be much worse if she came in at the end of the project and told us we had just built the wrong solution.
I have stepped into my 12th year of practicing Agile methods. Even now, organizations are looking at Agile as a silver bullet without fixing the root causes. The issue is that Agile was born mostly to banish the problems coming out of the Waterfall model.
The larger the effort, the more we need to estimate. And, the more your estimate will be wrong. The more we estimate, the more we have schedule games. That’s why I suggested you use agile approaches. You can break things down, and iterate.
What I mean by transparency is about letting the sunlight in to your overall operations, by default. In the case of Healthcare.gov, one of the numerous contractors applied this on front-end development, but the entire rest of the supply chain did not.
I picked up Daniel Kahneman’s "Thinking Fast and Slow" after a recommendation by Mike Jones in early 2013 – it’s taken me quite a while to get through it. The book starts by describing our two styles of thinking…
Most hiring issues can be broken down into one of three categories: constraining factors, improper vetting, or lack of awareness. The following sections outline the problems found within each.
This year’s Agile By Example (or simply ABE) was my 2nd visit to this conference, I’ve missed only the first edition. Last year I felt really refreshed by the conference built not only around code, coding, testing and developing software.
The Puritan Gift is not a book primarily oriented to programmers, but to knowledge workers and managers in general. Its goal is to show, through history, the evolution of American and Japanese management over the last two centuries, its strongest moments and its decline through the Cult of the so-called Expert and of corporate consultancy companies.
This week, for the first time ever, DZone is releasing the first in a series of checklists for software developers. Our first checklist covers Test-Driven Development (TDD). To complement this exciting new endeavor, I dug through the DZone archives and put together a Top 10 list of TDD resources.
In an open, self-regulated market, the tools gravitate toward their corresponding, welcoming environments. Low-trust tools go to low-trust, highly regulated environments, and high-trust tools are used in agile, high-trust cultures.