The use-case model can be a powerful tool for controlling scope throughout a project’s life cycle. Because a simplified use-case model can be understood by all project participants, it can also serve as a framework for ongoing collaboration and a visual map of all agreed-upon functionality. Use it to plan, to negotiate, and to prevent scope creep.
More from A List Apart
We’re obsessive about collecting input from a wide range of potential users and stakeholders. But with such an onslaught of feedback, there’s always a risk of having your motivation and faith in humanity sucked right out of you. Sometimes, you just need calm critique from the few people who really get you. So which kind of feedback is best? The answer is both.
From the Blog
As a freelancer, I work in a lot of different code repos. Almost every team I work with has different ideas of how code should be organized, maintained, and structured. Now, I’m not here to start a battle about tabs versus spaces or alphabetical order of CSS properties versus organizing in terms of concerns (positioning styles, then element layout styles, then whatever else), because I’m honestly not attached to any one system anymore.
Part of getting comfortable with the command line is making it your own. Small customizations, shortcuts, and time saving techniques become second nature once you spend enough time fiddling around in your terminal. Since Git is my Version Control System of choice (due partially to its incredible popularity via GitHub), I like to spend lots of time optimizing my experience there.