“What gets measured, gets done”. We all know this. By the way, did you notice that it says: “done”, not “done well”? We like metrics, because we base decisions on them. If we didn’t have them, then we would just be guessing.
For project managers things are decidedly more complex. Much of their traditional work around “when” is redundant, since we are aiming for stable teams and sizing work to the time work around “who” is also gone.
German parliment may be preparing to end future software patenting, and Subversion 1.8 is live! Plus, learn how to speed up your site with Redis and watch the funniest JavaZone parody trailer yet!
The pending changes list of TFS is a lie. It shows all files checked out for edit, not those with actual changes. A TFS power tools command can save the day.
About half way into the interview Dr. Dan starts talking about Cosmic Function Points. I almost sounds like a new age approach to Agile software development but he’s really talking about the complexity of the data flow between components in a system. It’s an interesting concept!
To be successful, organizations desperately need people who are both thinkers and doers. People who want to get things done, but always start with asking “Why?”.
In many ways, estimating project budgets or dates for agile projects turns out to be irrelevant. If you have a ranked backlog, and you finish features, you can always stop the project if you hit a particular date or cost.
There are so many reasons why continuously refactoring code is a good idea – in fact, it is a sound investment for the overall health of your codebase. So, what could be some reasons why we fear doing refactorings?
Working with legacy assets can be difficult. You will start out with fear, uncertainty, and doubt (aka the FUD factor) and you will probably question if it is worth going through the trouble of touching old code.
In Part 3, you had some knowledge of the team’s velocity. This is the option of when you do not have knowledge of the team’s velocity, because this team has not worked together before, or has not worked on a project like this before. You are all coming in blind.
Wrote earlier about the importance of refactoring and continuous alignment within the context of systematic reuse effectiveness. Reducing technical debt is an integral aspect of refactoring.
Having many projects open the same time, and working on them in parallel is a challenge. Ok, the human brain is not built for multitasking, but I still try ;-) . What I typically I end up in my Eclipse Problems View to have entries from multiple projects mixed up:
Pursuing systematic reuse the agile way? This primer will cover a variety of design practices to help your development teams. It covers:
An agile enthusiast who seeks excellence in software engineering. This is how Patroklos Papapetrou defines himself. Let's have a techdebt talk with this greek "software gardener" who recently published a very interesting approach on how to identify & remediate resign patterns with code metrics and agile practices, based on the original article written by Michael Duell.
You have options for estimation, once you have met the preconditions. If you don’t have the feature set in a ranked order, you are in trouble.
At the business level we often find "project pipelines" that become Kanban-like once Agile practices are embedded in the boardroom. This article considers this enterprise pattern...a "Kanban Sandwich" with a Scrum-like process in the middle.
If you missed last month’s webinar on How to Grow High Performance Teams Through Mentorship by Peter Saddington, we have attached the audio and slide deck below. Enjoy!
This week at the 1:1’s Paul and I started to push for the teams to build MVPs around a core assumption or two. We also brought in technical mentor and Telerik customer advocate, Dhananjay Kumar (DJ), to talk about hybrid apps and also give an overview of Icenium and Everlive for the technical co-founders.
Your teams are busy building services and service enabled processes – great! – how do you know if these services are built at the appropriate level of quality? Here are ten signs that your services might be accumulating technical debt...
I blame others and they blame me. The more difficult the problem, the more I need the help of others, the more I blame others and push them away.
So now that you know why it’s so difficult to estimate what do you do when someone asks you for an estimate?
“Get the Hell Out of the Building” week with a focus on Customer Development. Most teams went out and started to talk to potential customers about their offerings. We had a mentor, Joel Semeniuk, come in and spend all week with the teams to work on customer development and their business model canvas.
This misconception has gone to such an extreme that, some believe that if you are not using post-it notes then you are not Agile. This looks funny for many Agilists, but this belief is true with many newbies.
The original purpose of my blog was to pave the way for my first book. But 5 years later I have realized that NOOP.NL has become more than just a vehicle for my book projects.
You need to understand corporate culture before undertaking Agile adoption or Agile transformation. Here are some tips.