Coming from projects primarily conducted in the classic waterfall style – sometimes combined with some aspects of Scrum – I was really curious about learning more about the usage of Kanban. The questions we participants sought to be answered were: What is Kanban, and how can we use it to support our work?
I’m personally tired of hearing about how new, growing, successful businesses do things. I felt different about this Spotify presentation even though it fit the mold. Autonomy and collaboration are built into organizational structure.
It is a fact that some employees feel less excited or emotionally responsive toward their job. Here are some of the common reasons why people experience negative feelings about their work.
When you work on very talented teams, you will frequently know the answer to whatever the problem is well before the rest of the organization. When these conversations pop up, you should look a little closer to home. It is possible you have Smartest-person-in-the-room Complex.
Fist to Five (a.k.a. Fist of Five) is a simple tool for measuring level of agreement in a team. Often, this is far more expedient than discourse, even among those in agreement. For any simple question, such as the ones described as appropriate above, ask the team for a Fist to Five vote.
The tech industry needs to be more inclusive of women and people of color. It's about having the largest pool to draw excellence from. Sadly, most of the discussion, even the discussion that is advocating for a more inclusive culture, itself is divisive.
Because we know what it is like to read and debug a 500-line method. And we don’t want to go through it again. Because we’re sure the other guys’ code can use improvement. Even if they thought otherwise.
A few days ago I made the case that the most efficient code review process is one that deals with reviews within minutes of hours of the commit they pertain to. I didn’t dwell so much on the difference between pre-commit reviews (that until they “pass”, the commit can’t go in), and post-commit reviews (which suggest prioritized follow up work in the case of “fail”).
We need to be aware of any peculiarities of the real development process to select a tool that would be capable to replicate it. So, what are the things to note about the process that one would definitely need in the tool?
In an agile team, especially with continuous integration, we don’t notice handoffs. Continuous integration makes handoffs trivial. If we work together to achieve a feature, as in swarming or mob-programming, we don’t even have handoffs.
"Yesterday, I was in Sprint Planning…” I hear it once, and I’m suspicious. By the time the third team member says this, it’s clear the Daily Scrum I’m observing is broken. Everyone in the room knows we did planning yesterday—we were all there
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....