What process or methodology did we follow? “Do what makes sense!” Yes, that was the only thing that was told to me the first day I joined the team. No process, no compliance; only sensible things.
ATD 2013 was my first testing conference. I didn’t know what to expect. Sure it has “Agile” in the title, so it can’t be all about testing, right? Yet the agenda seemed a bit unfamiliar.
How does it happen that an individual gets an idea to come up with a product or an app? It quite often originates in this individual’s personal need to have an app that would help him or her do the things they need to do, or enjoy doing.
Even though there are hundreds of articles professing the beauty and efficiency of the one page résumé, not a day passes where I don’t see a five pager.
When I was younger I thought becoming a manager would be great because I would have all these “resources” to guide, direct, even bend to my will. Luckily I was never made a manager.
I hear many references to organizations wanting to follow the advice of Steve Jobs and to have only what he called "A Players". What's lost in that "sound bite" is that Jobs' went on to flesh out that notion that A players can come from many backgrounds, bringing talents from many different disciplines.
his is an outline of the problems that we have as an industry building secure software: why we fail at it, why Agile development is blamed for insecure software, and what we can do to build more secure software while still being Agile.
I have always found it hard to differentiate an Iteration from a Sprint, so much so that I commonly say they mean the same thing. They are synonymous. I use the two interchangeably. The difference is historical, the term “Iteration” originated in XP and “Sprint” in Scrum.
When I talk to people about working remotely the focus is often on the tools. I’ve noticed the real challenge is the working relationships and maintaining these even though we are hundreds of miles apart. Working effectively as a team means considering everyone's needs
For no reason other than LinkedIn communications are starting to irritate me, here's my personal LinkedIn Etiquette guide. Feel free to disagree with it all.
It’s been more than two years since I wrote “4 signs that agile is declining”. I gave a talk at Agile Eastern Europe (which hopefully will be up soon) that revisited this topic. Here’s a summary.
Many organizations have a system test team or integration team that is separate from the Scrum delivery team (the Design-Build-Test team). I sometimes get questions like those above from such organizations as they consider adopting an agile approach, particularly from large organizations that have to integrate the work of multiple teams.
It feels great. Yep, since we went remote, pairing has become really popular. No sharing body odour with your colleague, we just share our screens with a headset on. We may be separated by hundreds of miles but everyone is usually equally accessible.
SaaS onboarding seems like an odd concept to the uninitiated. Implementing a secondary system to integrate into an existing web interface would once have seemed like something that would be not only redundant, but barring that, impractical and too taxing.
This is the 3rd post in a three part series about quitting your job and working for yourself. Check out the first post about why you should want to quit your job, and the second post about the fantasies and realities of quitting your job.
Do I believe in program management—one person to coordinate the efforts of everyone—for large programs? You bet. Do I believe in project management? You bet. Am I one of those people who believe in agile project management for geographically distributed teams? Yes, sirree. How about projects and programs where people are clinging to their silos? Absolutely.
“Wet agile”, “the agile waterfall” and “the Agile-Waterfall Hybrid” … this controversial, mixed-method baby has as many names as formats. Some have received a lot of dedicated thought, are fit-for-purpose and manage to preserve the main benefits of the more pure methods.
Make sure you didn't miss anything with this list of the Best of the Week in the Agile Zone (week of Oct. 26 to Nov. 1).
Gathering requirements is an important part of any software professional's job. Learn about a few tools you can use to help this part of your career.
The truth is, the number of struggling projects far outweigh their successful counterparts. Why is this? Because sometimes developers are too smart for their own good.
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.
In this article we consider a hybrid agile approach known as Scrumban, which can potentially address both project and BAU work. Scrumban is becoming increasingly popular and has significant ramifications for project scalability.
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."
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.