One of the largest areas of waste in development 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, as well as examining how this can fit into your current planning and estimation workflow via the underused ‘definition of ready’. It’s a very actionable concept that you can apply immediately.
There are essentially two factors that determine whether your offshoring adventure is successful or not – people and process. This article is the first article in a series on managing remote teams, sharing experiences in developing a process for remote collaboration. As people sit apart in (several) remote locations, extra attention must be paid to articulating how people work together.
Often, requirements elicited from stakeholders describe a system’s functionality but fail to address qualities such as performance, reliability, & availability. Documenting these requirements is often overlooked because there are implicit assumptions that the system will perform to expected levels. This article describes a process developed on the idea of persona sketches to address this problem.
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. 2
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? 42