“…what about the magical number seven? What about the seven wonders of the world, the seven seas, the seven deadly sins, the seven daughters of Atlas in the Pleiades, the
Do your customers believe you treat them well? Of course it helps if your company (or division or your group or you personally) actually has a vision and best practices
This is the second part of a two part series on the impact of software requirements on technical debt. Part 1 defined technical debt, delved into its importance, discussed its
This is a two part series on the impact of software requirements on technical debt. Part 1 summarizes technical debt and part 2 discusses the impact that software requirements can
It is the end of your project and your tests are passing. Are you ready to confidently release your project? Or, are you secretly crossing your fingers like a young
He Who Gets Slapped – Leveraging the project requirements after analysis phase to avoid the tyranny of the urgent and help guide the project to a successful conclusion Someone who
We probably don’t think about dress codes too often. We do pay a little more attention when preparing for a job interview or meeting an important new client for the
Conclusion to the series, “How to Shoot Yourself in the Foot: 7 ways to do software requirements poorly to set your project up for failure and what to do instead.”
Number 7 in the series, “How to Shoot Yourself in the Foot: 7 ways to do software requirements poorly to set your project up for failure and what to do
Number 6 in the series, “How to Shoot Yourself in the Foot: 7 ways to do software requirements poorly to set your project up for failure and what to do
Number 5 in the series, “How to Shoot Yourself in the Foot: 7 ways to do software requirements poorly to set your project up for failure and what to do
Number 4 in the series, “How to Shoot Yourself in the Foot: 7 ways to do software requirements poorly to set your project up for failure and what to do
Don’t miss out on this opportunity
and request a conversation today!
