What questions should we ask when determining more about a product's dimensions? Let me show you how to facilitate a workshop based on the 7 Product Dimensions.
In their book Discover to Deliver: Agile Product Planning and Analysis, authors Ellen Gottesdiener and Mary Gorman introduced a simple and powerful model to guide product discovery effort – The 7 Product Dimensions model. This model identifies 7 areas (product dimensions) that we will need to explore – through collaborative questioning and reflection – in order to learn more about the product. The dimensions are User (who the users are), Interface (how they interact with the product), Actions (what they can do), Data (what data the product needs/stores in order to work), Control (rules & constraints), Environment (platforms that would host the product/on which value will be delivered), and Quality Attribute (customer’s expectations around quality, usability, etc.). The premise is simple: if we ask good, powerful questions about each of these dimensions, we’ll learn a great deal about this product we want to build, which will help us build a better product. You can find more information about the 7 Product Dimensions framework and canvas Here
Here are some of the questions that we could ask to discover more about each product dimension:
In this article, I will discuss how I adapted Avi’s original canvas to the needs of the teams I was coaching, elaborate on the different elements of a working agreement, and share with you a step-by-step guide to facilitating collaborative working agreement development workshops.
Full workshop breakdown on how to identify non-functional requirements (NFR) as a part of an agile project inception, including preparation and execution tips.
Shorter development cycles and faster innovation are the basic characteristics of the DevOps model. It has swept the market with new ideas and incredible solutions, leading to 74% adoption by global enterprises. The reasons are different, but the top ones are the ability to recover from a failure in less than 60 minutes, minimization of support cases by 37%, and overall need to “put out fires”. No wonder that Quality Assurance, as a stage of the software development process, had to adapt to the new reality of the DevOps model and change its traditional approaches.
The year 2020 has arrived, and its arrival brings a lot of innovations and transformations in the Information and Technology (IT) sector to DevOps technologies.
What is DevOps? How are organizations transitioning to DevOps? Is it possible for organizations to shift to enterprise DevOps? Read more to find out!