This is the last of three articles exploring the culture and practices that makes Menlo Innovations such a joyous workplace. This article examines their approach to user experience and requirements - a set of practices they call High Tech Anthropology®
What may be valuable to customers whom you do not even know in an unstructured and completely individualized market? This article suggests prioritizing your backlog using an enhanced quality model based on Maslow’s hierarchy of human needs. Search for most valuable features using the Need-Feature-Capability matrix and give those features highest priority in your backlog.
The book "Agile! The Good, the Hype and the Ugly" by Bertrand Meyer provides a review of agile principles, techniques and tools. It explores the agile methods Extreme Programming, Lean Software, Scrum and Crystal and provides suggestions on what to use or not to use from them, based on software engineering principles and research and personal experience of the book author.
One of the largest areas of development waste are poorly formed requirements. This post presents a very simple technique that can be applied to all user stories to improve quality and reduce waste. 3
This article is the first article in a series on managing remote teams, which shares experiences in developing a process for remote collaboration.
This article shares a simple technique used to address problems such as a system’s intended functionality but also qualities such as performance, reliability, portability, and availability.
Ellen Gottesdiener and Mary Gorman have written a book titled Discover to Deliver: Agile Product Planning and Analysis. They recently spoke to InfoQ about the ideas behind the book.
Eduardo Miranda from Carnegie Mellon University explains planning in agile projects, planning techniques, and the impact of agile on project management offices and the project manager role. 4
Suzanne and James Robertson have released the 3rd edition of their book Mastering the Requirements Process. This edition includes material focused on requirements in agile projects and outsourcing.
One of the main challenges when designing software architecture is considering quality attributes. Not only their design turns out to be difficult, but also the specification of these attributes.
Gojko Adzic has written Specification by Example in which he provides advice and guidelines on adopting this approach as a way to create living documentation on a software development project. 7
The line between development and architecture is tricky. Does it exist at all? Is an ivory tower actually needed? There's a balance in the middle, but how do you move from developer to architect? 43