Bill had two very different experiences interviewing for two different positions at two different companies: one as a software engineer, and one as a VP-level manager.
For a one week sprint, it’s possible to do Review, Retrospective, and Planning all on Wednesday morning.
By definition, any work that has not been completed to the satisfaction of the DoD remains undone. Taking work off a Product Backlog just because it is on a Sprint Backlog is therefore precocious and a mistake.
From software developer Curtis Lassam (who writes about comics and code) comes a comic series called Cube Drone. This is Cube Drone #2: Nyan.
I understand that you have to qualify large number of folks, at your very algorithmic-centric company, but when it comes to measuring what I do, a programming test isn’t a thing.
Coding (computer programming) is the art of creating anything from computer games and iPhone apps to computational models that help us improve health care. As our kids grow up, this ability to code will become as fundamental as reading and writing to their success, regardless of what occupation they ultimately choose.
Lean is more than just minimizing waste. A popular misconception of Lean is that it is suited only for manufacturing. In this article I will be discussing non-value added process and implementing Lean in software development.
Since the Agile Manifesto was published in 2001 much has changed. It's time to rethink yesterday’s manifesto in a new light and deconstruct which concepts were home runs and which still need to evolve.
Most companies have some variation of the same process for interviewing developers. There are a myriad of reasons for the candidate to say No. The important thing is for you to learn from their NO.
The existence of silos in large companies is fairly common. But simply knowing that silos exist doesn’t help too much. The operable question for everyone operating in these environments is: What can I do to remove unnecessary silos?
So, regardless of whether a change is imposed by the management of an organization, is requested by and driven by those most affected by the change, or any combination of both, the fundamental mathematics remain the same.
Hopefully these articles have helped the reader decide if a) agile will work for them and b) if they are already working in an agile way.
People aren’t resources! People finish work. If you don’t want us to finish projects, let’s decide which projects not to do. Then we can re-allocate people, if we want. But we don’t start with people. That’s crazy.
From software developer Curtis Lassam (who writes about comics and code) comes a comic series called Cube Drone. This is Cube Drone #1: Elevator.
I posted my slides for my Agile 2014 talk, Agile Projects, Program & Portfolio Management: No Air Quotes Required on Slideshare. It’s a bootcamp talk, so the majority of the talk is making sure that people understand the basics about projects. Walk before you run. That part.
The web is no longer a way we push some static content; it’s more about telling a compelling story, making people come to you and buy stuff
During retrospection, when evaluating the quality and value of our artifacts for Epic, Feature and Story decomposition a common theme for our scrum teams is that these artifacts are by design barely sufficient and as such are ephemeral and provide no enduring value.
I like this system because I find the visual aspect very important. It gives me a sense of accomplishment, which I value. Since most of what I do is creative work, fighting procrastination and “resistance” is high on my list of priorities, and visual tools help me with that.
What does aggressive decoupling look like?
What does aggressive decoupling look like?
When most people think about their careers, they tend to think 5 years out and picture the job they would like to have. This works well when you know with precision where you want to be, but what happens if your future isn’t quite so certain?
I’ve interviewed a few people for jobs at Monash University, and there’s always someone who comes out with something surprising. Here are some real examples.
I’m often surprised how many software developers neglect to do any salary negotiations at all or make a single attempt at negotiating their salary and then give up and take whatever is offered. Here's how you should do it.
It could happen when you clone a Git Repository with submodules, issuing a git submodule update command, that you are prompted with this error error.
Never start negotiating downward until some objection is provided, and don’t mistake the silence of an interviewer as an objection.