Archive for the 'Software Process' Category

Generic Isn’t Always Better

17Aug09

I saw a tweet recently that read ‘Use of “general” and “flexible” are design meeting smells’.
The truth is, words like “generic”, “general”, and “flexible” are pretty loaded words. Like the words “architect”, and “agile”, these words have different meaning to different people and unfortunately are very often misused.
The word generic is also a very [...]

Agilists and Architects: Allies not Adversaries Presentation

26Jun09

Martin Fowler and Rebecca Parsons speak about the challenges of Enterprise Architecture in agile environments:
http://www.infoq.com/presentations/agilists-and-architects

Throw-it-Over-the-Wall-Mentality

03Jun09

I’ve struggled with this throughout my career, but it’s never made sense to me until recently.
A colleague said something about operating in isolated environments so that one skill-set does not influence another skill-set. He was referring specifically to analysts not having access to development resources so that the requirements gathered from the client are [...]

Justifying Repayment of Technical Debt to Management

24Mar09

I’ve read 2 articles recently about technical debt: one by Martin Fowler, and one by Max Pool on Codesqueeze.
I particularly agree with Max’s idea that if you ‘Make your case, and show the business value, the majority of the time you will get that signature for the refactor’.
I always hear developers blaming management for a [...]

Top Down Design VS Bottom Up Design

04Mar09

I’ve heard a few arguments recently siding on either top-down or bottom-up design. I’ve heard some agreement on a need for both. My opinion resides in the second category.
Both are required for different reasons, but both are required in almost every context.
Top-down design is very valuable because it allows us to look at [...]

Agile & Best Practice Software Development Resources

17Sep08

I was about to come up with a list of books and blogs for a colleague that capture Agile & Best Practice Software Development, and I found these:
Top 100 Best Software Engineering Books, Ever
Top 100 Blogs for Development Managers (Q3 2008)
They very closely align with my interests and I believe the lists to be quite [...]

Let the Business Drive Sometimes Too

24Aug08

I wrote recently about transparency being key in software development. I think that another way to move in this general direction is to concentrate on letting the business drive your process sometimes too.
Our customers don’t need to know much about software development in order to help us develop software that adds a ton of [...]

Embrace the Skills

10Aug08

I tend to spend my time as a software developer taking in anything I can get my hands on – The old ‘jack of all trades, master of none’ adage. While I appreciate opportunities that exercise various skills (and develop new ones when possible), I find it very difficult to multi-task as a developer. Developers [...]

No Magic!!! – Transparency is Key

09Aug08

Most people who have worked with me have heard me preach about the importance of transparency. There is an old-school tendency in IT to view software as some sort of ‘magic’. Those paying for the software prefer to look at it this way, because it means that they are not expected to understand [...]

Critical Chain Scheduling

30Sep07

As a software developer I often receive push-back on promoting features or components to a production environment because of outstanding product backlog items.
The problem with this type of approach is that there will undoubtedly always be outstanding product backlog items. These backlog items will vary in criticality and the measure of criticality will be [...]




Follow shaunmacrae on Twitter