Is Your Software CM a Burden on Developers?Is your software configuration management process placing a burden on developers? Joe Farah lists some handy tips to ensure that CM benefits not only the business bottom line but also the developers and every role on the project team.
Explore Task Automation Now, Save Time LaterTest automation is a hot topic in the testing community and a perennial topic of debate. What doesn't seem to receive the same attention, though, is task automation: automating the repetitive, non-testing processes that testers have to waste their time on.
Solutions to Old and Bad SoftwareA recent article in the Atlantic describes the software behind many systems we rely on, and not all of the software is as robust and well written as we might hope. While agile values and techniques may not be the whole solution, they can help you improve the quality of your software.
The Role of a Project Manager in an Agile EnvironmentIn a recent post on Linkedin, a question was asked about the role of project managers in a fully agile environment. Joe Townsend weighs in and describes how a project manager can fit in with Scrum while adhering to the principles of the Agile Manifesto.
It's the Relationships, StupidRelationships—working and personal—are vitally important to successful business analysis. If you don't have them, nothing else much matters.
Using a Scaled Agile Framework for Big Agile ProjectsAs the software debacles experienced by both the Royal Bank of Scotland (RBS) and Knight Capital Group show, large-scale projects can become large-scale problems. Using a Scaled Agile Framework (SAFe) helps steer these big projects in the right direction.
CIO: It's a Tough Job, but ... Will It Last?Where the CIO position is heading or even whether it will still be around in a few years is far from a sure thing. Look around, and you’ll see that opinions vary considerably about what the future holds for CIOs. Will it stay the same, split into multiple roles, or disappear completely?
Just-in-Time Requirements AnalysisAll requirements are built on some sort of hypothesis. Just-in-time requirements analysis embodies the idea that you form your hypothesis as late as responsible—not as late as possible.
