Many software developers I’ve talked to have expressed interest in the idea of someday either starting their own business, or in some capacity working for themselves. Before you do really quit your job, you should first understand why it is a good idea to quit your job.
This post is an excerpt from my new book, Conversational Git. The entire book is available online and its source is on GitHub. It’s designed to be a quick, accessible introduction for experienced developers. I’d be delighted to hear what others think.
Maintaining focus has become a such sticking point for so many. How do we keep it? How is it so easily lost? What tools can we use to find it, induce it, or retain it? If you’re constantly seeking focus and it seems nowhere to be found, you may need to ask yourself: how driven are you, truly, in what you do?
Scrum took over when more players started promoting “Agile” as it had stronger and clearer management. The ‘My Supply’ project at a TW client was in back 2002/3, and fully XP.
The average developer makes hundreds of decisions every day. This applies to programmers of all types including newbies, seniors, leads, and architects. How we make these decisions can make all the difference.
A couple months ago I started a series of posts about communication (see Non-Violent Communication for Agile Teams). The concept of non-violent communication has been introduced and championed by Marshall Rosenberg in his notable book.
Abi Crafter at Countersoft liked my “11 Myths and 2 Truths of Agile” blog entry so much he turned it into this Infographic. Thanks Abi!
Guy Lawrence – former CEO at Vodafone – tells of an organizational transformation effort that is intrinsically tied to office renovation – he says: “Conventional offices and working is dead”. The motivation for undertaking these sweeping changes is to have people from Generation Y (born after 1982) actually want to work at Vodafone.
A kegerator is a staple of the modern startup, and smart tech businesses know that it's a great way to attract talent. Developers love beer. But does it make a workplace unsafe, less productive, or encourage harassment?
Disruptive technologies, and disruptive practices, can cause good managers to fail. This Chapter explains why a new management model is imperative and characterizes the market ecosystem in which software development teams must operate.
A while back when I was working in a global banking organization we requested two virtual machines for development and testing. Why did it take so long to deliver virtual machines, and why could they not deliver consistent, working machines?
Scrum Teams who follow a system's journey into service often find that work becomes more Kanban-like. In this article we examine the challenges and gotchas of moving from a project context to "Business As Usual".
If you make your project portfolio decisions based on money, estimated cost, you too will have Sony’s problems. This is why cost is the wrong question to ask. You want to ask the value question, “How much value will this project provide?”
As lean and agile development methods are becoming increasingly proven in many software development industries, the interest for large scale agile transitioning programs is booming.
I am just waiting for the day I hear a developer turn around the words of my grumpy old Color Sergeant and say back to the Project Manager - “It’s called an estimate because it is one. If it was meant to be definitive it would be called an ‘Exact’”.
Discover what a 80 year old book can teach us about dealing better with people. Find old solutions for our newer communication problems.
An intuitive guide to efficiently track and manage projects in an agile way using GreenHopper for JIRA.
Agile is a set of values, principles, techniques and frameworks for the adaptable, incremental & efficient delivery of work. They can be applied to any type of work including finance, sales, HR, marketing, corporate strategy, leadership, and more.
A practical primer on how to manage successful software development efforts.
There have been a lot of words spoken both in print and on the Internet about how to be more agile, and it can be hard to filter. I distilled my experiences down into my own hopefully-pithy maxims. Call it Bumper-Sticker Agile.
Anyone involved with hiring entry-level technology professionals is aware that students are being prepared by schools for how to do work in the industry, but are often ill-prepared on how to find work in the industry.
I’ve contemplated things around Kanban recently, and here’s another interesting perspective. It might help make more sense of the Kanban method as a method for managing knowledge work, and software development work, in particular.
The minimum viable product (MVP) is a powerful concept that allows you to test your ideas. It is not to be confused with the minimal marketable product (MMP), the product with the smallest feature set that still addresses the user needs and creates the right user experience.
When we see only 27% of software developers are women in a world of 50% women, the fact that women are historically discriminated against is evidence that the effects of their historical oppression haven't yet been corrected
Do you have any stories showing how a few micro-habits have transformed a team’s productivity? There seems to be no written repository collecting such developer micro-habits together, and nor is there any obvious forum in which they are explored, shared and discussed. That seems a shame, and a huge waste.