<?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 Eleonora Elefante on Medium]]></title>
        <description><![CDATA[Stories by Eleonora Elefante on Medium]]></description>
        <link>https://medium.com/@eleonoraelefante?source=rss-3b8c1c0b7a54------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Stories by Eleonora Elefante on Medium</title>
            <link>https://medium.com/@eleonoraelefante?source=rss-3b8c1c0b7a54------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 20:45:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@eleonoraelefante/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[Our software development project workflow: from client’s brief to product development]]></title>
            <link>https://medium.com/@eleonoraelefante/our-software-development-project-workflow-from-clients-brief-to-prodct-development-cc2c56e67409?source=rss-3b8c1c0b7a54------2</link>
            <guid isPermaLink="false">https://medium.com/p/cc2c56e67409</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[workflow]]></category>
            <dc:creator><![CDATA[Eleonora Elefante]]></dc:creator>
            <pubDate>Tue, 15 Feb 2022 14:54:43 GMT</pubDate>
            <atom:updated>2022-03-01T21:23:41.479Z</atom:updated>
            <content:encoded><![CDATA[<h4>A quick journey trough our process of software development.</h4><p><strong><em>Project workflow: </em></strong><em>a sequence of activities or cycles you need to do to complete a project</em>.</p><p>In this article, I am going to share the workflow that my team and I adopted for our last software development project, as we had the chance to test it and found it very efficient.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Moma65IveppR5HdWqnlZuw.png" /></figure><p>However, keep in mind that each project is unique and there is no magic formula nor a workflow that fits all kinds of projects: for this reason it is essential to keep flexible, understand your project’s peculiarities and customize the workflow accordingly.</p><p>Also, this article will provide you with a general overview but of course there are much more mini-cycles in each sub-phase and I might deepen them in more specific posts.</p><h3>Project workflow</h3><p>Here is the scheme of our entire workflow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jRemSMc1h792Gv1dZDVnow.png" /></figure><p>Let’s give it a closer look together, phase by phase.</p><p><strong>👉🏼 Phase 1: From the client brief to the solution backlog</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NpICsINllxQU0998IS9tbQ.png" /></figure><p>Everything starts with the <strong><em>client brief</em></strong><em>: </em>we talk with our client and discuss their requests, needs, issues, etc.</p><p>On that basis, we develop our <strong><em>research plan</em></strong> which generally includes: <br><strong>1.</strong> the essential question that is going to drive the research;<br><strong>2. </strong>research method;<br><strong>3.</strong> main guiding questions;<br><strong>4. </strong>research activities and sources;<br><strong>5.</strong> research outcome;<br><strong>6.</strong> research timeline;</p><p>Once this is complete, the research can start. <br>In this phase, we collect the necessary data to confirm or identify the <strong><em>problem statement</em></strong> and the <strong><em>requirements</em></strong> the solution must meet.</p><p>With a clear problem statement and solution requirements, we can create a <strong><em>solution</em> <em>backlog</em></strong>, which contains the solution requirements in the form of <em>user stories</em>.</p><p>The user stories are then prioritized according to what is most relevant for our client and/or end-users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U5Bo8nLz1F2BIi3zSTP4nQ.png" /><figcaption>Solution backlog example</figcaption></figure><h4><strong>👉🏼 Phase 2: From the solution backlog to the timeline development</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XhuVRAHluTYU3ky8lrgvqw.png" /></figure><p>Once we have defined the backlog, we can brainstorm about the possible <strong><em>solutions</em></strong> (the end-product) and proceed with the <strong><em>prototyping</em></strong>.</p><p>In the meantime, the <strong><em>technical investigation </em></strong>starts: in this phase, we aim to understand possible technical boundaries and identify the technologies that could fit the product at best.</p><p>Once the prototype is ready, the solution gets <strong><em>reviewed </em></strong>with the client and/or <strong><em>tested</em></strong> with end-users.</p><p><strong>Case 1: </strong><br>The solution prototype is rejected. In this case, we reiterate the research process and come up with a new solution.</p><p><strong>Case 2: </strong><br>The solution needs some changes. In this case, we integrate the client’s or users feedback in our requirements list, have a short research iteration and design a new prototype version, which is tested again until the solution is approved.</p><p><strong>Case 3: </strong><br>The solution is approved. In this case, we proceed with the definition of the <strong><em>Minimum Viable Product</em></strong><em> </em>to be developed by a certain date.</p><h4><strong>Phase 3: From the project timeline </strong>until the end of the development</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S-UZM9wPTo0hhiwraMQDSw.png" /></figure><p>The <strong><em>project timeline</em></strong> is designed according to the product backlog: <br>we split the user stories into smaller <strong><em>tasks</em></strong>. Depending on the difficulty of the task and on members’ expertise, we make a time estimation for each of them. Then we split tasks into <strong><em>Sprints </em></strong>and<strong><em> </em></strong>assign tasks to team members.</p><p>During the implementation, we keep the team aligned with <strong><em>d</em>aily stand-up meetings</strong><em> </em>where we update the <strong><em>sprint task board</em></strong>. We keep track of the work by moving tasks in these categories: <em>not started</em>, <em>in progress</em>,<em> to review</em>, <em>completed</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P8f6c0-F8IV-dQXNoMm10g.png" /><figcaption>Sprint task board example</figcaption></figure><p>In the meantime, <strong>new client requests </strong>may arise. <br>In this case, we evaluate the client request and, depending on its relevance, we try to integrate it into the next Sprints backlog.</p><p><strong>At the end of the Sprint:</strong> <br>We review the work done and test the product with the client and/or end-users. If something is not completed or doesn’t work properly, we move it to the next Sprint and adjust our plan.</p><p>This Sprint-cycle repeats until every user story of the solution backlog are complete and your solution is tested and ready for <strong><em>delivery</em></strong>. 🥳</p><h4>Conclusions: lessons learned</h4><p>In conclusion, I’d like to share a few of our lessons learned during our experience:</p><ul><li><strong>Be flexible<br></strong>You need to accept that your plan will change many times: your client will ask you to add or edit product requirements, unexpected things will happen, bugs will come up when you least expect it. Be patient.<br>Have a plan but embrace continuous change.</li><li><strong>Take some time for team reflections <br></strong>Allow your team to take some time to reflect on how things are going. <br>One of our good practices is to have <strong><em>retrospective meetings </em></strong>at the end of each Sprint. During this meeting, we reflect on our workflow to identify the processes that are effective, the ones that can be improved, and to learn from our mistakes.</li><li><strong>Develop your own workflow </strong><br>Methods and frameworks are essential guidance but following them to the letter could mislead you sometimes. That’s why it is important to be sensitive about what your project and team need and adapt those processes to them.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cc2c56e67409" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How field research helped us to create a meaningful iOS app for hospital nurses]]></title>
            <link>https://medium.com/apple-developer-academy-federico-ii/how-field-research-helped-us-to-create-a-meaningful-ios-app-for-hospital-nurses-670c22ce70b5?source=rss-3b8c1c0b7a54------2</link>
            <guid isPermaLink="false">https://medium.com/p/670c22ce70b5</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[field-research]]></category>
            <category><![CDATA[apple-developer-academy]]></category>
            <category><![CDATA[human-centric-design]]></category>
            <dc:creator><![CDATA[Eleonora Elefante]]></dc:creator>
            <pubDate>Thu, 19 Mar 2020 16:46:32 GMT</pubDate>
            <atom:updated>2020-05-30T17:54:19.078Z</atom:updated>
            <content:encoded><![CDATA[<p>A human-centered design case study on how field research and observations completely changed our project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JO3ylzuP9nrluZjgGMNG6w.jpeg" /></figure><p>First, let me introduce you who we are: <br>We are the <strong>weirdOS</strong> <strong>team,</strong> a group of students from the <em>Apple Developer Academy in Naples (Italy)</em>. We started working together during a <em>MiniChallenge</em> in February 2020 and that’s how our project was born.</p><p>Now let’s start by giving you <strong>more information about the project</strong>:</p><ul><li>The goal was to create something that could solve a read human need <br> HOW? Using <a href="https://medium.com/dc-design/what-is-human-centered-design-6711c09e2779"><strong>Hu<em>man-Centered Design</em></strong></a>.</li></ul><p>The key of this approach is <em>empathy</em>: you have to deeply understand your user, his gains, his pains, his needs.</p><ul><li>The Persona we decided to focus on was a <strong>Nurse</strong>. Why? My mom is a nurse, and also all the members of the team have contacts with nurses: this is important because having real and physical contact with your potential user is crucial and has to be easy.</li></ul><h3>Let’s talk about the <strong>research process</strong>:</h3><h4>First step:<strong> interviews</strong>.</h4><p>We interviewed many nurses in order to know more about their daily tasks. <br> We conducted <strong>10 interviews </strong>and we started to understand more about their work day. <br> Here an example of the kind of questions we asked: <br> • What are your main activities at your work, jobs to be done?<br> • What do you like most in your job? What do you like the least?</p><p>As you can see, these questions are all about “WHAT”. But actually, what we really needed to know, it was <strong>HOW </strong>and <strong>WHY</strong>. That’s why, even if we collected a lot of information, we still didn’t find something we could really work on; we were stuck because we were still on the surface.</p><h4>Second step: <strong>field research</strong>.</h4><p>This is what really brought us the turning point in the project.</p><p>We spent a day in the hospital, observing nurses carrying out their tasks. We could finally share their point of view, and this, trust me, changed everything.</p><ul><li>First because after the first few hours there we could already throw away some previous assumptions and ideas: we clearly saw why some solutions we were thinking about would never fit our User Persona.</li><li>Second because when you ask someone to tell you about his daily tasks, it might be that he doesn’t tell you things that he takes for granted but that are still relevant to your research, that’s why <strong>you need to see with your eyes</strong>.</li></ul><p>But what happened during our “visit” into the hospital?</p><p>While observing the work in the Oncology department of the hospital, a nurse in particular captured our attention: the <strong><em>head-nurse</em>.</strong></p><p>That’s how we met Alfredo, here he is while working:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/907/1*Re8UBK0wIS4oqArGaYTnPw.jpeg" /></figure><p>Alfredo is the heart of his department:</p><ul><li>He mediates the communication between doctors and nurses, doctors and patients, doctors and patients’ families, patients and nurses</li><li>He gives and receives information to and from the administration of the hospital</li><li>He organizes shifts</li><li>He takes care of the pharmacy of the department</li><li>And, most importantly, he has to constantly insert data about all these things and keep these information always in mind.</li></ul><p>All this things at the same time! It’s crazy, isn’t it?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TEJJRG9YKeX8o3Y_4qjQxA.jpeg" /><figcaption>Alfredo’s desk. It was very useful for us to see how he organizes all the data he has to manage.</figcaption></figure><p>Moreover, while we were there <strong>something unexpected happened</strong>:</p><p>A doctor came to the head-nurse and was really angry and screamed at him: the doctor was in the surgery room going to operate on a complicated patient but then he realized that they forgot to give the patient an anesthesiological consultation so he couldn’t proceed with the surgery. And as you know, time is crucial in this kind of things.</p><p>Let me explain to you how it works: before a surgery every patient has to perform some pre-operation protocols (including the anesthesiological consultation). These protocols are almost always the same for any kind of surgery; the head nurse doesn’t have the responsibility to perform them but he absolutely has the responsibility <em>to check</em> and to ensure, <em>on time</em>, that the protocols have been performed.</p><p>And that’s how we came up with <strong>our solution</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XBVHLBd48ywhAfkY_pPwpg.png" /></figure><p>Well, you can clearly see how much the time spent in the real world helped us:</p><ul><li>We found a new more specific User Persona, not just a nurse, but an head-nurse.</li><li>We found out what we could NOT do: there are some things that you can’t replace with your eventual product.</li><li>WE FOUND A REAL SPECIFIC PROBLEM TO WORK ON.</li></ul><h4>Third step: <strong>prototyping</strong>.</h4><p>Well, even if you finally found your solution you don’t have to forget about your Persona. We prototyped by <em>collaborating with our User Person</em>a, asking him <em>feedback </em>and making changes based on these.</p><p>Our main goal it was to make the user experience as <em>comfortabl</em>e and <em>quick</em> as possible: we don’t want to steal precious time from our user.</p><p>Here there is the<strong> evolution of our prototype:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4QlKVR8RDMBaMewn2eJfQg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uzMps_9sJaGQmB_RVfC9hg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*03R-EazysPeDi4y_slH9ZA.png" /></figure><h4>Now, the point of this story is:</h4><p>If we didn’t go to the hospital we would never have stumbled upon this need and probably we would have created something useless based on our assumptions. <br>If you really want to create something <em>meaningful</em> for you user, nothing is better than <strong>going out into the real world</strong> and <strong>observe with your eyes</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HNrw98y9p-YbsxHucnzSBA.png" /></figure><h4>And here we are:</h4><p>Giovanni, Antonio, Francesco, Ekaterina, Eleonora and Claudia :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZSUB8I3pg5OpyrySoGunhg.jpeg" /></figure><p>Thanks for reading. Hope you enjoyed!</p><p><a href="https://medium.com/u/24ff46cbb158">Antonio Mennillo</a>, <a href="https://medium.com/u/f50f36c88a70">Claudia Catapano</a>, <a href="https://medium.com/u/2b231a78b097">Ekaterina Akchurina</a>, <a href="https://medium.com/u/8508c03f89b6">Arena Francesco</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=670c22ce70b5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/apple-developer-academy-federico-ii/how-field-research-helped-us-to-create-a-meaningful-ios-app-for-hospital-nurses-670c22ce70b5">How field research helped us to create a meaningful iOS app for hospital nurses</a> was originally published in <a href="https://medium.com/apple-developer-academy-federico-ii">Apple Developer Academy | Federico II</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>