<?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 Karim B on Medium]]></title>
        <description><![CDATA[Stories by Karim B on Medium]]></description>
        <link>https://medium.com/@karim.kb?source=rss-635e88926584------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*0NjPcks0OJ4mrW0ZmVzcXg.jpeg</url>
            <title>Stories by Karim B on Medium</title>
            <link>https://medium.com/@karim.kb?source=rss-635e88926584------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 15:54:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@karim.kb/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[Agile, But Not Quite]]></title>
            <link>https://medium.com/@karim.kb/agile-but-not-quite-77067b67e13b?source=rss-635e88926584------2</link>
            <guid isPermaLink="false">https://medium.com/p/77067b67e13b</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Karim B]]></dc:creator>
            <pubDate>Thu, 23 Jan 2025 12:33:33 GMT</pubDate>
            <atom:updated>2025-01-23T12:36:48.282Z</atom:updated>
            <content:encoded><![CDATA[<h3>Agile, But Not Quite : The Shift from Principles to Convenience</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/896/1*QQ_nsIPH-7SFBBwFuRdwXg.jpeg" /></figure><h3>As a Product Owner, I’ve had the privilege (and sometimes the challenge) of working with various organizations across different industries. And one thing has become abundantly clear: while many companies claim to be “agile,” few actually embrace the Agile Manifesto as it was originally intended. Instead, agility is often twisted and bent to fit the unique context of the company.</h3><h3>The Agile Manifesto: A Quick Recap</h3><p>The Agile Manifesto, created by a group of software development professionals, is built on four key values:</p><ol><li><strong>Individuals and interactions over processes and tools</strong></li><li><strong>Working software over comprehensive documentation</strong></li><li><strong>Customer collaboration over contract negotiation</strong></li><li><strong>Responding to change over following a plan</strong></li></ol><p>Along with these values, there are 12 principles that emphasize continuous delivery, simplicity, regular reflection, and collaboration. These principles were meant to guide companies toward a more flexible, collaborative, and iterative way of working.</p><p>But in practice? Not so much.</p><h3>The Reality: Agility Based on Convenience</h3><p>Many organizations, especially larger enterprises, take an “agile-adjacent” approach, adopting only parts of the framework that suit their existing processes. In fact, it’s common to see teams following Agile practices only superficially, while continuing to operate with traditional, waterfall-like structures behind the scenes.</p><p>This isn’t necessarily a result of malice; it’s often the result of context and convenience. Agile principles require a shift in culture, mindset, and processes. For many companies, especially those entrenched in old ways of working, this can be a huge leap. So, instead of making those changes, they adjust the Agile framework to fit within their comfort zones, which often means straying far from the original intent.</p><h3>Agility on Paper, Not in Practice</h3><p>One of the most obvious examples of this phenomenon is the way many companies interpret “responding to change over following a plan.” In theory, this means that teams should be flexible, adaptive, and open to shifting priorities as new information or market changes arise. In reality, many organizations still adhere to strict yearly roadmaps and rigid project deadlines. Instead of responding to change, they often try to control and predict every aspect of the project, creating a paradox where teams are labeled as “agile,” but are still operating under a traditional mindset.</p><p>Another key issue is the misunderstanding of <strong>“individuals and interactions over processes and tools.”</strong> Many organizations that claim to be Agile focus heavily on the tools : Jira, Confluence, etc ; and the processes : daily standups, sprints, retrospectives, without putting enough emphasis on building a culture of collaboration and trust within teams. Agile is about empowering individuals, yet too often, the focus is placed on “following the rituals” rather than genuinely fostering autonomy and accountability.</p><h3>Agile for the Sake of Agility</h3><p>What I often see in practice is that companies adopt Agile because it’s a buzzword and they believe it’s the key to success. However, they don’t deeply embrace its principles or modify their structure to truly foster agility. Instead, they’re often looking for a quick fix, a way to claim they’re “agile” without fundamentally altering how they work.</p><p>There’s a big difference between <strong>saying you’re Agile</strong> and <strong>being Agile.</strong> When companies just pay lip service to Agile and try to shoehorn it into their existing operations, they run into a situation where their “agility” is often nothing more than a set of rituals and buzzwords, disconnected from the real value it’s meant to bring.</p><h3>The Consequences of a Misaligned Agile Mindset</h3><p>When Agile principles are not applied authentically, teams can become disillusioned. What started as an experiment in innovation and collaboration turns into just another framework to be checked off. As a Product Owner, I’ve seen how this lack of true commitment can lead to frustrated teams, decreased productivity, and a lack of real progress. People follow the motions, but they don’t see the deeper value of Agile in how they work or how they create products.</p><p>This misalignment can also create disconnects between teams and stakeholders, as the original goal of increasing customer collaboration often gets lost in the shuffle of internal processes and politics. Instead of focusing on delivering working products that solve real customer problems, teams can end up prioritizing internal processes, documentation, or other less impactful activities.</p><h3>So, What Can We Do?</h3><p>If we want to bridge the gap between how companies <em>say</em> they’re agile and how they <em>really</em> are, we need to start by embracing the true spirit of Agile. This means focusing not just on the rituals, but on fostering a culture of collaboration, trust, and continuous improvement. It’s about creating an environment where change is welcomed, feedback is acted upon, and teams are empowered to make decisions that drive value for the customer.</p><p>As Product Owners, we need to be advocates for this mindset, helping to bridge the gap between corporate realities and Agile ideals. We must encourage our teams to embrace the principles of the Agile Manifesto, not because it’s trendy, but because it delivers real value to customers, employees, and the organization as a whole.</p><p><strong>In Conclusion</strong></p><p>The Agile Manifesto offers a vision of a more flexible, responsive, and collaborative way of working. But for many organizations, it remains just that, a vision. Until companies embrace Agile as a culture and not just a framework, the gap between what they say and what they do will continue to widen. As Product Owners and leaders, it’s up to us to push for true agility, one that is about continuous improvement and delivering value to customers, not just checking off boxes on a list.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=77067b67e13b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding the Differences Between SAFe and Scrum: Choosing the Right Agile Framework]]></title>
            <link>https://medium.com/@karim.kb/understanding-the-differences-between-safe-and-scrum-choosing-the-right-agile-framework-dac2a49a6d09?source=rss-635e88926584------2</link>
            <guid isPermaLink="false">https://medium.com/p/dac2a49a6d09</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[safe]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Karim B]]></dc:creator>
            <pubDate>Tue, 09 Apr 2024 15:40:38 GMT</pubDate>
            <atom:updated>2024-04-09T15:49:19.293Z</atom:updated>
            <content:encoded><![CDATA[<h3>Understanding the Differences Between SAFe and Scrum</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4z46TA0bEoz4eenmCff24A.png" /></figure><h3>INTRODUCTION</h3><p>In the world of Agile methodologies, two popular frameworks stand out: SAFe (Scaled Agile Framework) and Scrum. While both aim to enhance agility and streamline development processes, they have distinct characteristics and are suited to different organizational needs. In this article, we’ll explore the key differences between SAFe and Scrum to help you choose the right framework for your project or organization.</p><h3>KEY CONCEPTS</h3><h4>Scale and Scope:</h4><ul><li><strong>SAFe</strong>: Designed for large-scale enterprises and complex projects involving multiple teams, departments, or business units. It provides guidance on how to coordinate and synchronize work across the organization, aligning teams to a common mission and vision.</li><li><strong>Scrum</strong>: Primarily used for small to medium-sized teams working on single projects or products. It focuses on iterative and incremental development, with a strong emphasis on self-organization, collaboration, and delivering value in short iterations.</li></ul><h4>Organizational Structure:</h4><ul><li><strong>SAFe: </strong>Prescribes a hierarchical structure with various roles and responsibilities at different levels, including teams, programs (Agile Release Trains), and portfolios. It defines roles such as Release Train Engineer (RTE), Product Owner, and System Architect to facilitate coordination and alignment at scale.</li><li><strong>Scrum:</strong> Advocates for a flat organizational structure with three primary roles: Product Owner, Scrum Master, and Development Team. The emphasis is on self-organizing, cross-functional teams that have the autonomy to plan and execute work collaboratively.</li></ul><h4>Planning and Execution:</h4><ul><li><strong>SAFe:</strong> Emphasizes long-term planning and program increments (PIs), typically spanning 8–12 weeks. It includes ceremonies such as PI Planning, where teams synchronize their work and plan for the upcoming increment. SAFe also provides guidance on portfolio-level planning and governance.</li><li><strong>Scrum:</strong> Focuses on short-term planning and iterative delivery, with fixed-length iterations (sprints) typically lasting 2–4 weeks. The Sprint Planning, Daily Standup, Sprint Review, and Sprint Retrospective are key ceremonies that drive transparency, inspection, and adaptation within the team.</li></ul><h4><strong>Flexibility and Adaptability:</strong></h4><ul><li><strong>SAFe:</strong> Offers a comprehensive framework with built-in flexibility to accommodate various organizational structures, domains, and scaling challenges. It provides configurable elements and optional practices, allowing organizations to tailor SAFe to their specific context and needs.</li><li><strong>Scrum:</strong> Provides a lightweight framework with minimal rules and guidelines, promoting flexibility and adaptability within teams. While Scrum is less prescriptive than SAFe, it still requires adherence to its core principles and values to be effective.</li></ul><h3>ROLES</h3><h4>SAFe :</h4><ol><li><strong>Release Train Engineer (RTE)</strong>: A servant leader and chief Scrum Master for the Agile Release Train (ART), facilitating ART events and ensuring smooth operation.</li><li><strong>Product Manager / Product Owner</strong>: Responsible for defining and supporting the building of desirable, feasible, viable, and sustainable products that meet customer needs.</li><li><strong>System Architect</strong>: Defines the overall architecture of the system, identifies nonfunctional requirements, and designs interfaces and collaborations.</li><li><strong>Business Owners:</strong> Stakeholders with business and technical responsibility for fitness for use, governance, and return on investment (ROI) for a solution developed by an ART.</li><li><strong>Agile Teams:</strong> Cross-functional groups responsible for defining, building, testing, and deploying increments of value within short time frames.</li></ol><h4>Scrum :</h4><ol><li><strong>Product Owner</strong>: Represents the stakeholders and is responsible for maximizing the value of the product and the work of the Development Team.</li><li><strong>Scrum Master</strong>: Helps everyone understand Scrum theory, practices, rules, and values. Facilitates the Scrum process and ensures the team is following its practices.</li><li><strong>Development Team</strong>: A self-organizing and cross-functional group of individuals who collectively are responsible for delivering the increment of the product during each Sprint.</li></ol><h3>CEREMONIES</h3><h4>SAFe :</h4><ol><li><strong>PI Planning (Program Increment Planning)</strong>: A face-to-face planning event aligning all teams on the ART to a shared mission.</li><li><strong>System Demo</strong>: Provides an integrated view of new features delivered by all teams in the ART during a Program Increment.</li><li><strong>Inspect &amp; Adapt</strong>: A significant event where the current state of the solution is evaluated, and teams identify improvement backlog items.</li><li><strong>Coach Sync</strong>: Coordinates dependencies of ARTs and provides visibility into progress and impediments.</li><li><strong>Product Owner (PO) Sync</strong>: Provides visibility into ART progress and discusses problems or opportunities with feature development.</li><li><strong>ART Sync</strong>: Combines Coach Sync and PO Sync into a single event for an ART.</li><li><strong>Iteration Planning</strong>: Agile team determines iteration goals and commits to backlog items for an upcoming iteration.</li><li><strong>Iteration Review</strong>: Teams review the results of the previous iteration and adjust the backlog based on feedback.</li><li><strong>Iteration Retrospective</strong>: Teams reflect on their practices and identify ways to improve at the end of an iteration.</li><li><strong>Backlog Refinement</strong>: Teams refine, review, and estimate future stories and enablers in the backlog.</li><li><strong>Team Sync</strong>: Short daily meetings to inspect progress, communicate, and adjust upcoming work.</li></ol><h4>Scrum :</h4><ol><li><strong>Sprint Planning</strong>: A meeting where the team plans the work to be performed during the Sprint.</li><li><strong>Daily Standup</strong>: A short meeting where the team synchronizes activities and plans for the next 24 hours.</li><li><strong>Sprint Review</strong>: A meeting where the team demonstrates what they accomplished during the Sprint and gathers feedback.</li><li><strong>Sprint Retrospective</strong>: A meeting where the team reflects on their work during the Sprint and identifies improvements.</li></ol><h3>KEY WORDS</h3><h4>SAFe :</h4><ol><li><strong>Agile Release Train (ART)</strong>: A long-lived team of Agile teams that incrementally develops, delivers, and often operates one or more solutions in a value stream.</li><li><strong>Program Increment (PI)</strong>: A timebox during which an ART delivers continuous value, usually lasting 8–12 weeks.</li><li><strong>Continuous Delivery Pipeline</strong>: Describes the workflows, activities, and automation needed to release value to end-users constantly.</li><li><strong>Customer Centricity</strong>: A mindset and way of doing business focused on creating positive customer experiences.</li><li><strong>Design Thinking</strong>: An iterative solution development process ensuring solutions are desired by customers and users.</li><li><strong>Lean UX (User Experience)</strong>: A mindset, culture, and process that embrace Lean-Agile methods for designing user experiences.</li><li><strong>Built-In Quality</strong>: Practices established to ensure that outputs meet appropriate quality standards throughout the process.</li><li><strong>DevSecOps</strong>: A mindset, culture, and set of technical practices promoting communication, integration, automation, and cooperation.</li><li><strong>Innovation and Planning (IP) Iteration</strong>: Provides teams with dedicated time for exploration, planning, and learning.</li><li><strong>SAFe Scrum</strong>: A lightweight process for Agile teams to deliver value continuously within the SAFe framework.</li><li><strong>SAFe Team Kanban</strong>: A Lean-Agile method helping teams facilitate the flow of value by visualizing workflow and establishing work in process limits.</li></ol><h4>Scrum :</h4><ol><li><strong>Sprint</strong>: A time-boxed iteration, usually lasting 2–4 weeks, where the team works to deliver a potentially shippable product increment.</li><li><strong>Product Backlog</strong>: A prioritized list of all desired work on the project.</li><li><strong>Sprint Backlog</strong>: A subset of the Product Backlog selected for the Sprint, along with a plan for delivering the product increment.</li><li><strong>Increment</strong>: The sum of all the completed Product Backlog items at the end of a Sprint.</li><li><strong>Scrum Board</strong>: A visual representation of the work to be done, work in progress, and work completed during a Sprint.</li><li><strong>Definition of Done (DoD)</strong>: A shared understanding of the criteria that a product increment must meet before it can be considered complete.</li><li><strong>User Story</strong>: A brief description of a feature told from the perspective of the person who desires the new capability, usually written in the format: “As a [user], I want [feature], so that [benefit].”</li><li><strong>Burn Down Chart</strong>: A graphical representation of work left to do versus time, typically shown for each Sprint.</li></ol><h3>CONCLUSION</h3><p>SAFe and Scrum are both powerful Agile frameworks that offer unique approaches to managing projects and delivering value. The choice between SAFe and Scrum depends on factors such as organizational size, complexity, culture, and strategic objectives. By understanding the differences between these frameworks, organizations can make informed decisions and adopt the approach that best suits their needs. Whether scaling Agile across the enterprise with SAFe or adopting a more lightweight approach with Scrum, the ultimate goal remains the same: delivering value to customers quickly and effectively.</p><h3>Thank you :)</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dac2a49a6d09" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Scrum or Scrumban : Choosing the Right Agile Framework for Your Team]]></title>
            <link>https://medium.com/@karim.kb/scrum-or-scrumban-choosing-the-right-agile-framework-for-your-team-2d24c69d497c?source=rss-635e88926584------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d24c69d497c</guid>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[kanban]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Karim B]]></dc:creator>
            <pubDate>Wed, 27 Mar 2024 12:32:46 GMT</pubDate>
            <atom:updated>2024-03-27T12:32:46.240Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Scrum or Scrumban : Choosing the Right Agile Framework for Your Team</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4OKuv432le_3gtssmK4Lnw.png" /></figure><h3>Introduction</h3><p>As a product owner navigating the realm of Agile methodologies, the choice between Scrum and Scrumban can be both empowering and perplexing. Each framework presents unique opportunities and challenges, but ultimately, the decision rests on finding the best fit for your team’s needs and project requirements. In this story, we’ll explore the key differences between Scrum and Scrumban and help you decide which framework is best suited for your team.</p><h3><strong>Scrum: The Classic Agile Framework</strong></h3><p>Scrum is a well-established Agile framework characterized by its structured approach to project management. It consists of predefined roles, events, and artifacts that guide teams through iterative development cycles called sprints. Key elements of Scrum include:</p><ol><li><strong>Roles</strong>: Scrum defines three primary roles: the Product Owner, Scrum Master, and Development Team. Each role has specific responsibilities and contributes to the success of the project.</li><li><strong>Events</strong>: Scrum events, such as sprint planning, daily stand-ups, sprint review, and sprint retrospective, provide opportunities for collaboration, feedback, and continuous improvement.</li><li><strong>Artifacts</strong>: Scrum artifacts, including the product backlog, sprint backlog, and increment, help teams organize and prioritize work, track progress, and ensure transparency.</li></ol><h3><strong>Scrumban: The Hybrid Approach</strong></h3><p>Scrumban, as the name suggests, combines elements of both Scrum and Kanban methodologies. It offers flexibility and adaptability while incorporating Lean principles to optimize workflow efficiency. Key features of Scrumban include:</p><ol><li><strong>Continuous Flow</strong>: Unlike Scrum’s fixed-length sprints, Scrumban emphasizes a continuous flow of work. Teams pull tasks from the backlog as capacity allows, enabling a more flexible approach to prioritization and delivery.</li><li><strong>Work-in-Progress Limits</strong>: Scrumban introduces work-in-progress (WIP) limits to prevent overloading and optimize resource utilization. By setting WIP limits for each stage of the workflow, teams can maintain focus, reduce multitasking, and improve throughput.</li><li><strong>Cadence and Iteration</strong>: While Scrumban embraces the iterative nature of Agile development, it does not enforce fixed timeboxes like Scrum. Instead, teams can adopt their cadence for planning, review, and retrospective activities based on project needs.</li></ol><h3><strong>Choosing the Right Framework for Your Team</strong></h3><p>So, how do you decide between Scrum and Scrumban for your project ? Here are some factors to consider:</p><ol><li><strong>Team Size and Structure</strong>: Scrum is well-suited for larger teams with clearly defined roles, while Scrumban may be more suitable for smaller, cross-functional teams.</li><li><strong>Predictability vs. Flexibility</strong>: If your project requires a high level of predictability and structure, Scrum may be the better choice. However, if flexibility and responsiveness are more critical, Scrumban offers greater adaptability.</li><li><strong>Workflow Complexity</strong>: Scrumban is ideal for projects with fluctuating priorities and variable workloads, whereas Scrum is better suited for projects with well-defined requirements and stable workflows.</li></ol><h3>Conclusion</h3><p>As a product owner, my journey with Agile methodologies has been one of exploration, experimentation, and growth. Whether you embark on the Scrum path or venture into the realm of Scrumban, remember that the Agile journey is about continuous learning and adaptation. Embrace the principles of transparency, collaboration, and customer focus, and let them guide your team towards success.</p><h3>Thank you :)</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d24c69d497c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Story Points VS Hours]]></title>
            <link>https://medium.com/@karim.kb/story-points-vs-hours-13345d62f5a8?source=rss-635e88926584------2</link>
            <guid isPermaLink="false">https://medium.com/p/13345d62f5a8</guid>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[product-owner]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[scrum-master]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Karim B]]></dc:creator>
            <pubDate>Fri, 22 Mar 2024 11:00:48 GMT</pubDate>
            <atom:updated>2024-03-22T11:00:48.551Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4yT0BV9c_8bVCEpy_IsKwA.png" /></figure><h3>Introduction</h3><p>In the realm of SCRUM, product owners play a pivotal role in steering the development process towards successful outcomes. One of the critical decisions they often face is how to estimate and measure the effort required for tasks: through story points or hours. Each approach has its merits and drawbacks, and as a product owner, understanding these nuances is crucial for effective planning and decision-making.</p><h3>Understanding Story Points</h3><p>Story points are a unit of measure used in agile development to estimate the relative size and complexity of user stories or tasks. They provide a high-level view of effort without delving into specific timeframes. Story points are typically assigned based on factors such as complexity, uncertainty, and risk, allowing teams to prioritize and plan their work effectively.</p><h4>Advantages of Story Points</h4><ol><li><strong>Relative Estimations </strong>: Story points enable teams to compare the effort required for different tasks relative to one another, rather than focusing on absolute time estimates. This approach encourages collaboration and consensus-building among team members.</li><li><strong>Focus on Complexity </strong>: By considering various factors beyond just time, such as technical challenges or dependencies, story points provide a more holistic view of effort estimation.</li><li><strong>Adaptability</strong> : Story points allow for flexibility and adaptation as the project progresses. Teams can adjust estimates based on new information or changes in requirements without being constrained by fixed timeframes.</li></ol><h4>Challenges of Story Points</h4><ol><li><strong>Subjectivity</strong> : Estimating story points involves a degree of subjectivity, as different team members may interpret complexity differently. Achieving consensus can sometimes be challenging.</li><li><strong>Learning Curve</strong> : Adopting story points may require a learning curve for teams transitioning from traditional time-based estimation methods. It requires a shift in mindset towards relative sizing rather than absolute timeframes.</li><li><strong>Lack of Precision</strong> : Story points provide a broad estimate of effort, which may not always align with stakeholders’ expectations for precise timelines.</li></ol><h3>Understanding Hours</h3><p>Hours-based estimation involves quantifying the effort required for tasks in terms of actual time units, such as hours or days. This approach provides a more concrete and granular view of effort but requires detailed planning and tracking.</p><h4>Advantages of Hours</h4><ol><li><strong>Concrete Estimates</strong> : Hours provide precise estimates of time required for tasks, which can be useful for planning and scheduling purposes.</li><li><strong>Accountability</strong> : Tracking hours allows for more granular visibility into team productivity and progress, enabling product owners to monitor project timelines closely.</li><li><strong>Stakeholder Expectations</strong> : Hours-based estimates may align more closely with stakeholders’ expectations for specific delivery timelines, especially in industries with rigid deadlines.</li></ol><h4>Challenges of Hours</h4><ol><li><strong>Overemphasis on Time</strong> : Focusing solely on hours may lead to a narrow view of effort estimation, overlooking other important factors such as complexity or uncertainty.</li><li><strong>Micromanagement</strong> : Detailed tracking of hours can sometimes lead to micromanagement or a lack of trust within the team, hindering collaboration and autonomy.</li><li><strong>Inflexibility</strong> : Hours-based estimates may not easily accommodate changes or uncertainties that arise during the development process, leading to rigid planning and scheduling.</li></ol><h3>Conclusion</h3><p>In conclusion, while the product owner may choose story points as the primary method for estimating effort due to their emphasis on collaboration and adaptability, it’s essential to recognize that different stakeholders may have varying preferences. The product owner’s ability to adapt to executive management’s expectations by incorporating hours-based estimates demonstrates flexibility and alignment with organizational needs. By leveraging story points for internal team planning and communication and transitioning to hours when interfacing with executives, product owners can effectively balance agility with the need for precise timelines, fostering transparency and trust across all levels of the organization.</p><h3>Thank you :)</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=13345d62f5a8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case study: Welness App]]></title>
            <link>https://medium.com/design-bootcamp/case-study-welness-app-a5fc00e4b9c7?source=rss-635e88926584------2</link>
            <guid isPermaLink="false">https://medium.com/p/a5fc00e4b9c7</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[wellness]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[case-study]]></category>
            <dc:creator><![CDATA[Karim B]]></dc:creator>
            <pubDate>Sun, 22 Jan 2023 19:33:49 GMT</pubDate>
            <atom:updated>2023-01-23T08:42:11.601Z</atom:updated>
            <content:encoded><![CDATA[<h3>Case study: Wellness App</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/828/1*7FhqN7NBtdupe6l2WqYveA.png" /><figcaption>Stressless</figcaption></figure><h3>Challenge</h3><p>The Daily Health Conference (a non-profit organization dedicated to promoting health and wellness) is very excited to explore how technology can be used to help people live healthier lives.</p><p>While brainstorming what the new mobile apps should do, the board realized that the opportunities for translating the concept of wellness into a digital product are virtually infinite. Their members could use their apps to keep track of diet plans, fitness programs, mental wellness, stress levels, water intake and so on. The posibilities are endless and they are not exactly sure where to begin!</p><p>As a result, they’ve organized a competition for the upcoming conference. <strong>Designers will conduct user research to understand people’s relationships with mental, physical, and emotional well-being. Designers will then create a prototype for a tool that will motivate them to take action. Finally, designers will pitch their ideas in front of a jury composed of wellness professionals, designers, and investors. </strong>The winning concepts will be presented at the conference and developed into the Daily Health Conference’s first set of digital apps</p><p>For this challenge, I teamed up with my friend Vincent.</p><h3>Empathize</h3><p>To gain a better understanding of this particular topic, we used the <strong>secondary research</strong> method. So, we used existing sources in order to help arrive at the goal of our research.</p><p>From these research, our insights were:</p><ol><li><strong>9 out of 10 people</strong> feel stressed in general ;</li><li><strong>Work</strong> is the first cause of stress mentioned;</li><li><strong>Prevention</strong> is the #1 action to reduce stress.</li></ol><p><em>Sources: OMS 2022 / Opinionway 2017 / US department of health and human services 2022</em></p><p>To go further in understanding the topic, we decided to <strong>interview</strong> 5 users and do a <strong>survey</strong> with a series of questions that generates data points about user attitudes.<br>Our target for users interviews: 5 young workers, mix of ethnicities, gender and socio-economic levels.</p><p>Users interviews and survey allow us to confirm our research, our insights were:</p><ol><li><strong>Everyone </strong>experiences stress at<strong> work</strong>;</li><li>Available mostly <strong>mornings</strong> and <strong>evenings</strong> to reduce stress;</li><li>Need to <strong>be accompanied</strong>;</li><li><strong>Knows </strong>and <strong>tried </strong>some wellness apps.</li></ol><p>Then, we used the method of <strong>Empathy Map </strong>to synthesize rational and sentimental aspects of our users through their situation, acts, feelings and emotions. Empathy Maps shed light on which problems to solve, and how.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gXhMK-d5BVHcBQyBCl3fwg.png" /><figcaption>Empathy Map</figcaption></figure><h3>Define</h3><p>These led us to build our User Persona: <em>Julien, </em>an<em> </em>urban worker who is moderately stressed, work stress affects his health and spirit . When he’s not at work, he’s available mostly mornings and evenings 2 to 4 times a week. He knows and tried some wellness apps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/821/1*7VhPOOs2cJnL_qzwXAfP6A.png" /><figcaption>Persona</figcaption></figure><p>Julien’s motivation ? Better manage and reduce his stress. His goal ? Be healthy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/891/1*w20gijW7BsUoZw007oBsIQ.png" /><figcaption>User Journey Map</figcaption></figure><p>Here is the typical Julien’s journey</p><p>We can see some spots where Julien’s visit becomes unpleasant: his experience is impacted. he will surely not want to repeat it.</p><p>To tackle this problem, we decided to focus on the point where we had the most negative feedbacks from our users.</p><p>Then, we developed a Problem Statement to identify the gap between what our product has and what our users need:</p><p><em>‘’</em>How can we <strong>help </strong>and <strong>encourage young urban workers</strong> to better <strong>manage and reduce their stress</strong> because it impacts their <strong>health</strong>, <strong>motivation </strong>and <strong>relationship </strong>to others<em>.’’</em></p><p>Problem Statement, as well as User Persona are important because they define the project’s main objective.</p><p>These are created based on the pain points and opportunities we uncovered during the research phase.</p><h3>Ideate</h3><p>After we defined the problem and clarified our user persona, we employed a series of tools and exercises in order to generate potential solutions to help the client and users accomplish their goals.</p><p>The tool we used were:</p><ul><li><strong>Crazy 8&#39;s:</strong> a fast sketching exercise that challenges people to sketch eight distinct ideas in eight minutes.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/845/1*XIKqSpsVKawr7Fm-19Hwrg.png" /><figcaption>Crazy 8&#39;s</figcaption></figure><h3>Visual Competitive Analysis</h3><p>The next step in creating our brand is understanding the competitive space our product will be in and how to position myself in it.</p><ul><li>What other products are in our space?</li><li>What other products do people use our app use?</li><li>What do their sites or apps look like?</li></ul><p>When looking at our competition, we want to identify the current identities that are being used within the market, so that:</p><ul><li>We are aware of current trends in this space</li><li>We set our product apart from the competition</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/926/1*x_8ppoPqiJuHj1H2cEMYnA.png" /><figcaption>Visual Competitive Analysis</figcaption></figure><h3>Solution</h3><p>We are excited to share with you our solution, <strong>Stressless, </strong>an innovative app<strong> </strong>designed to track and <strong>manage stress</strong> levels through innovative techniques, symptom tracking and short, interactive exercises.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/913/1*YvfcElZcoqWBcKadHmKyJw.png" /><figcaption>Stressless</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/966/1*p-kmZk-7Om7KymOBUphysQ.png" /><figcaption>Brand values</figcaption></figure><h3>From Concept to Prototype</h3><p><strong>1 - Low-fidelity</strong> (lo-fi) prototyping is a quick and easy way to translate high-level design concepts into tangible and testable artifacts. The first and most important role of lo-fi prototypes is to check and test functionality rather than the visual appearance of the product.</p><p><strong>2 - Mid-Fidelity</strong> (mid-fi) prototyping is a great option to refine the execution of solutions and give an opportunity to change direction and testing out options. We used mid-fi prototype to give our target users a great sense of what the solution will look like.</p><p><strong>3 - High-Fidelity</strong> (hi-fi) prototyping is a computer-based interactive depiction of the product. It is the most accurate to the final design in terms of details and functionality. The main purpose of interactive prototypes is their use in the usability testing of the product have target users validate it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/942/1*6G2Ez2z16EV136mTitmIEg.png" /><figcaption>Concept to Prototype</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YyopvH4KZYLqL2de6NFzWA.png" /><figcaption>MVP Prototype</figcaption></figure><h3>Learning outcomes</h3><ul><li>Use design thinking and iterative methods to best anticipate user needs</li><li>Implement a user research strategy using quantitative methods to gather information</li><li>Prioritize the functionalities of a product to create a MVP</li><li>Follow best practices for accessibility to create the product’s interface</li><li>Conduct desirability tests to determine how the user perceives the graphical choices</li><li>Realise several prototypes of a product in order to choose the final version of the application</li><li>Visually represent the user’s data in order to create a unique and customised experience</li></ul><h3>Conclusion</h3><p>I am really happy to rethink how people can adopt and commit to a health-improving routine with the mobile app solution <strong>Stressless.</strong></p><h3>Thank you :)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/225/1*rZWrRSoJxqBjjlGNzVttkQ.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a5fc00e4b9c7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/case-study-welness-app-a5fc00e4b9c7">Case study: Welness App</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case study: Redesigning the LinkedIn mobile app]]></title>
            <link>https://medium.com/design-bootcamp/case-study-redesigning-the-linkedin-mobile-app-a57e6f3906b?source=rss-635e88926584------2</link>
            <guid isPermaLink="false">https://medium.com/p/a57e6f3906b</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[linkedin]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Karim B]]></dc:creator>
            <pubDate>Fri, 13 Jan 2023 21:06:33 GMT</pubDate>
            <atom:updated>2023-01-14T04:13:33.277Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/225/1*VPXFxjnMQUttPYOvtLKJvA.png" /><figcaption>Linkedin logo</figcaption></figure><h3>Challenge</h3><p>The purpose of this challenge is to select a <strong>well-known native mobile app</strong> and redesign a minimum of three screens<strong>.</strong></p><p>So, I have chosen a very popular mobile app, the app ‘<strong>LinkedIn</strong>’. It’s a business and employment-focused social media platform that works through websites and <strong>mobile apps</strong>. The platform is primarily used for professional networking and career development, and allows job seekers to post their CVs and employers to post jobs. <strong>LinkedIn</strong> allows members to create profiles and connect with each other in an online social network which may represent real-world professional relationships.</p><h3>Replicate</h3><p>As part of the visual redesign, I had to do two things: first, I reproduced the existing screens because each redesign, no matter how small or big, always begins with an audit of the existing design. Second, I redesigned the app’s look and feel.</p><p>In fact, the task I had to do is screenshots some existing screens and design them on Figma as identical. In order to have a good playground that I’ll be able to redesign, I chose the <strong>candidate’s LinkedIn profile.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V1Q8yCvfqLf-inrQWSFegQ.png" /><figcaption>Copy</figcaption></figure><h3>Heuristic analysis</h3><ol><li><strong><em>Information overload &gt;</em></strong><em> </em>Keep It Simple<em>.</em></li><li><strong><em>Too much white &gt; </em></strong>New branding colors.</li><li><strong><em>Branding elements &gt; G</em></strong>etting consumer attention with new branding elements.</li><li><strong><em>No avalaibility information &gt; </em></strong>New feature.</li><li><strong><em>Skills visibility &gt; </em></strong>New feature.</li><li><strong><em>Endorsement visibility &gt; </em></strong>New feature.</li></ol><h3>Visual Competitive Analysis</h3><p>The next step in creating my brand is understanding the competitive space my product will be in and how to position myself in it.</p><ul><li>What other products are in my space?</li><li>What other products do people use my app use?</li><li>What do their sites or apps look like?</li></ul><p>When looking at my competition, I want to identify the current identities that are being used within the market, so that:</p><ul><li>I am aware of current trends in this space</li><li>I set my product apart from the competition</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BekwUPjM2P5bQSu5GZZvHg.png" /><figcaption>Visual Competitive Analysis</figcaption></figure><h3>Moodboard</h3><p>A moodboard is an arrangement of images, materials, and pieces of text intended to evoke or project a particular style or concept.</p><p>Moodboard is a great way to convey my design idea, win pitches, and get an early sign-off. What I am thinking and feeling about a creative idea is limited to how good my verbal communication skills are at expressing this to project stakeholders. A moodboard can help get everyone on the same page and start a conversation that aligns everyone’s vision.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/986/1*pU8b58-d6p3TOEEC4UO-bA.png" /><figcaption>My moodboard</figcaption></figure><h3>Style Guide</h3><p><strong>Moodboards</strong> will inspire the design direction. <strong>Style tiles</strong> will translate the mood, feel, and tone of our website or app based on what we learned from the needs of our client and user. But as an internal tool for our design, marketing, content, and development teams, we need a more robust document with specific guidelines.</p><p>The way that companies and products achieve <strong>consistency</strong> is through <strong>Style Guides</strong>.</p><p>A <strong>Style Guide</strong> is a set of standards that communicate design instructions to a team or organization. Style Guides align designs with a company’s voice and mission.</p><p>They compile a mature set of guidelines and visual references for a whole digital product that includes. Not only fonts, colors, style, and other UI elements but also much more info that companies may need to carry out a consistent brand strategy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AytLTEL1Q3FSZnw0yIAP-A.png" /><figcaption>My style guide</figcaption></figure><h3>Redesign</h3><p>Finally, I’m excited to share with you my LinkedIn mobile app UI redesign.</p><p>I decided to use black and yellow branding colors traditionally seen as a symbol of professionalism, seriousness, joy and friendliness.</p><p>I decided to design new app features that add value :</p><p>· Business Card<br>· Rating stars for skills<br>· Like button for endorsement<br>· Total years of experience<br>· Availability</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*puXpjZv9kZd3KZJ-AkUfKw.png" /><figcaption>My redesign</figcaption></figure><p><a href="https://www.linkedin.com/posts/karim-belabed_ui-ux-design-activity-7018996378227900416-sEoA?utm_source=share&amp;utm_medium=member_desktop">Karim BELABED on LinkedIn: #ui #ux #design #linkedin #redesign #branding</a></p><h3>Learning outcomes</h3><ul><li>Deconstruct the user interface design of an existing product</li><li>Use usability heuristics and visual patterns to improve the product’s usability</li><li>Perform a visual competitive analysis to deepen your visual creativity</li><li>Document the brand identity, the visual components and the design principles of the product</li><li>Recreate a product’s user interface design to match the brand’s identity</li></ul><h3>Conclusion</h3><p>I really liked this challenge, I have spent a lot of time redesigning but it was fun and exciting !</p><p>So, it was my first redesign and I am really happy about the result :)</p><h3>Thank you :)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/232/1*LjIJXus4ZjB-XiHXuwetXg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a57e6f3906b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/case-study-redesigning-the-linkedin-mobile-app-a57e6f3906b">Case study: Redesigning the LinkedIn mobile app</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case study: Local e-commerce website]]></title>
            <link>https://medium.com/design-bootcamp/case-study-local-e-commerce-website-e7eb70df4a5f?source=rss-635e88926584------2</link>
            <guid isPermaLink="false">https://medium.com/p/e7eb70df4a5f</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[bootcamp]]></category>
            <category><![CDATA[ironhack]]></category>
            <dc:creator><![CDATA[Karim B]]></dc:creator>
            <pubDate>Thu, 29 Dec 2022 11:27:40 GMT</pubDate>
            <atom:updated>2022-12-30T06:01:32.124Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/930/1*ejIMDl9VnZZNxWo1blP83A.jpeg" /></figure><h3>Challenge</h3><p>The purpose of this challenge is to help local shops improve their online presence to be more competitive in the market.</p><p>Transitioning online will help local businesses and professionals improve their online presence and to be more competitive in the actual market. For this challenge, I teamed up 2 amazing people : Anthony and Pauline.</p><p>We selected a local business called <a href="https://l-endroit-par-fee.myshopify.com/"><strong>l’endroit-par-fée</strong></a>, it’s an online retailer of pet food based in a small town in France.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/438/1*9f0AN5vBMvA7DfzkTeT0Bg.png" /><figcaption>website</figcaption></figure><h3>Empathize</h3><p>The first step of the project was to <strong>interview </strong>Aurelie, founder and owner of l’endroit-par-fée. Talking with her made us understand her story, her goals for the future and the points she wants to improve.</p><p>From this interview, stakeholder goals were:</p><ol><li>Make the website <strong>fun</strong> and <strong>easy </strong>to use;</li><li><strong>Increase </strong>the number of <strong>customers</strong>;</li><li><strong>Increase sales</strong>.</li></ol><p>To gain a better understanding of this particular topic, we used the <strong>secondary research</strong> method. So, we used existing sources in order to help arrive at the goal of our research.</p><p>From these research, our insights were:</p><ol><li><strong>50%</strong> of French households owned a pet as of 2022;</li><li>Pet owners prefer <strong>healthy food</strong>;</li><li><strong>Kibbles</strong> remain the main food for cats and dogs.</li></ol><p>Sources: <a href="https://www.facco.fr/chiffres-cles/les-chiffres-de-la-population-animale/">Facco</a></p><p>To go further in understanding the problem, we decided to <strong>interview </strong>5 users.<br>Our target: 5 people, who own cats and dogs and who consider healthy food to be a major part of their lives, mix of ethnicities, gender and socio-economic levels.</p><p>Users interviews allow us to confirm our research, our insights were:</p><ol><li><strong>Safe/trusted</strong> website;</li><li><strong>Organic/healthy</strong> food;</li><li>Customer <strong>reviews</strong>.</li></ol><h3>Define</h3><p>These led us to build our <strong>User</strong> <strong>Persona</strong>: <em>Alix, </em>who loves living in the countryside because there’s more space to be free. When she’s not at work, she likes spending time with her cat and her dog. She wants only healthy and organic foods for her pets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RxdrS8eakaWehATxxYwCgA.png" /><figcaption>Persona</figcaption></figure><p>Alix’s motivation ? Take care of her pets. Her goal ? Healthy food.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*88SElZsOvY6NiyJID3m2uA.png" /><figcaption>User Journey Map</figcaption></figure><p>Here is the typical Alix’s journey</p><p>We can see some spots where Alix’s visit becomes unpleasant: her experience is impacted. She will surely not want to repeat it.</p><p>To tackle this problem, we decided to focus on the point where we had the most negative feedbacks from our users.</p><p>Then, we developed a <strong>Problem Statement</strong> to identify the gap between what our product has and what our users need:</p><p><strong><em>‘’Pet owners concerned about the well-being of their pets need healthy and organic foods because the products on the market are not always adapted to the digestive system of their animals and some ingredients can be harmful.’’</em></strong></p><p>Problem Statement, as well as User Persona are important because they define the project’s main objective.</p><p>These are created based on the pain points and opportunities we uncovered during the research phase.</p><h3>Ideate</h3><p>After we defined the problem and clarified our user persona, we employed a series of tools and exercises in order to generate potential solutions to help the client and users accomplish their goals.</p><p>The tools we used were:</p><ul><li>Round Robin: a team-sketching exercise</li><li>Bad/Good Ideas : use bad ideas to come up with fresh good ideas</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/535/1*-3roCuycW_Sa5khrLNgcyA.png" /><figcaption>Concept sketches</figcaption></figure><p>Concept sketches are a great way to quickly test your ideas and get feedback before you spend too much time developing them.</p><h3>Prototype</h3><p>Low-fidelity (lo-fi) prototyping is a quick and easy way to translate high-level design concepts into tangible and testable artifacts. The first and most important role of lo-fi prototypes is to check and test functionality rather than the visual appearance of the product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zTROpIqIB8bnINMH2xXS6A.png" /><figcaption>Prototype</figcaption></figure><p><a href="https://www.figma.com/proto/l6no5TD4ZNC3B3YxUdqftv/ecommerce_midfi-(Copy)?node-id=1%3A3&amp;scaling=scale-down&amp;page-id=0%3A1&amp;starting-point-node-id=1%3A3">Click here to see the prototype</a></p><h3>Test</h3><p>To test our concept, we found 4 potential users of our solution based on our persona.</p><p>Testing the prototype gave some insightful feedback to the prototype.</p><p>Indeed, at the early stage of the design process, the main goal of testing is to validate ideas and product goals.</p><p>Early validation of our ideas is crucial because it can help minimize costs. The later you make changes in the production line, the more expensive and difficult it becomes to implement these changes.</p><p>Here is what come up from our testing :</p><ul><li>Pain points : misunderstanding about some products</li><li>Wish list : make buttons more visible, more categories</li><li>Positive : fun and easy to use, customer reviews</li></ul><h3>Next step</h3><p>The next step would be actually :</p><ul><li>Add wish list points</li><li>Create a hi-fi prototype</li><li>User testing</li><li>Website development</li></ul><h3>Learning outcomes</h3><ul><li>Perform a competitive analysis on a specific industry in order to propose a market-driven solution</li><li>Gain clarity by identifying and speaking with the project’s various stakeholders</li><li>Define the information architecture of the content to match the users’ mental models</li><li>Organize the content visually in wireframes to create a consistent layout</li><li>Perform user testing to validate the usability of the solution</li><li>Explore interface aesthetics by presenting different visual elements that correspond to the company’s brand identity</li><li>Create a mobile and a desktop version of the solution to demonstrate its responsiveness</li></ul><h3>Conclusion</h3><p>For a local shop, an online presence is just as important as the physical location. An e-commerce website is often the best way to promote the shop, as search engines do support local businesses. It is also a great way to increase sales and revenue by offering services such as delivery or click-and-collect.</p><p>So, I am really happy to help local shop like <strong>l’endroit-par-fée</strong>.</p><h3>Thank you :)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*oE-bLoS3ngTfrK4W4uKuQg.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e7eb70df4a5f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/case-study-local-e-commerce-website-e7eb70df4a5f">Case study: Local e-commerce website</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case study: Design thinking challenge]]></title>
            <link>https://medium.com/design-bootcamp/case-study-design-thinking-challenge-4ca83f0240aa?source=rss-635e88926584------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ca83f0240aa</guid>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[bootcamp]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Karim B]]></dc:creator>
            <pubDate>Sun, 11 Dec 2022 10:30:15 GMT</pubDate>
            <atom:updated>2022-12-12T07:15:23.902Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/728/1*mxJ2J8MbveaT5ewJDq6ZLQ.jpeg" /></figure><h3>Challenge</h3><p>The purpose of this challenge is to make heritage accessible to everyone.</p><p>In fact, since the 1970s, museums and other public institutions have been suffering a profound crisis.</p><p>As a UX/UI designer, we have to find an innovative solution to help museums and other public institutions fulfilling their mission of preserving cultural heritage while making it more accessible to a wider audience</p><h3>Empathize</h3><p>To gain a better understanding of this particular topic, we used the <strong>secondary research</strong> method. So, we used existing sources in order to help arrive at the goal of our research.</p><p>From these research, our insights were:</p><ol><li><strong>Free admission for 18–25</strong> is effective in motivating people to go to museums;</li><li><strong>People living in large cities</strong> go to museums more than others;</li><li>In 40 years, attendance <strong>has changed little.</strong></li></ol><p>To go further in understanding the problem, we decided to interview 5 users.<br>Our target: <strong>3 people</strong>, who consider culture to be a major part of their lives who have been to a museum recently and <strong>2 people</strong> who haven’t been to a museum in the last 12 months, mix of ethnicities, gender and socio-economic levels.</p><p>Users interviews allow us to confirm our research, our insights were:</p><ol><li><strong>High prices</strong> to access these cultural spaces;</li><li><strong>Not attractive </strong>and<strong> not funny</strong>;</li><li><strong>Need to be accompanied.</strong></li></ol><h3>Define</h3><p>As we start to organize our Users Research into our <strong>Affinity Diagram</strong>, 6 popular topics emerge and we were able to have more clarity on where was the majority of the negative points.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/961/1*XY2kmHEAUXQAN4HV51i34g.png" /><figcaption>Affinity Diagram</figcaption></figure><p>These led us to build our <strong>User Persona</strong>: <em>Elodie, </em>who loves living in Paris because there’s always something going on. When she’s not at work, she likes spending time with her friends and family. Actually, museums are not top of mind for her, but she won’t say « no » if a friend invites her.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XJeotOYebmT7AOVnDYvNjg.png" /></figure><p>Elodie’s motivation ? Spend time with friends. Her goal ? Entertaining herself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ormbKHUj01Cd6khy1o8Ysg.png" /><figcaption>User Journey</figcaption></figure><p>Here is the typical Elodie’s museum journey</p><p>We can see some spots where Elodie’s visit becomes unpleasant: her experience is impacted. She will surely not want to repeat it.</p><p>To tackle this problem, we decided to focus on the point where we had the most negative feedbacks from our users.</p><p>Then, we developed a <strong>Problem Statement</strong> to identify the gap between what our product has and what our users need.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/538/1*-kZMgJiif_n9pFmRGue_Uw.png" /><figcaption>Problem statement</figcaption></figure><p><strong>Problem Statement</strong>, as well as <strong>User Persona</strong> are important because they define the project’s main objective.</p><p>These are created based on the pain points and opportunities we uncovered during the research phase.</p><h3>Ideate</h3><p>After we defined the problem and clarified our user persona, we employed a series of tools and exercises in order to generate potential solutions to help the client and users accomplish their goals.</p><p>The tools we used were:</p><ul><li><strong>Round Robin</strong>: a team-sketching exercise</li><li><strong>Bad/Good Ideas</strong> : use bad ideas to come up with fresh good ideas</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/647/1*zhWbbz9AZt3kBRIvjeNFVg.png" /><figcaption>Concept sketches</figcaption></figure><p>Concept sketches are a great way to quickly test your ideas and get feedback before you spend too much time developing them.</p><p>When we start to group similar ideas together, 2 clear topic emerge :</p><ul><li>An audioguide with famous voices from the <strong>pop culture</strong></li><li>An <strong>interactive</strong> museum game</li></ul><p>Then we combined these into one solution : an app to personalize the museum visit by choosing a famous voice guide and playing interactive games.</p><h3>Prototype</h3><p>Low-fidelity (lo-fi) prototyping is a quick and easy way to translate high-level design concepts into tangible and testable artifacts. The first and most important role of lo-fi prototypes is to check and test functionality rather than the visual appearance of the product.</p><p><a href="https://www.figma.com/proto/RzlGEsvNOBWLyqFYJ6sSgQ/Prototype-Museum?node-id=102%3A1709&amp;scaling=min-zoom&amp;page-id=0%3A1&amp;starting-point-node-id=102%3A1709">Click here to see the prototype</a></p><h3>Test</h3><p>To test our concept, we found 5 potential users of our solution based on our persona.</p><p>Testing the prototype gave some insightful feedback to the prototype.</p><p>Indeed, at the early stage of the design process, the main goal of testing is to validate ideas and product goals.</p><p>Early validation of our ideas is crucial because it can help<strong> </strong>minimize costs. The later you make changes in the production line, the more expensive and difficult it becomes to implement these changes.</p><p>Here is what come up from our testing :</p><ul><li><strong>Pain points</strong> : sharing personal data</li><li><strong>Wish list</strong> : ability to save a work of art, customized itinerary</li><li><strong>Positive</strong> : funny, interactive, discount voucher</li></ul><h3>Next step</h3><p>The next step would be actually to add some features :</p><ul><li>Add wish list points</li><li>Be able to use the app with other users</li><li>Create Live Events</li><li>Share last visit on social networks</li></ul><h3>Learning outcomes</h3><ul><li>Implement a user research strategy using qualitative methods to gather information</li><li>Drive insights from user research using a tool to synthesise findings</li><li>Define the user persona utilising user research</li><li>Identify the problem to be solved and the way to answer it</li><li>Generate alternative and innovative ideas for the desired solution</li><li>Define all the steps of the process to reach the desired solution</li><li>Develop an innovative solution to solve the problem</li></ul><h3>Conclusion</h3><p>By combining collaboration and iteration, that are at the heart of <strong>Design Thinking</strong>, we can tackle wicked problems. We are able to come up to innovative solution that we improve with each new iteration.</p><h3>Thank you :)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*3LUzRoih36Qxm_tOb-9ltg.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ca83f0240aa" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/case-study-design-thinking-challenge-4ca83f0240aa">Case study: Design thinking challenge</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case study: Wireframing challenge]]></title>
            <link>https://medium.com/design-bootcamp/ironhacks-prework-wireframing-challenge-f507f5a686b4?source=rss-635e88926584------2</link>
            <guid isPermaLink="false">https://medium.com/p/f507f5a686b4</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ironhack-prework]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[case-study]]></category>
            <dc:creator><![CDATA[Karim B]]></dc:creator>
            <pubDate>Wed, 09 Nov 2022 20:54:05 GMT</pubDate>
            <atom:updated>2022-11-11T08:22:57.511Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vGgg6Ppypj41qMGU4_YDnA.jpeg" /></figure><h3>Challenge</h3><p>For the Ironhack’s Prework: Challenge 2, I have to ‘reverse engineer’ one popular app Interaction Design and User Flow.</p><p>Using Figma, my task is to create a wireframe version of the User Flow of the chosen app based on screenshots. So, I have chosen a very popular streaming services in France, the app ‘<strong>MyCANAL</strong>’. It’s a mobile application on which you can watch the excellent programs of CANAL+ anytime, anywhere, you can stream content like Game of Thrones, Gomorra, MotoGP and Formula1.</p><h3>User Flow</h3><p>My user flow for this challenge is launching the episode 1 of the first season of Gomorra, it’s a very good italian crime drama television series that I want to see again, which is currently available on MyCANAL. I chose this app and this flow because I am using MyCANAL on a daily basis and I am very familiar with, it’s really easy to use it, it’s French and I find the UX/UI design very good.</p><h3>Screenshots of the user flow</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zYZl31MvE1Jz1m_l-aBaAQ.png" /><figcaption>Flow to launch the episode 1 of Gomorra</figcaption></figure><h3>Inventory of the UI Elements</h3><p>The UI elements used are the following :</p><ul><li>Iphone status bar + home indicator</li><li>Topbar (buttons, text, dropdown menu)</li><li>Bottom nav bar</li><li>Images</li><li>Text (different sizes of titles and texts)</li><li>Buttons</li><li>Cards</li><li>Search bar (empty + filled with text)</li><li>Iphone native keyboard</li><li>Video</li><li>Progress bar</li></ul><h3>Lo-fi wireframe screenshot</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DdY5vHgWfj9lhK543cowcg.jpeg" /><figcaption>Lo-fi wireframe of the user flow</figcaption></figure><p>Please find the following steps below:<br>→ Click on search in the bottom nav bar<br>→ Type “Gomorra” with the keyboard<br>→ Click on the “Gomorra” first card in the result<br>→ Click on play in the “Play” button<br>→ Watch the first episode of Gomorra</p><h3>Figma wireframe screenshot</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y5CYJ92_6RGvuMH8rXtGjg.png" /><figcaption>Figma wireframe of the user flow</figcaption></figure><h3>Conclusion</h3><p>I really liked this challenge, I have spent a lot of time wireframing but it was fun and exciting !</p><p>So, it was my first wireframe and I am really happy about the result :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f507f5a686b4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/ironhacks-prework-wireframing-challenge-f507f5a686b4">Case study: Wireframing challenge</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ironhack’s Prework: Design Thinking Challenge]]></title>
            <link>https://medium.com/@karim.kb/ironhacks-prework-design-thinking-challenge-2a54c7432cfc?source=rss-635e88926584------2</link>
            <guid isPermaLink="false">https://medium.com/p/2a54c7432cfc</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ironhack-prework]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ironhack]]></category>
            <dc:creator><![CDATA[Karim B]]></dc:creator>
            <pubDate>Thu, 03 Nov 2022 13:47:11 GMT</pubDate>
            <atom:updated>2022-11-03T13:47:11.022Z</atom:updated>
            <content:encoded><![CDATA[<h3>Company Background</h3><p>UrbanGo is a public transit and mapping start-up in Silicon Valley, CA. The firm handles urban mobility challenges by identifying the quickest and shorted transport route in the designated region, enabling users to choose between the available private and public transport options. This approach reduces the identification of mobility services while providing optimal services to consumers. The company has released robust mobile and web-based applications that adequately meet these requirements.</p><p>However, the applications do not allow users to purchase tickets from the available transportation services. As a result, the company intends to develop a feature that aggregates the service selection and ticket purchasing, providing a one-stop solution for the transportation challenges in urban areas.</p><h3><strong>Problem Encountered in User Interviews</strong></h3><p>The interview was selected as the primary requirements elicitation method due to its ability to extensively address design issues. This method involved asking five participants questions regarding the ticketing service needed for the system. There were three problems identified during the interview sessions. First, the participants provided conflicting information regarding the system requirements. These inconsistencies required streamlining the user needs to provide a robust app feature for the ticketing service. Secondly, two interviewees answered the questions from other users’ perspectives. This approach prevented them from providing their view regarding the component. Lastly, one participant had challenges recalling their interaction with ticketing services for transport services. This situation hindered the interviewee’s ability to respond to the design questions effectively.</p><h3><strong>Problem Being Solved</strong></h3><p>The primary design problem is developing an integrated ticketing service for the UrbanGo application that enables users to pay for the app’s public and private transportation services. UrbanGo application allows users to choose a cost-effective private or public transportation service based on its estimated arrival time, departure, and price. However, the app does not enable users to pay for the services, increasing the complexity of commuting. This situation is aggravated when the travellers need to connect two or more services, leading to unnecessary delays and hurdles. The one-stop ticketing service seeks to resolve these challenges by enabling users to select their preferred transportation service and pay for different services to ease commuting. Thus, the absence of aggregated payment solutions in transportation compromised smooth commuting among travellers.</p><h3><strong>Solution Plan</strong></h3><p>The design problem was resolved through the system development methodology. This approach provides a robust app deployment strategy that effectively identifies user requirements and addresses business needs. The first phase is requirements elicitation, where user interviews are conducted. The second phase was the system analysis, where the user requirements and business needs were verified and validated. This validation provided the design concepts for the solution. The third step is prototyping, where prototyping techniques are used to design the service. The design functionalities developed during this stage were coded in the subsequent phase. The fourth stage is system coding, where the service is developed. This development involves integrating the payment gateway for the credit and debit cards and aggregating payment services for the solution. The last phase is testing and deployment, where the service is checked, improved and released to the consumers.</p><h3><strong>Paper Prototype Design</strong></h3><p>The paper prototype for the integrated payment service is shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6y1-PY3c7kqDtJyaJa4psg.jpeg" /></figure><h3><strong>Things Learned in the Process</strong></h3><p>The design process offered valuable insights into developing enterprise systems. For instance, the interviews provided hands-on exposure to requirements elicitation, a critical part of the system design process. Since the participants provided conflicting requirements, it was crucial to streamline them to offer a robust design concept. Additionally, the prototyping phase provided critical design information that enhanced the development of the service components. For example, it enabled the development of different service features and validation to ensure their relevance in the solution. Thus, the process provided a suitable environment for learning system development.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2a54c7432cfc" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>