Note: At no point are we asking about local branching (on your local workstation with Git, etc). This is all about branching on the remote repository. That is if your company has one, and isn’t completely distributed, with no central repo.
Apart from Android, Google does Trunk Based Development (TBD) everywhere. They made the review process as lean as they could, by making reviews ordinary and continuous.
Agile development has a serious Appsec problem. Most Agile development teams suck at building secure software. But one of the reasons for this is that Appsec has a serious Agile problem.
What does a developer gain by embracing Scrum? I’m a strong believer of Scrum, but some time ago, I got my beliefs questioned. That is always good because it forces one to think them over again and reason about why one believe in certain things.
Developers have their own cynical kind of humor. Consider, for instance, Geek and Poke’s view on how to insult a developer. But there’s a better humor than posting stuff on a website. There are source code comments.
Last week one of the teams I coach was given a day to build a proof of concept for a new business idea. I thought that #MobProgramming might be a good fit for the day’s activities, so here’s what happened.
Anyone who has done any software development has heard it. The sentence that makes you feel like getting a shotgun. It’s a client shouting “How hard can it possibly be to add that feature? The last one you implemented in a couple of hours and this one looks like the same thing!”.
It is important to remember in all this discussion that software is a derived demand. Nobody wants software for its own right, they want it to achieve some other aim.
This week we're talking to Claus Viscuso, open source advocate, OO software developer, and developer evangelist at Kii focusing on MBaaS and Android.
In a distributed Agile project, team members may not often see each other face to face, but must work collaboratively toward a single outcome. The reasons for distributing your Agile team will be different for each organisation.
Lean thinking describes seven classical sources of waste. Here are the seven wastes of enterprise information application architecture:
I have developed a new goal-oriented agile roadmap — the GO product roadmap, or “GO” for short. GO is based on my experience of teaching and coaching product managers and product owners, as well as using product roadmaps in my own business.
When you ask for permission to take a vacation, you are implicitly saying that work is the higher-order item in your life. I cannot tell you how many people fall into the trap of thinking that they should schedule their vacations around their work schedule.
I have blogged before on the subject of “What is Agile” - I’ve even expanded on that blog in an unfinished piece of writing called “What is Agile? Perspectives on Agile” - but sometimes I think it's just sex....
The corollary to Vertical Divide and Conquer is Conway’s Law, which tells us for our vertically aligned business and technical capabilities to be truly successful we must also re-structure our organisation so that our development teams are vertically aligned with singular responsibility for specific business capabilities.
Nearly every reason put forward to offshore your development team gains more value from first reviewing and addressing other areas within your business that need real attention before considering offshoring.
A new etiquette has emerged for remote working. Without it uncertainty can leave words unspoken and replaced by assumptions that lead to conflict.
The subject of keeping fit creatively is tied to productivity in most “booster” books, but productivity and continuous problem-solving are two different things. I’ve come to this conclusion over many years of what I call “living and exploring”.
Since I’m bringing my TDD spaceship to Agile Testing Days (October 28th through 31st in Potsdam) and Agile Eastern Europe (October 4th and 5th in Kiev), I’ve created a short video depicting in detail what led me to do this.
It’s been two months already, and Agile Eastern Europe is long past. Which is why it is a good opportunity to put my talk there “Not the agile I used to know” front and center.
Here is my current thinking on how I communicate and consult around Agile. For me, it’s all about understanding the desires and wishes of the organization I am working with and mapping that to an approach to Agile that fits their context.
Today’s internet is rife with fascinating subcultures, many I’d never heard of. Parmy’s book on Anonymous takes us to the door of all these places, and gives us a candid peak at what goes on there. Kids these days are up to no good!
Carrying on from my previous posts applying the economists' tools to thinking about software development (Supply & Demand in software development and Software supply over time). In this post I want to see what happens when we apply Agile...
Although many successes are seemingly interlaced with failure, some find ways to endure and grow. Why is that? One common area of growth is a developer's analytical abilities. Skepticism can be a valuable tool in a developer's tool belt, but like most tools it is only needed at certain times.