Make sure you didn't miss anything with this list of the Best of the Week in the Agile Zone (Apr. 11 to Apr. 17). This week's topics include the relationship between golf and agile, the fate of eXtreme Programming, and how to properly handle management conundrums while implementing agile.
“Ready for Test” usually means it’s either deployed (and yet to be tested) or waiting to be deployed. Either way, not much is happening to the work sitting in this column. Basically it’s waste, and remember, waste is very bad.
According to the Bureau of Labor Statistics, women comprise 47% of the general workforce. Why then, does the same survey say that women comprise only 26.1% of all "Computer and Mathematical" occupations?
The point is to create a repeatable, empirical, continuously improving process. If we can create a reliable, successful process (which here includes culture and practices), we can get reliable, successful results.
TEALS, is a volunteer program where software engineers teach CS to high school students on their way to work. Basically, the schools schedule the CS class for first period so that the engineers can make it into work by 9:30. One group is teaching at a school that is 100% English-as-a-second-language students.
There are lots of management problems that need to be taken care of in any project. Agile spreads some management responsibilities around, but doesn’t make management problems go away. Projects can’t scale and teams can’t succeed unless somebody - a project manager - takes care of them.
The sport of golf is a mathematician's dream. Why?
In a rapid evolving industry, like software development, using Scrum is a really good solution to constantly verify new technologies in your team, with little risks, but with real world feedback at the same time.
I regularly hear from and read about technologists in a career rut. Unless one is both lucky and adept at predicting the future, experiencing some temporary stall can happen to professionals at any career stage.
What do you do for geographically distributed teams, if you want to move to agile? First question: does the team want to move to agile? Or, does the management want to move to agile? I am serious.
When organizing your own workflow, modularity increases your ability to scale testing. Total elapsed time is much lower. You can do many tasks in parallel and then combined at the end. This includes testing activity.
When I was a young software programmer, I had to develop features with estimates given by more senior programmers.
Nowadays everyone is agile. Or at least they say. Most organisations use Scrum. Or they claim to do it, while still doing waterfall. But why is the industry so focused on Scrum? What happened to eXtreme Programming? Why did we loose the XP practices? Is it too extreme?
There was some hubbub a few months ago when it was revealed the Executive Director of the UK’s Year of Code initiative can’t code. Apparently a number of people don’t agree with the idea that competency in a domain is a requirement to manage that domain. I find this idea infuriating and it can only end poorly.
Make sure you didn't miss anything with this list of the Best of the Week in the Agile Zone (Apr. 04 to Apr. 10). This week's topics include discussions of the prototype of future knowledge workers and software developers, a video about how meetings feel for engineers, and why you shouldn't estimate spikes.
It is important for technology companies to think of ways to boost their employee’s morale and help inspire them so that they can become more productive in their work. To help leaders and even managers out there, here are some amazing ways that they can use to boost their employees' morale.
Everybody makes mistakes, otherwise we would all write bug free code. For most of us a mistake can be fixed and doesn’t have too serious consequences.
When Lean goes awry, Toyota- the company and its principles, practices, and culture- is there to set things straight. Agile has no such entity. Instead, we have hundreds of “Agile” shops who attribute success to some (non-)Agile practices. The corruption and perversion here is inevitable.
While every intranet is different, there are some common factors that need to be considered so your intranet supports your business requirements.
There is a simple heuristic, which you can use to determine the top priority activity you can engage in-at any given moment.
I believe any technical leader has a responsibility to review all the code that goes into a codebase.
To do a great job, product owners need a strong ScrumMaster at their side. This post explains the differences between the two roles, what product owners should expect from their ScrumMaster, and what the ScrumMasters are likely to expect from them.
We work with our brains rather than our brawn. We generate value because of what we know and what that knowledge allows us to do.
The other day I was watching Kent Beck’s talk about Ease at Work. It touched me deeply and I could really relate to what he described.
If you implement all of your spikes for each release in a “Sprint 0″, you could estimate them. If you do, do so always so that your velocity will be reliable. Spikes are, like defects, generally harder to estimate correctly relative to user stories. It’s best to time-box them.