Related Content
 |
Cassandra’s Curse: You Can’t Make Clients Take Action According to Greek myth, Cassandra's curse was that she could predict the future but no one would believe her prophecies. Sometimes the same can be said for project proposals. You can give the best assessment possible, but that doesn't mean the client will heed your words. Read on for encouragement. |
|
 |
Successful Performance Testing Begins at Requirements Discovering performance issues in early builds allows more time to correct the design. By including critical performance-related features and elements earlier, we can take advantage of the incremental nature of the development process to avoid creating engineering in potential performance issues. |
|
 |
Maximizing the Coexistence of Scrum and Kanban It is difficult to exclusively use Scrum or kanban in product development, given the advantages they both provide. The prospect of using the two together can be just as difficult to fathom, yet it is possible for them to coexist—and with optimal results. Read on to learn how to combine the two. |
|
 |
Tools—Some Assembly Required A tool architecture is simply a picture of all your development, testing, and deployment tools and how they fit together. Creating a "current state" diagram and then looking forward and creating a "future state" diagram helps you understand where tool integrations would be beneficial. |
|
 |
Beware of Serial Status Meetings Standup meetings are great in many instances. But if you're calling serial status meetings, you may find that people will stop attending. To engage employees and address issues quicker, you may want to try lean coffee or a problem-solving meeting. Read on for tips on involving your team. |
|
 |
How Can I Create Good Definitions? It is vital that everyone communicates properly if we are to build software applications that meet the needs of our organizations. However, creating clear and unambiguous requirements necessitates good definitions, which can sometimes be difficult. Conrad Fujimoto shares his starting technique. |
|
 |
What's in the September/October 2014 Better Software Magazine? In our latest issue of Better Software magazine, the feature articles focus on software licensing and ways to improve your team’s approach to process improvement. Creating software for a wide range of platforms is difficult enough, but enforcing software licensing also can be challenging. |
|
 |
Take a More Agile Approach to Problem Solving Your managers want you to estimate features or projects months or even years in advance. But the work changes—or the code changes, or the people on the project change. What you thought might be a reasonable estimate four weeks ago looks wacko when you revisit it in six months. What can you do? |
