|
|
Each week I capture, mark, and comment on blog posts and news articles around the internet. This is short list of three links that I think others will find valuable for their thought lives.
A Simple Device Diagram for Responsive Design Planning by Adam Edgerton of Metal Toad Media. This is a great resource post for development teams. It discusses screen resolutions of common devices so that teams can better optimize experiences on their solution sites. Caller ID spoofing scams aim for bank accounts by Byron Acohido of USA Today. Crime has no boundaries in the digital world. This article discusses how criminals are using cell phones and SMS …Continue reading >>
I don’t like process waste.
Who does? But how many of us really try to change processes to eliminate or reduce waste? In my experience this is a tough topic, and I dare say an unwelcome one, most of the time. The problem is that in an organization processes are tied to job existence and security. So the people in charge of setting the processes and administering them really don’t see the incentive to make adjustments.
I’m nearing my 20th year of software development experience, so I’ve observed and talked to many practitioners about software development process philosophies and techniques. Process waste starts to build when the people within the …Continue reading >>
What’s the most powerful step in a software development process? It’s not uncommon for analysts to label steps in a process. The critical path, bottlenecks, waste, and non-essential steps come to mind. So I would say that common wisdom agrees that all steps in a process do not hold equal weighting of importance. Maybe there isn’t a single most powerful step in the software development process you follow or maybe it depends on the context of the situation.
For what it’s worth, a few weeks ago it occurred to me that the act of estimating was perhaps the most powerful step. Estimating is completed at the ground level, by …Continue reading >>
This is about IT and Business alignment. I’m fortunate enough to have worked in two different functional areas of a business: IT and Marketing. I can say with 100% confidence that business owners and stakeholders of software releases should be more concerned and involved in the IT release management process. The typical release process covers areas such as requirements specification, feature prioritization, business case modeling, and go-live deployment communication. It’s a set of tasks intended to oversee the requirements, development, testing, and deployment of software releases. Sounds very IT, but it should be a shared business process.
Release management is about adding value. Release Management is also about how IT …Continue reading >>
If your backlog is not a graveyard then you may be short of ideas. In my 20+ years of software, I’ve always had a backlog for software development. The list is full of ideas, customer requests, and defects. It fills faster than the team can implement and some items become aged and never resolved. I’ve come to realize that if I don’t have a list with aged items it’s probably because I don’t have an open channel of incoming ideas and I’m no listening to my customers.
I used to stress over an overflowing backlog and it was a source of frustration. As I matured a bit with software development …Continue reading >>
|
|
Latest Discussions