I came across a case study of how to estimate and slice stories in a real-world scenario. Everyone knows Adobe, and this is how they do it: Using Vertical Slicing and Estimation to make Business Decisions at Adobe.
The case study presents an actual problem which needs to be solved, and Adobe did not ignore it.
I found a nice overview of what you should focus on when entering the German market. You see, we Germans are stereotypical at times:
- Low-risk choices
- Localisation is key
- Premium quality
See the full article here.
Good user experience is useful to the user; it has some real benefits, as demonstrated by WordPress autocorrecting your email address in case of typos.
Useless user experience can be funny, but does not bring add any benefit, as demonstrated by Windows 8 calculator.
The Cranky Product Manager returned and she brings us a list of common product management mistakes that we need to prevent. Even experienced PMs make these mistakes. Among the items on the list are:
- Not meeting with enough customers often enough.
- Allowing a piece of shit to ship.
- Making the product hard to buy or up-edition.
- Being afraid to draw pictures.
See the full list here.
When shopping for camera lenses, Amazon checks whether they fit on a camera you bought earlier. While one can argue that this ties customer to Amazon and prevents them to buy somewhere else, this feature does actually add value instead of just looking good.
Most software product are developed as closed-source projects. There are some famous examples of open-source software though, such as Firefox, Linux, OpenOffice, etc.
To avoid the pitfalls and successfully release your software product as open source, this article lists what you need to take care of:
- Why Open Source?
- Getting Started
- Choose A Default License
- Outgoing Review
- Accepting Contributions
- Maintaining The Project
- Warning Signs
- End-Of-Lifing Projects
Joelle Steiniger wrote a real-life case study about how not to go about developing a product. She writes that they listened to people in the development process, which was wrong. Eventually, they tried so solve the original problem without following pre-defined solutions. One of the most famous examples is mentioned as well: Henry Ford would have built faster horse carriages, had he listened to people.
The post is a longer one, but it is worth it.
Here is an example of a very good UI that is more than pure eye candy: On about.com, suggested text colours fit the text background colour picked earlier.
The user has a real benefit from the UI behaviour: The suggested colours are more useful than just a palette of unrelated colours. Nice!
Hora Loranger from Nielsen Norman Group has a nice article that shows what to keep in mind when choosing category names for websites (or user interfaces):
- Choose descriptive words and phrases
- Avoid made-up words or terms
- Check for overlapping categories
- Use classification schemes that communicate attributes your users can decipher
- Don’t rely on your instincts when deciding label names.
Use usual, great examples and more insight in provided in the article. Highly recommended.
This is something for a laugh: Cartoons of the different types of software engineers. Personally, I like the Teflon-gineer most, but also found real-life examples of all other types.