Looking for:
Sprint Zero: A Good Idea or Not?.Sprint 0 - our best practices - Codibly - Create, Impact, Innovate |
Scrubbing Sprint Zero | .The Concept and Execution of Sprint Zero — Clearly Agile
After having this time to work as a team and with stakeholders or owners, we have a prototype that's aligned with the business objective, a user-centered prototype that stakeholders can test, and a detailed scope of the product development phases within a product backlog organized in a roadmap or releases so we can start working with both squads at a high grade of confidence.
At Wealize, we've tested and validated that customers that onboard on this working process felt after it to have a better understanding of their business, the value of having an interactive prototype to share and that those factors help in the early stages of a business fundraising. Thus, we work in different stages during the period of weeks to understand the business value, translate it into product requirements, and design a solution we can test.
The approach for a good sprint zero execution is based on the decision-making framework promoted by HCD and relates to every week or stage of the cycle. For this matter, we identify 3 key elements to succeed in a progressive execution of the sprint zero which reflects on the following weekly working sessions to use as a reference:.
The purpose of defining certain stages during sprint zero is to be able to create a relation about every phase, in terms of time and delivery. Thus, each stage is related to one week of work with the variable mentioned above taking weeks place during stages 2 and 4. The main objective of the first week of sprint zero is to ensure teams and stakeholders are on the same page regarding the business goal. The deliverable can be a written business landscape based on the most relevant areas of a new business: background, business objective, problem, solution, customer persona, competitors advantage, and technology.
To gather this information from the customer, we can perform a business interview based on the business model canvas' relevant streams or asking the 5Ws of the business. The main objective of the second stage of sprint zero is to translate the business requirements into functional needs from a user-centered point of view. For this need, we are focusing the working sessions on two main works: user flows and user story map.
The USM is a great technique we use transversally when we work with products, but I'll talk about this in future posts. The deliverables of this phase are both a users flow and user story map board validated with the stakeholders. We like to use Miro so we can keep it alive with customers' feedback and comments. The key result at this stage is to build an interactive prototype and define a solution architecture to base the application.
On the technology side, now that we understand both the business and the product, we can draw a solution architecture drawing the IT infrastructure with the requirements registered from the customer and our advice - you might have your favorite cloud service provider. The deliverable is a product backlog detailed at the user story level, ideally with the suggested implementation and acceptance criteria, organized by product releases or feature roadmap.
Now both the squad and the stakeholders can have a more accurate scope of the product development phases that unlocks time and money questions that arise during the first steps of a new business. Some customers may have a clear vision and definition of the business to work throughout a traditional process of requirements gathering and request for proposal.
But those, innovative ideas, that are looking to become a reality, and have an impact on thousands of business users need a curate phase due to understanding the right problem we are solving for them. Founders or decision-makers that have been through sprint zero or related methodology, confess to feeling more prepared to start a new business or initiative in their companies, even if the development phase is delayed.
For teams, developers and designers feel more confident and motivated with the product development phases, not only by having a detailed registration of tasks but having been working in their specialty and plugin those skills into the sprint zero execution and delivery. We help fact-checkers to uncover fake news with AI chatbots and conversational platforms. Discover here success stories of AI for verification Maldita's award-winning AI assistant, the start of a collaboration based on journalistic excellence and next-generation conversational technology.
Mariano Morera Jun 10, What's Sprint Zero? Record these interactions if possible. Develop User Personas The purpose of User Personas is to create reliable and realistic representations of your key audience segments to help guide your team through key product decisions. Your Personas should be based largely on qualitative research, so get off your butts and go talk with your users!
You can also gain insight into users with quantitative user research via surveys, analytics, etc. I recommend creating Personas for the primary target audiences for the product, focusing on the most important segments.
The goal of Personas is not to represent all audiences or address all needs in the product, but instead to focus on the major needs of the most important user groups. The key aspects of a Persona include:. Utilizing the analysis from the user research in Sprint 0, the Design Lead can develop the highest priority user flows as well as a few UX templates e.
Home page, Content page, etc. It will serve as the initial user experience hypothesis, that the design team can utilize for design iterations and testing, where it can include a few of the following: content layout and structure, navigation, user flows, etc. Next, imagine your product is human, and select a specific archetype from the list below that best reflects the character you want to reflect or develop one of your own :.
Next, choose the personality attributes that best match the archetype, where you should consider aligning one or more attributes with your Personas:.
Create a list of the personality attributes that your team creates. Review them and resolve any conflicting attributes. Narrow the list to the top attributes, and prioritize them accordingly.
Read more in my post about creating a unique product personality. The Dev Lead set a solid foundation in the Strategic Product Planning process , with the development of the Product Architecture, design documentation, and setting up the development environments. Now the whole Development Team meets to work together on the following deliverables…. Sprint 0 is especially important for teams that are new to Agile, or for products with a lot of complexity that require further exploration before Sprint 1.
Or simply to give teams a chance to get to know each other and collaborate on something smaller before diving into the full sprint cadence. With everything completed in the Strategic Product Planning and Sprint 0, your product team should be ready to hit the ground running on the first day of Sprint 1!
I recommend using a Design Sprint. He is currently Design Director at Blizzard Entertainment, where he leads the development of world class experiences for gamers.
Additionally, he is a successful entrepreneur who co-founded and ran multiple tech startups. View all posts by Joe Smiley. Skip to content.
No comments:
Post a Comment