<?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 Gabriella Annunziata on Medium]]></title>
        <description><![CDATA[Stories by Gabriella Annunziata on Medium]]></description>
        <link>https://medium.com/@gabriella.annunziatana?source=rss-40b747ed0ed1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*jjA019z7XYvB-1Qh</url>
            <title>Stories by Gabriella Annunziata on Medium</title>
            <link>https://medium.com/@gabriella.annunziatana?source=rss-40b747ed0ed1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 01:41:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@gabriella.annunziatana/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[A guide for your first Product Backlog]]></title>
            <link>https://medium.com/@gabriella.annunziatana/a-guide-for-your-first-product-backlog-486c9f90c65c?source=rss-40b747ed0ed1------2</link>
            <guid isPermaLink="false">https://medium.com/p/486c9f90c65c</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[process]]></category>
            <category><![CDATA[backlog]]></category>
            <category><![CDATA[agile-development]]></category>
            <dc:creator><![CDATA[Gabriella Annunziata]]></dc:creator>
            <pubDate>Thu, 30 Mar 2023 11:12:14 GMT</pubDate>
            <atom:updated>2023-03-30T23:08:03.995Z</atom:updated>
            <content:encoded><![CDATA[<h3>Overview</h3><p>The first approach to <strong>Agile</strong> methodologies might be quite confusing and overwhelming; you can find a lot of information about the topic with all the different applications of Agile. The subject in question is something not easy to discuss expecially if we are talking about planning and overseeing an entire project. How to efficiently create an action plan?</p><p>While designing any kind of product, the most helpful tool you could consider is sectioning the whole into more approachable items; in this way you might find easier to vision your future plan and prioritize the work. This is one of the main elements in Agile methodologies and you can see the adaptation of this concept in the making of <em>Sprints</em>: the whole process is divided in<strong> short</strong> <strong>fixed time frames</strong> that induce a frequent deliver of the product in order to better respond and adapt to the possible changes requested by the stakeholders.</p><h3>Product Backlog</h3><p>If you are working with Agile for your project and you have chosen the methodology that better fits your team needs, you certainly are facing one of the key point of project planning: the product backlog. The first question that comes up naturally is:</p><h4>What is a product backlog?</h4><blockquote>A product backlog is a list of the new features, changes to existing features, bug fixes, infrastructure changes or other activities that a team may deliver in order to achieve a specific outcome. <em>(1)</em></blockquote><p>But does the product backlog consist just of tasks? Not really, we can refer to it as the<strong> single source of work</strong>: all the work that is needed for the realization of the project is in the backlog, with relative priorities, estimation of effort and completion status. Now that we know broadly what are we talking about , it’s time to ask the second crucial question:</p><h4>How to build a product backlog?</h4><p>To better understand the topic in this article I propose a practical example of a real backlog created for an app developed by my team. It is called <strong>Unori.</strong> To give you some context, Unori is an app to learn (?) American and Italian sign language, created for parents of deaf children.</p><p>The first step into creating your own product backlog is having <a href="https://www.visual-paradigm.com/guide/agile-software-development/what-is-user-story/">user stories</a>. As a reminder, the usual structure of a user story is : &lt;&lt; <em>As [role] I want to [functionality] so that I can [benefit] </em>&gt;&gt;.</p><p>Be careful to always write the user story from the perspective of the end-user and try not to be too specific and precise in this early stage of the process.</p><p>The <em>role </em>refers to a characteristic trait of the user persona that proves essential in order to define the main target of our project.</p><p>The user persona of Unori is Matilde, 35 years old, that works as a translator for a publishing company. She has a child, Giulio, a 4 years old boy born with a hearing impairment. Matilde doesn’t have much free time but in order to create a connection with Giulio, and help him develop, she takes time to study and research about deaf community.</p><p>After analyzing the user needs and pains we wrote these initial user stories:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iSraU_tBmF8jtOh9ufUMdA.png" /></figure><p>These are all useful and essential user stories, but to be practical and to plan an effective backlog we need to prioritise some user stories. One of my favourite methods of prioritisation is <a href="https://www.agilebusiness.org/dsdm-project-framework/moscow-prioririsation.html"><strong>MoSCoW</strong></a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3VHLQOorxYXncYtpD-Wm9w.png" /></figure><p>At first you should focus on the user stories that you must have in the product implementation. The main reason is that without these stories the product itself doesn’t have any value because they aim to fulfill the user’ basic needs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MKNV5-76ClRSBbU3JBrtug.png" /></figure><p>If during the entire process you keep in mind or visible to the whole team your <strong>MVP -</strong> <a href="https://www.netsolutions.com/insights/what-is-a-minimum-viable-product-mvp/">Minimum Viable Product</a> - it can be easier to choose what is really important and should have higher priority.</p><p>Talking from experience, you should <strong>always define and stick to the MVP</strong>.</p><p>In fact, while working on the backlog for Unori, the team realised that the initial idea we had of the project couldn’t be delivered in the time required mostly because we were working with technologies that were new to the developers, and also the UX needed further analysis. So we refined our MVP and created more specific user stories to implement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/764/1*j-idwxwx0nIGYgeuoB4jQw.png" /></figure><h4>How to plan the implementation of a user story?</h4><p>We have talked about <strong>tasks</strong> and how big of a role they play in the construction of a backlog, but how to create tasks?</p><p>Once you choose the starting user story, you can define the various steps in order to achieve the completion of the story: this is a <em>bottom-up</em> approach. At first you can be generic in the description of the task and later on add more information and details.</p><p>The task should have a <strong>descriptive name</strong>, should be <strong>assigned</strong> to specific team members and also have a <strong>completion status</strong> (to do-in progress-completed).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jl6o5qCM8pBeE_e4yvcOpw.png" /></figure><p>In the example above, the user story I’m referring to is:</p><p>&lt;&lt;<em>Matilde wants to learn useful words in sign language in order to communicate with her child</em>&gt;&gt;.</p><p>You might have noticed that in this case the implementation of the story is divided into two sprints since we have already done the most crucial part of an efficient product backlog: <strong>the effort estimation</strong>.</p><p>One of the most difficult part of planning is the prediction of the obstacles and uncertainties you could face on the road. If the team lacks pragmatism or realism, these obstacles could create delay on timeline and lead to a possible failure.</p><p>Each user story has a relative effort estimation based on the level of <strong>risk</strong>, <strong>repetition</strong> and <strong>complexity.</strong></p><blockquote>Risk is the amount of total risk or uncertainty associated with the task. For instance, if the task involves third parties, contractors, or project stakeholders, it can increase the amount of risk.</blockquote><blockquote>Repetition is the team’s experience with similar tasks.</blockquote><blockquote>Complexity is the task’s level of difficulty (and how clear the objectives of the task are). (2)</blockquote><p>You could either estimate the entire user story or each task if you already divided the work.</p><h4><strong>How to estimate the effort?</strong></h4><p>The most used method for the estimation in Agile project management consists of story points that could be considered real units of measurement.</p><blockquote>Story points are relative measurements: the value of the story points assigned to each user story depends on the team, the tasks, and how the developers perceive the potential risks. (3)</blockquote><p>If you decide to use story point rather than a time-based estimation, you should decide on which kind of sequence your story points refer to. The sequence doesn’t have to be strictly numerical. Be creative and find what works for your team - you could even use t-shirt sizing as a sequence! - .</p><p>The most famous is the Fibonacci sequence, often modified to make it simpler (1, 2, 3, 5, 8, 13, 20, 40, 100).</p><h4>Definition of Done</h4><p>The last step of proper product backlog is the individuation of specific success criteria in accordance with your team. It is fundamental to come up with a clear definition of when the task, or the user stories, are unanimously considered as completed.</p><h3>Links</h3><p>(1) <a href="https://www.agilealliance.org/glossary/backlog/#q=~(infinite~false~filters~(postType~(~&#39;page~&#39;post~&#39;aa_book~&#39;aa_event_session~&#39;aa_experience_report~&#39;aa_glossary~&#39;aa_research_paper~&#39;aa_video)~tags~(~&#39;backlog))~searchTerm~&#39;~sort~false~sortDirection~&#39;asc~page~1)">https://www.agilealliance.org/glossary/backlog/#q=~(infinite~false~filters~(postType~(~&#39;page~&#39;post~&#39;aa_book~&#39;aa_event_session~&#39;aa_experience_report~&#39;aa_glossary~&#39;aa_research_paper~&#39;aa_video)~tags~(~&#39;backlog))~searchTerm~&#39;~sort~false~sortDirection~&#39;asc~page~1)</a></p><p>(2) <a href="https://asana.com/resources/story-points">https://asana.com/resources/story-points</a></p><p>(3) <a href="https://www.mountaingoatsoftware.com/blog/what-are-story-points">https://www.mountaingoatsoftware.com/blog/what-are-story-points</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=486c9f90c65c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[API Implementation]]></title>
            <link>https://medium.com/@gabriella.annunziatana/api-implementation-9c3dcd08cb3e?source=rss-40b747ed0ed1------2</link>
            <guid isPermaLink="false">https://medium.com/p/9c3dcd08cb3e</guid>
            <category><![CDATA[app-development]]></category>
            <category><![CDATA[swiftui]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Gabriella Annunziata]]></dc:creator>
            <pubDate>Tue, 07 Feb 2023 13:31:41 GMT</pubDate>
            <atom:updated>2023-03-30T11:09:23.702Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Overview</strong></h3><p>One of the feature of the app consisted of a place to find various resources to consult regarding IT fields, for this reason we chose to implement Google Books APIs; it gives you programmatic access to many of the operations available on Google Books website. Some of the main features that we used are:</p><ul><li>Search and browse through the list of books that match a given query;</li><li>View information about a book, including metadata, availability and price.</li></ul><h3><strong>Implementation</strong></h3><p>After reading the documentation of Google Books, the first step was creating a model to code and decode the JSON file with the information of the books. This is an example of the JSON structure:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u1Pzbtk5oCxnlqrilVqG-Q.png" /></figure><p>We created a struct, Library, that conforms to the Decodable protocol and has an array of items of type Book, than following the guidelines of the file, we created a set of substructures of Library as shown below:</p><pre>struct Library: Decodable {<br>    var items: [Book]<br>    struct Book: Identifiable, Decodable {<br>        let id = UUID()<br>        var volumeInfo: VolumeInfo<br>        struct VolumeInfo: Decodable {<br>            let title: String?<br>            let authors: [String]?<br>            let description: String?<br>           var imageLinks: ImageLinks?<br>            struct ImageLinks: Decodable {<br>            var thumbnail: String?<br>    }<br>}</pre><p>The app uses a view model, BooksViewModel, to act as a central point for fetching data. It is implemented as an ObservableObject, so it can leverage SwiftUI&#39;s state management system:</p><pre>extension LibraryView {<br>    @MainActor class BooksViewModel: ObservableObject {<br>        @Published var itFields: [ITField]<br>        init() {<br>            // Initialize all the IT fields<br>            itFields = [<br>                ITField(title: &quot;iOS-Development&quot;),<br>                ITField(title: &quot;Android-Development&quot;),<br>                ITField(title: &quot;Web-Development&quot;)<br>            ]<br>            Task { await setBooks() }<br>        }<br>        // Initialize all the books by calling Google Books API<br>        func setBooks() async {<br>            do {<br>                for fieldPosition in 0 ..&lt; itFields.count {<br>                    // Initialize the books of the IT field<br>                    try await itFields[fieldPosition].books = getBooks(<br>                        url: &quot;https://www.googleapis.com/books/v1/volumes?q=\(itFields[fieldPosition].title)&quot;<br>                    )<br>            } catch {<br>                print(&quot;Error getting books: \(error.localizedDescription)&quot;)<br>            }<br>        }<br>        // Return all the decoded JSON of the API call<br>        func getBooks(url: String) async throws -&gt; Library? {<br>            guard let url = URL(string: url) else {<br>                fatalError(&quot;Missing URL&quot;)<br>            }<br>            do {<br>                let (data, _) = try await URLSession.shared.data(from: url)<br>                let decodedData = try JSONDecoder().decode(Library.self, from: data)<br>                return decodedData<br>            } catch {<br>                print(error.localizedDescription)<br>                return nil<br>            }<br>        }</pre><p>Let’s discuss what’s going on here!</p><p>The app requires the access to books regarding three subjects: iOS Development, Android Development and Web Development; for this reason the call to the API is made using these URL queries.</p><p>The type ITField has a variable called “books”, of type Library, that is applied when the function setBooks is used. Both the functions are executed asynchronously and utilised the do - catch statement to achieve error handling.</p><p>The function getBooks has the main scope of decoding the JSON file, using the JSONDecoder.</p><p>The last and the easier step of the implementation is calling the functions in the specific view that needs the API content, than the app should be built successfully.</p><h3><strong>Conclusion</strong></h3><p>This is a simplified way to implement an API in your app and we could improve the way errors are handled. We hope you find this useful and wish to hear your reviews.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TDd44FAoffAPivpiQUWGHA.png" /></figure><p><strong>Resources</strong></p><p><a href="https://developers.google.com/books/docs/overview">https://developers.google.com/books/docs/overview</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9c3dcd08cb3e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>