<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by David Rizkalla on Medium]]></title>
        <description><![CDATA[Stories by David Rizkalla on Medium]]></description>
        <link>https://medium.com/@david.rizkalla?source=rss-3258c0214a71------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*DEcKalZ8AnfyVtUgCoWrGg.jpeg</url>
            <title>Stories by David Rizkalla on Medium</title>
            <link>https://medium.com/@david.rizkalla?source=rss-3258c0214a71------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 13:58:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@david.rizkalla/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Remote delivery — the importance of keeping the culture alive]]></title>
            <link>https://medium.com/momenton/remote-delivery-the-importance-of-keeping-the-culture-alive-26ceeb2acd2b?source=rss-3258c0214a71------2</link>
            <guid isPermaLink="false">https://medium.com/p/26ceeb2acd2b</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[team]]></category>
            <dc:creator><![CDATA[David Rizkalla]]></dc:creator>
            <pubDate>Tue, 11 Aug 2020 04:45:13 GMT</pubDate>
            <atom:updated>2020-08-11T07:59:50.002Z</atom:updated>
            <content:encoded><![CDATA[<h3>Remote delivery — the importance of keeping the culture alive</h3><h3>Introduction</h3><p>Our year at Momenton started full of promise. In February, we partnered with a government agency to modernise its architecture. The ask was to build and quickly deliver a complex process orchestrator that would scale and be fast. Here we had an excellent opportunity to showcase our technical skills — Kubernetes, event-driven architectures and API gateways — and our ability to deliver high-quality software within a short time frame. Just one month later, the spectre of Covid-19 loomed. We knew this was going to force businesses into a remote working model. To get ahead of this and to be prepared, we trialled remote working before restrictions were enforced. As a team, we were set up for success, armed with an elite skill set, ready to overcome the challenges of a global pandemic, forcing us to work remotely. What we discovered was that even the best processes and tools could falter without strong human connections.</p><h3>Remote working begins</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/810/1*LTClELt1ouTHHxeNFJ9BBQ.png" /><figcaption>March- The Pandemic starts to hit Australia and all businesses begin preparing for remote working</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*5y8fM1lVdWRhHoRjwOxUIQ.jpeg" /></figure><p>First, we worked on a 2-day rotation. Half the team worked from home and on Fridays we all came together in the office.</p><p>The following week, everyone worked remotely from Monday to Wednesday and came into the office on Thursday and Friday. We were able to perform our ceremonies via Slack video calls. We stayed in contact throughout the day using Slack chat and email. We were able to visualise our work using tools such as Jira and GitLab.</p><p>Finally, remote working became the norm; for our safety, we all worked from home 5-days a week. Thankfully we were prepared, or so we thought…our workflow, tools and processes were solid and built for a remote working environment. Our code repositories were web-based and remote access was not restricted. However, our team morale started to decline. The way we were communicating with one another became laced with an air of frustration and hostility. Individuals started to take feedback on code reviews personally and team collaboration was breaking down. This was evident in Story Refinement sessions and Retrospectives. As a result, our performance and sprint goals were negatively affected. These were issues which our team did not have before the pandemic. Nothing had changed with our processes and tools; we still performed all of our ceremonies and could access our work all the same.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kuz2XDS9FNtrtek32VwIig.png" /></figure><p>So what was causing this drop in team performance and morale? Well on top of the pressure of delivering an end product amidst a toilet paper buying frenzy, hands dryer than the Sahara caused by the excessive use of hand sanitiser and the daunting prospects of home schooling; working remotely was affecting our team culture. We were losing our identity, the bond we had developed over time through human interaction. We only ever communicated during work-related ceremonies, Slack chat and email. Even code reviews and questions on stories were done via the comments section of GitLab and Jira. Comments were being misinterpreted as demanding or condescending when written compared to verbal conversations. We were missing ‘face to face’ interactions.</p><h3>The new ‘face to face’</h3><p>Before lock-down and remote working, casual social interactions with colleagues occurred regularly such as, going for a coffee together or Friday night drinks. The importance and value of this time was taken for granted. These casual moments brought us closer together as colleagues and friends. Accepting and taking on feedback from colleagues is always easier when there is a mutual sense of respect.</p><p>In order to deal with this breakdown, we implemented a few principles to improve communication across the team. We came to an agreement that code review and Jira comment queries were to be followed up by a verbal conversation. If feedback was added to a code review, this would be followed up by a video call to the developer. Here feedback could be elaborated on. The same applied for Jira comments, rather than just tagging a person in a comment. These conversations helped in bringing a sense of understanding and respect back into the team.</p><p>To reinvigorate this lost work culture, we all decided to dial into stand-ups with coffees in hand, making them less formal and more in line with the friendly vibe that we had lost. We also started having Zoom catch-ups on Wednesdays and Fridays. We ended our workday at 4:30 pm, grabbed a drink, changed our virtual background to something fun and had a laugh. That’s all it was about; we didn’t discuss work or the sprint. In fact, we introduced a rule, you bring up work, you get kicked from the Zoom party!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Yly2uz32k9PtvvXVca1nZQ.png" /></figure><p>These simple changes had almost immediate effects, our team was much happier. Individuals began to accept feedback from one another more willingly and produced better code. Overall, our team was back to its high-performing self, successfully and remotely, we delivered a fully functioning Complex Process Orchestrator within 16 weeks.</p><h3>Conclusion</h3><p>Whilst having a framework to set guide-rails for Agile teams is important (something we will talk about in a subsequent post) what is just, if not more important is maintaining team culture and morale especially when working with remote &amp; distributed teams.</p><p>We went into a remote working setting with the right setup and tools to get the job done, but that wasn’t enough. We needed to maintain our face-to-face conversations and values to keep our performance alive. Simple techniques you can use to give feedback is video chats such as Slack or Zoom as opposed to commenting on stories or code reviews. Along with some scheduled break out time to have a virtual drink together was a major key to our successful delivery of the project.</p><p>Look after your team’s happiness, and they’ll look after the required task at hand. Don’t underestimate the importance of human connection and the impact it can have in the workplace; especially during this time.</p><p>Reach out to <a href="/service/mailto:hello@momenton.com.au">hello@momenton.com.au</a> to understand how <a href="https://momenton.com.au/">Momenton</a> can help your organisation with new remote ways of working and how we can help you deliver your product faster.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=26ceeb2acd2b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/momenton/remote-delivery-the-importance-of-keeping-the-culture-alive-26ceeb2acd2b">Remote delivery — the importance of keeping the culture alive</a> was originally published in <a href="https://medium.com/momenton">Momenton</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting predictable in an unpredictable environment]]></title>
            <link>https://medium.com/momenton/getting-predictable-in-an-unpredictable-environment-6fa2a771a5d8?source=rss-3258c0214a71------2</link>
            <guid isPermaLink="false">https://medium.com/p/6fa2a771a5d8</guid>
            <category><![CDATA[business-analyst]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[David Rizkalla]]></dc:creator>
            <pubDate>Mon, 25 Mar 2019 04:51:47 GMT</pubDate>
            <atom:updated>2019-03-25T05:31:20.790Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6Po0HF5e6rb58fSG2r0pXw.jpeg" /></figure><p>Predictability — Product Owners love it and rightfully so, they want to know what features they will get and when they will get it. In the past, I have found getting predictability to be an attainable task through story estimation and user story mapping. User story mapping is an activity used to provide a graphical representation of a users journey through a product. If you want to know more about story-mapping, click <a href="https://medium.com/momenton/leveraging-user-story-mapping-to-anchor-your-mvp-71cda7cb7eb">here</a> to read a past blog I wrote on leveraging user story mapping. By running a story mapping exercise and estimating our user stories, you can determine how many sprints a feature/epic would take based on the teams Velocity and Capacity at the time. However, is it this simple in every environment? With every product? Well Yes…and no.</p><h3>The ‘Yes’ part</h3><p>The key to getting predictable is finding the right estimation exercise that works for your team, once you can make your estimation more objective, getting predictable and determining how long a feature will take becomes as simple as estimating the stories and knowing your velocity.</p><h3>The ‘No’ part</h3><p>Here is where it gets complicated, finding the right estimation exercise for a team isn’t always as easy as trying the plethora of estimation techniques available to you. Don’t get me wrong, it’s good practice trying new estimation techniques but sometimes the problem isn’t always with the chosen technique but with the product or environment you work in.</p><h4>New teams and new features</h4><p>Sometimes development teams can be working in code that is new to them. If the team is new or the product is new it is hard to measure the complexity or level of effort required to achieve a story. Even with relative sizing exercises it is still quite subjective. 8 Points for 1 Developer can be 3 Points for another, development teams generally comprise of different experience levels. All teams and software are different and diverse and this can complicate estimation.</p><h4>Complex Environments</h4><p>Not all products are one simple piece of software, some products live within a very complicated environment. Many downstream systems managed by different teams, some of which are overseas. There can be a major reliance on these downstream systems for Product Owners to achieve their desired outcomes. Subject matter experts (SMEs) for these downstream systems don’t always sit within the Development team. This means we hit a lot of dependencies on other teams and spend time liaising with these teams on how we send data downstream. This significantly affects estimation as we cannot always foresee work required by these groups or the level of complexity involved on their side.</p><h4>External Blockers</h4><p>Estimation does not factor in downtime such as environment issues and other factors outside our teams control. SIT environments go down, overnight builds fail and dependencies are well…not always dependable. Pointing a story as X amount of points cannot realistically factor in another teams work effort without that team being present or factor in unforeseen events.</p><h3>So what do we do about it?</h3><h4>Have you heard of Throughput?</h4><p>A technique which is working well within one of the current teams I am in is Throughput. Throughput is the number of work items completed through a unit of time. In our instance the number of stories completed in a sprint. The good thing about Throughput is, it factors in your external blockers, complex environments and unknowns because it is based on the number of stories you have delivered in past sprints and not how many points estimated prior to the story being delivered. So for example, for the last 4 sprints you have committed 20, 23, 20 and 23 stories respectively and only delivered 13, 14, 9 and 8 stories respectively. Then our average Throughput is 11 Stories.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/656/1*PHtZn9MZqRKqmxQ_66vTdw.png" /></figure><p>The most common question which arises when using Throughput is; How can we determine what stories to commit if we haven’t estimated how big each story is? What if we chose 11 stories which take longer than a sprint to complete because we are not estimating their size? If you’re asking this question, then you’re not refining your stories properly. Refinement isn’t only about discussing what needs to be done in a story but if we can split this story down further. I like to think about white-flour vs whole-wheat flour, white flour is wheat so refined it becomes a fine powder. When baking bread with white-flour as opposed to whole-wheat flour, you get a product which bakes faster, lighter and fluffier. Similarly in story refinement, you want to refine your stories down to the smallest tasks possible, this will get your stories moving faster and lighter in terms of complexity and effort. I wrote a section on story refinement in a past blog post about effective user stories. You can view it <a href="https://medium.com/momenton/how-to-use-your-stories-effectively-3493273c3898">here</a> if you would like to know more about refinement. Refinement sessions are imperative for throughput to be effective because stories need to be consistently small.</p><h4>What’s small?</h4><p>My interpretation of what small is, is a subjective one. What a team considers small doesn’t really matter that much, as long as it is consistent. That means, if a development team agree that ‘small’ is a story which takes 3 days well then guess what? That’s small. Once a development team agree on what a small story is, we can work towards refining stories to be small.</p><h4>How does this differ from estimation?</h4><p>I know making stories small sounds a lot like estimating stories, that is because it is a type of estimation. It’s just how we go about the estimation and how we use it. When refining stories, give power to the the development team. Rather than presenting a story, elaborating the acceptance criteria and then asking; How long will this story take? Ask the question like this; How much of this story can you complete in 3 days? This gives the Developers and Testers the power to commit to what they can do rather than throw a subjective number of days at you. It may be agreed that of the 3 Acceptance Criteria, only acceptance criteria 1 and 3 can be achieved in a 3 day period while the acceptance criteria 2 can be done in another 3 day period. Split the story accordingly. You now have two consistent work items in the backlog.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lW0RSLxmJR1f0VXVLDIXfw.png" /><figcaption>A story split into 2 consistently sized stories</figcaption></figure><p>Once you have consistently small stories you will find that overtime, your average throughput will become more predictable and your delivery will be stable.</p><h3>Summary</h3><p>To summarise, if you’ve found estimating stories with points or time has not helped bring predictability to your sprints or due to external blockers, complex environments or unknown factors your sprints are never complete, then give Throughput a try. Throughput is the number of work items completed within a unit of time.</p><p>Before you try Throughput, make sure your stories are refined and small. Make sure your team has discussed and agreed on a consistent definition of small and that all stories are small before they can be committed for work.</p><p>Now use past sprint throughput to get your average throughput and over time your throughput will become far more predictable.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6fa2a771a5d8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/momenton/getting-predictable-in-an-unpredictable-environment-6fa2a771a5d8">Getting predictable in an unpredictable environment</a> was originally published in <a href="https://medium.com/momenton">Momenton</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to use your stories effectively]]></title>
            <link>https://medium.com/momenton/how-to-use-your-stories-effectively-3493273c3898?source=rss-3258c0214a71------2</link>
            <guid isPermaLink="false">https://medium.com/p/3493273c3898</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[new-ways-of-working]]></category>
            <category><![CDATA[user-stories]]></category>
            <dc:creator><![CDATA[David Rizkalla]]></dc:creator>
            <pubDate>Tue, 02 Oct 2018 05:06:00 GMT</pubDate>
            <atom:updated>2018-11-01T22:40:05.222Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RcMg7Bg9eU64ChWD" /><figcaption>Photo by <a href="https://unsplash.com/@rawpixel?utm_source=medium&amp;utm_medium=referral">rawpixel</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>User Stories are <strong>small</strong> and <strong>simple </strong>descriptions of a feature. They are narrated from the perspective of a person who will use this new functionality. User stories are the most popular agile technique to capture product features and are easy to use but harder to make effective. The basic foundation of a user story is; as a &lt;user&gt;, I want &lt;function&gt; so that &lt;reason&gt;. Stories should be Independent, Negotiable, Valuable, Estimable, Small and Testable (INVEST). This is all a good start, I always try and keep my stories relevant to the INVEST principles. Is that enough to make stories effective? Short answer, no. Here are a few handy tips to really get the most out of your user stories.</p><h3>Users come first</h3><p>User stories are written from the perspective of the user and how they will utilise the product. Spend some time identifying who your users actually are, it isn’t necessarily the end-user who will be directly interacting with your product. The user in your story should be the one who is directly interacting with the product for its intended function. For example, if you were making some enhancements to a web Content Management System. The end-user is your online web user however, work done to the CMS means your user in this instance are the authors. By determining this early, you can make sure their user experience is at the forefront of your mind.</p><h3>Collaborate and build stories together</h3><p>User stories should never just be handed to the development team to start working on, <strong>User stories are there to initiate conversations. </strong>By collaborating with the development team, the stories can be broken down further, reduce overhead and in turn accelerate delivery. As a Business Analyst, I gather requirements from stakeholders and tend to write up the initial stories. However, I like to perform elaboration sessions. In these sessions I run the team through these stories and <strong>as a group</strong> we break them down and discuss how we are going to meet these requirements. At this point, the team has built the story together. This builds up the understanding of what needs to be done as a group and ensures we are all on the same page.</p><h3>Keep it simple</h3><p>Seriously, keep it simple. Keep your stories concise and short, focus on what is important and make your requirements clear. If they are not clear, go gather more information. It’s really that simple. The way I structure my stories is with simplicity in mind, a narrative, one line description of what the story is about, a questions section (if any) and no more than 6–8 acceptance criteria.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lmyiUKRLiJ7Oc93W1ijsuA.png" /><figcaption>An example of a simple user story</figcaption></figure><h3>Splitting and refining your stories</h3><p>Just like story writing, story splitting isn’t a one person task, infact there is probably a blog series on this alone — hmmm so stay tuned I might just dive into more detail in a seperate post . In the meantime take a read of this — Use your elaboration sessions to discuss the stories, if a story is anything bigger than what the team consider small, work together on the best way to split it. Think as a team, how can we split this story into smaller pieces of work and still maintain our ‘INVEST’ principles. The more you split them, the simpler and more manageable they become, leading to faster delivery. Sometimes you&#39;ll leave elaboration without having a story ready for development. That is fine, you’ve had a conversation and a greater understanding of the details you may need before the next elaboration. I have experienced spending multiple elaborations discussing the same complex user story. The final outcome however, was our one complex user story turned into three simpler and more manageable user stories.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RaEHwKkzlKaf0wknnH9cww.png" /><figcaption>The example above is a high level story split. These actually got split further with more elaborations. Keep in mind there are many conversations behind these user stories.</figcaption></figure><h3>Acceptance Criteria</h3><p>Acceptance Criteria are the conditions that need to be satisfied for the story to be ‘done’. These are conditions which developers will build to and testers will test against. In addition to being clear and concise they also need to be solution free. What I mean by this is, as a BA or a PO we should not influence the development team to build a product in a certain way, leave this for the collaboration sessions. For example, on a website managed by a CMS the stakeholder wants an image in the button component which links to another page. The image they want is the same image in the banner of the page the button component is linked to. My thought process would suggest that the image can be pulled from the page properties of the page the banner is on. However, a solution free acceptance criteria for this could be “Button component to have the same image as the banner of the page it is linking to”. This makes for more collaboration and more ideas on how to achieve this task. Getting the image from page properties is an effective method of achieving this, but is it the best method? Who knows, you can raise your ideas during elaboration and see what the team thinks.</p><h3>Make sure the stories are always visible to the team</h3><p>Stories should always be visible, the PO, developers and testers are always going to refer back to them. By having a board we can see what is in progress, who is working on it and what is done and ready for release. The PO can continuously prioritise the backlog and the development team can see what is coming up next.</p><h3>Don’t just rely on user stories</h3><p>User stories are a great tool but they should not be your only one for building a backlog of work. As they are small narratives with a few acceptance criteria, the details need to be documented elsewhere. Whether is is through process flowcharts and UX designs, this all depends on the type of product you are building and what the development team may need. You can refer to this additional material through your acceptance criteria. For example, we have UX designs for enhancing the menu bar in an app. One of your acceptance criteria in your story could be “Build menu bar as per UX design &lt;Insert link to UX design&gt;”. Our developers now have a guide to build to and testers have the same designs to test against.</p><h3>Summary</h3><p>User stories are small descriptions of a feature, designed to initiate a conversation. These conversations are what drive feature development, not just the user story. Through these conversations, your stories can be split into more manageable pieces of work by the team and provide them with a greater understanding of the requirements. For added value to the teams collaboration, don&#39;t just rely on user stories to capture user requirements. By using tools like process flow diagrams and UX designs, the development team can have a more visual understanding of what they may need to do.</p><p>Thanks for reading — my name is David Rizkalla — I’m 3–1 by KO and its time to eat.</p><p>If you would like to learn more head on over to <a href="http://www.momenton.com.au/">momenton</a> and hit us up for a chat.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3493273c3898" width="1" height="1" alt=""><hr><p><a href="https://medium.com/momenton/how-to-use-your-stories-effectively-3493273c3898">How to use your stories effectively</a> was originally published in <a href="https://medium.com/momenton">Momenton</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mob programming isn’t for the programmers, it’s for the team.]]></title>
            <link>https://medium.com/momenton/mob-programming-isnt-for-the-programmers-it-s-for-the-team-6eb6a06850c3?source=rss-3258c0214a71------2</link>
            <guid isPermaLink="false">https://medium.com/p/6eb6a06850c3</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[business-analysis]]></category>
            <dc:creator><![CDATA[David Rizkalla]]></dc:creator>
            <pubDate>Sat, 25 Aug 2018 11:15:43 GMT</pubDate>
            <atom:updated>2018-11-01T22:40:37.493Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*grjVi-E2HIEeBfFpuT5Jvw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/JlUfDpXsuuM?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Den</a> on <a href="https://unsplash.com/search/photos/mob?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Mob programming is not just for a programmer’s benefit. I love mob programming and I hope after this blog your interest will be peaked enough to try it with your development team.</p><p>Firstly, what is mob programming? It is when the whole development team, product owner and stakeholders all work on the same thing, at the same time, in the same place and on the same computer. We had one driver on the keyboard at a time and rotated this role every seven minutes, everybody was apart of this rotation. That includes myself (Business Analyst) and even our team’s Accessibility Analyst. If you were on the keyboard you were being navigated by everyone else.</p><p>I know this concept of working can sound inefficient, so many resources working on a single 3 point story, seven developers, one tester and a business analyst (we had one developer, one tester and our PO absent that day) spending a whole day all working on a single story. However, where inefficiencies are made, they are counter-balanced by efficiencies elsewhere, story kick-off, walk through and code review were all done as we went. Time is saved from scheduling all these steps into the process. We just jumped right in and started the story, I dealt with any questions or concerns in real-time while all the developers collaborated to come up with how we actually meet the stories requirements. As UX, accessibility and myself were present during the stories development the walk-through didn’t need to happen either, the relevant parties had seen it come to fruition already and I was there to make sure our acceptance criteria was met.</p><p>We also updated our test cases as a team, our tester was navigating the driver and running us through what he will be testing for, the value this brings alone is priceless. With developers consciously aware of what will be tested made sure they developed and checked their work as they went. This will be a tangible benefit when it comes to testing, we will see minimal to no defects come out of this story. Minimal defects equals minimal unexpected work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/567/1*oVz8BfybOLx0wF7-BhiLug.jpeg" /><figcaption>A small Mob</figcaption></figure><p>Putting all our developers together to collaborate throughout the stories life-cycle really helped bring out the best outcome. Not just in code quality but in functionality, we got to utilise everybody’s strengths while being able to manage and compensate for everybody’s weaknesses. The knowledge sharing ensures we all learn off each other and grow our skill sets as a team. I learned so much in a single session of mob programming, how styling through code works and what details developers need to style particular things. I can now take what I have learnt and implement it into my stories and elaboration sessions. These changes I make will bring further efficiencies in the long-term as I will have answered questions required by the developers before they will even need to go and ask.</p><h3>Summary</h3><p>In summary, collaboration between a team builds stronger a team. What comes when a strong team bonds, is a more efficient team that delivers higher quality software. Mob programming provides these benefits in the long-term, they are noticeable to our scrum from a single session, we will only get better and faster at mob programming from here. In the long-term our scrum could deliver better quality results in shorter time frames.</p><p>Agile principles encourages trying new things and trying new ways of working. If mob programming fails to work for your team, so what? You have failed fast and learnt from it. A lesson will be learned about how your team functions and a lesson learnt is never a waste of your time. Just try it.</p><p>If you would like to learn more head on over to <a href="http://www.momenton.com.au/">momenton</a> and hit us up for a chat.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6eb6a06850c3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/momenton/mob-programming-isnt-for-the-programmers-it-s-for-the-team-6eb6a06850c3">Mob programming isn’t for the programmers, it’s for the team.</a> was originally published in <a href="https://medium.com/momenton">Momenton</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Leveraging User Story mapping to anchor your MVP]]></title>
            <link>https://medium.com/momenton/leveraging-user-story-mapping-to-anchor-your-mvp-71cda7cb7eb?source=rss-3258c0214a71------2</link>
            <guid isPermaLink="false">https://medium.com/p/71cda7cb7eb</guid>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[user-story-mapping]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[David Rizkalla]]></dc:creator>
            <pubDate>Mon, 23 Jul 2018 01:37:49 GMT</pubDate>
            <atom:updated>2018-07-23T01:37:49.925Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FrDceIp-Kg1_gi8QKNYvYA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/gNUMZjxd89w?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">rawpixel</a> on <a href="https://unsplash.com/search/photos/agile-planning?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>In this post we will touch on the value of User Story mapping and how it relates to anchoring your product to commercial value. (This may turn into a multi-part series but lets just start here for now…)</p><p>Story mapping is an important part of software development, it plays a major role in the initial phases of a project. I rely on its ability to provide structure in this chaotic agile world. Story-mapping is an activity used to provide a graphical representation of a users journey through a product. It initiates conversations and ensures the user is the primary focus of our products.</p><p>A Developer, Tester, Product Owner and Business Analyst (me) (maybe some SMEs) sit down together and discuss the product we are about to work on. As a group, we start by identifying and recording our users journey through sticky notes or another visual format. Then we display these notes sequentially for all members to see. We look for similar groupings of journey notes in order to start building out the journey map. Here is an example of how we would map out a user journey for a new customer making a purchase from an online store.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/969/1*ewOjH2XMFYwEAPYpmat8SQ.png" /><figcaption>Group similar user journey cards together such as; Searching items and browsing items.</figcaption></figure><p>Now that we have mapped out and grouped the user journey, we have our product’s features. A feature is a part of the functionality of the software, it is generally too big to be one user story. Each feature is broken down into small bite size pieces of work, these are called stories.</p><p>The key to this story writing task is keeping each story as small as possible, without making each one dependent on the other (I believe the text book term is acronymed as ‘I.N.V.E.S.T.’). This means, stories can be done in any order without relying on any other story to be complete. These story cards can be stuck below their respective feature card, going vertically down the board, repeat this task until you have gone through each feature. Once this task is complete, your board will start looking a lot more fleshed out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/965/1*0KKMnX2ecqc6ivAHoCTGWA.png" /></figure><p>As you can see above, we now have stories for each feature. These stories can and probably will be split and broken down further as they get elaborated. How we go about splitting stories in Elaboration is a topic for perhaps another blog.</p><p>Story priority should be based on what provides the <strong>most value in the least amount of time</strong>, referred to as your minimal viable product or MVP. There are many methods of doing this but I like to keep it simple and categorise stories with the group as ‘must have’ &amp; ‘nice to have’. ‘Must have’ stories remain higher on the list and ‘nice to have’ stories are moved towards the bottom. Once again we repeat this for each feature and story. It should look something like the diagram below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/966/1*bbDYXKxbpthBZwg8OI4MNQ.png" /><figcaption>The story hierarchy makes more sense now</figcaption></figure><p>Now it’s time for the Developer and Tester to size each story. As we are still working at a high level, I like to use t-shirt sizing estimations. How much work is involved in accomplishing each story; S, M, L, XL. I know some prefer to size before prioritising but I don’t. I always put the customer first, customer satisfaction is my primary indicator for project success. I favour business value over fast delivery. Once we have estimated, we can determine two more pieces of information:</p><ol><li>Our Epics — Epics are large chunks of work comprising of one or more features. They are the <em>backbone</em> of a project and help provide a high level structure of what is ‘done’ and what is ‘in progress’. However, determining what an epic is, is quite subjective. There are no set rules of what a large chunk of work is. We group features into epics based on the size and the effort required. It can look something like this:</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/976/1*gn3cUZ0c4OaadA3D0__SjA.png" /><figcaption>This is grouped based on sizing and related features.</figcaption></figure><p>2. Our sprint runway — This is a rough timeline of how long it will take to complete our MVP and our additional ‘nice to have’ stories. If you release after every sprint, this runway also shows how many releases you will need to accomplish the MVP. To determine how many of your stories go into a sprint we rely on the sizing and priority exercises completed earlier, along with the estimated capacity the team can achieve in a sprint.</p><p>This will conclude the final step in your user story mapping session and you will most likely have a board similar to this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/983/1*NhXeUzQqDzRCs2KjI0347A.png" /><figcaption>Red sprint lines can resemble the products MVP and the black sprint lines are the nice to have stories</figcaption></figure><h3><strong>Summary</strong></h3><p>In my experience, user story-mapping can take anywhere from 2–8 hours to complete. In this time, a timeline is created to provide a structured view of the project.</p><p>You know you have done a successful Story Map when your outputs are:</p><ol><li>Customer centric conversations</li><li>Team collaboration</li><li>Initial identification of your MVP</li><li>Finger in the air indicative time-frames</li><li>Providing a structured approach to identifying Epics, Features and User Stories</li><li>Transparent stakeholder high-level view of the product or project</li></ol><p>Thanks for reading — my name is David Rizkilla.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=71cda7cb7eb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/momenton/leveraging-user-story-mapping-to-anchor-your-mvp-71cda7cb7eb">Leveraging User Story mapping to anchor your MVP</a> was originally published in <a href="https://medium.com/momenton">Momenton</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>