Agile Practitioners 2015 is starting its way, and the first step is the Call For Papers! The Agile Practitioners conference started 4 years ago, and is an actual effort by the community. I’m proud to be part of the organizing committee, after presenting at the last 3 gatherings.
If you’ve been paying attention to agile at all, you’ve heard these terms: pairing and swarming. But what do they mean? What’s the difference?
Interruptions seem a central part of modern working life. Whether it’s open plan offices or the influx of digital tools into the workplace, a distraction never seems far away
Since Scrum is an iterative process, you can have great success by focusing on things that you can say with a fair degree of confidence, while still allowing for some uncertainty in all planning and estimates.
Almost every New Product Introduction process includes some placeholder slots to talk about risk. Everyone knows enough to put mitigation plans in these slots. But those mitigation plans are drafted and then ignored by the vast majority of managers.
When you are making GitHub commits you have to provide a story that explains the changes you are committing to a repository. Many of us just post 'blah blah’, ‘what I said last time", or any other garbage that just gets us through the moment. You know you’ve all done it at some point.
So, where did our new event fall on a scale compared to the others? Did I feel like attendees received value and did I feel like we got a good return on our investment? Let me give a little comparison.
It's dangerous to link to lines or blocks of code on Github without explicitly specifying the commit hash in the URL. This emits the Github URL to the HEAD commit on the current branch, specifying the commit hash in the URL
"Release!" is a card game about making software inspired by development strategies like Lean, Agile, and DevOps.
Proponents of the Waterfall Model suggest that by doing all the design up front and making sure that each part of the process is correct before moving onto the next part, means that bugs are found sooner and therefore costs are reduced.
In my role as technical editor for agileconnection.com, I have the opportunity to read many terrific articles. I also have the opportunity to review and comment on those articles.
I’m going to be volunteer teaching AP computer science this fall at a NYC high school! Aside from actually prepping them for the AP exam, I’ve been thinking about how to share the programming culture I love with the students. Off the top of my head, I’d like to tell them about:
Traditionally, a product strategy is the result of months of market research and business analysis work. It is intended to be factual, reliable, and ready to be implemented. But in an agile, dynamic environment a product strategy is best created differently.
Imagine walking into a library, and having to walk up and down the aisles trying to find the book you want. Imagine walking into a hardware store, row upon row and shelf upon shelf. But nobody has put any signs up. Do you document your code libraries and keep an index?
I was fortunate enough to recently be accepted to the inaugural php[world] conference. Shortly thereafter, a friend of mine within the community inquired about submitting to and speaking at conferences. I thought I’d post the resources I shared with them here for others interested in the same topic.
The transition from individual contributor to management is probably a bit selfish for almost everyone. In that moment when your responsibilities and title change, you will naturally focus your attention on you.
I [participated] in a panel towards the end of the one-day event focused on the prospects for Process Mining as a discipline and as a technology market; but I was also keen to hear the practitioner stories which made up a large proportion of the event’s schedule.
Validation is an engineering activity. In many ways it’s very much how engineers tell a product, “you’re awesome!” Unfortunately, many people don’t really understand what engineering validation really is.
Why not turn all that company jargon into a knowledge goldmine and create a wiki that can contain them for every employee to view, add or edit to?
For most of my software development career, when I worked for a company, as an employee, I had the dream of someday being free. I wanted to be able to work for myself. To me, that was the ultimate freedom.
This week I launched agilepatterns.org to help meet the challenge of enterprise scaling. In this posting I set out the rationale for doing so in terms of recent high-profile IT failures, and the need for genuine sponsorship for deep organizational change.
Lets have less talk about “The Scientific Method” and more talk about “Tidying up the Kitchen” - or is it better in French? Mise en place…. come to think of it, don’t the Lean community have Japanese word for this? Pika pika.
It’s been quite the summer for debunking widely held beliefs. Last month there was a broohaha over an article in New Yorker from Harvard academic Jill Lepore that attempted to poo poo Clayton Christensen’s widely heralded thesis from The Innovator’s Dilemma.
Rituals act as social glue, help pace your work, and foster discipline. Like your regular morning coffee, they give your team structure and stability in an ever changing environment.
Make sure you didn't miss anything with this list of the Best of the Week in the Agile Zone (July 4 to July 11.) This week's topics include scaling agile, dev of the week, the bystander effect, whether developers need degrees and kanban.