<?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 Ajla Fijuljanin on Medium]]></title>
        <description><![CDATA[Stories by Ajla Fijuljanin on Medium]]></description>
        <link>https://medium.com/@ajlafi?source=rss-faffa94143e1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*5-WTyldsD-9JM1rv</url>
            <title>Stories by Ajla Fijuljanin on Medium</title>
            <link>https://medium.com/@ajlafi?source=rss-faffa94143e1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 03:32:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ajlafi/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[Why Discovery Phase Is The Most Important Phase In Software Development Cycle]]></title>
            <link>https://medium.com/maestral-solutions/discovering-your-scope-41100f95fd65?source=rss-faffa94143e1------2</link>
            <guid isPermaLink="false">https://medium.com/p/41100f95fd65</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[product-lifecycle]]></category>
            <category><![CDATA[discovery]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[Ajla Fijuljanin]]></dc:creator>
            <pubDate>Wed, 19 Dec 2018 15:07:08 GMT</pubDate>
            <atom:updated>2019-01-29T13:06:13.355Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yN6lv1up75k50pUGzhVvYA.jpeg" /><figcaption>Source: AnyForSoft</figcaption></figure><h3>Here’s the truth about software development industry: <strong>technology alone is not enough and it never will be</strong>.</h3><p>Yes, writing clear and readable programs is important, but designing, writing, testing, and sustaining programs with the aim of meeting the market needs and solving user problems is crucial.</p><p>Software engineering is not so much about how to write the solution but rather about<strong> identifying the solution</strong> itself.</p><p>We believe that, in an age of intellectual fragmentation, identifying solutions is best done when people from different fields come together and invest in customer-centric development. The aim is to understand the problem in depth, envisage the optimal solution, predict its limitations, and take the privacy and security aspects gravely.</p><h4><strong>It all begins with the Discovery phase.</strong></h4><p>This is one of the most underrated, but remarkably important phases of software development. It’s really easy to skip or not pay enough attention to this step. This probably happens because:<br><strong>1.</strong> You’re too excited about the project, so you rush to development<br><strong>2.</strong> Your previous experience boosted your confidence to a point that it makes you believe Discovery is unnecessary in your case<br><strong>3.</strong> You simply don’t see how it fits with agile methodology your company proudly practices.</p><p><strong>But here is the real truth:</strong> Discovery phase is a process that brings coherence and clarity to the project that cannot subsist otherwise. It provides value far beyond the associated costs. Information that comes from the Discovery phase actually promotes agility and helps you make wiser decisions along the way.</p><h4>After working 10+ years in the industry, and with Fortune 500 clients, we can confidently say that collaborative efforts of the Discovery team and the Client result in nothing less than <strong>superior solutions, lower risks and costs of change, and maximized potential of the overall project.</strong></h4><h4>How to start with the discovery phase?</h4><p>At Maestral, it all starts with our cross-functional team auditing the existing solutions and performing in-depth research into Client’s goals. We account for business strategy, budget and timeline to ensure our proposed solution is the best way to maximize business potential.</p><p>The process is based on collaborative efforts where we collect and systemize information and existing documentation. We <strong>apply structure to the innovation process</strong> and involve all stakeholders in the definition of the problem and the development of solutions.</p><p>Immersing in Client’s business strategy and customer experience to make critical success assumptions is crucial at this phase.</p><p>Our goal is giving the specific project the best chance of succeeding by providing an accurate budget and timeline estimate, as well as a clarity of vision over the long-term work.</p><h4><strong>Techniques / Asking The Right Questions</strong></h4><p><strong>Do we know what we need to know?</strong> To bridge the gap between planning and execution, we seek to understand general project vision and specific goals prior to collecting, reviewing, systematizing, and analyzing existing and incoming information.</p><p><strong>Are we asking the right questions the right people?</strong> We are aware that faulty assumptions too often enervate effective consulting, and we attempt to identify existing problems as perceived by different stakeholders, from product owners to end users.</p><p><strong>Is data managed properly?</strong> We claim that Discovery phase is not about data quantity but about management quality. The key test for this process is whether available, often limited data can effectively determine the core driver of a problem.</p><p><strong>Which solution is the right solution?</strong> Too often competing ideas and conflicting information make it difficult to determine the right approach. It is of ultimate importance for us to identify a sound method for reconciling disparate perspectives.</p><h4><strong>Results / Expected Results</strong></h4><p>Discovery phase is essentially a viaduct between a theoretical concept and the authentic development of the product. It is a process of ultimate realization of what the Client needs, beyond the limitation of a functional specification.</p><p>A well done Discovery phase provides stakeholder with several results:</p><p><strong>Project requirements are validated based on evidence rather than assumptions</strong> which reduces potential for costly mistakes to occur.</p><p><strong>Selected approach reflects a balance between Client’s business goals and User’s needs</strong> highlighting user experience and increasing chances for project success.</p><p><strong>Success is determined by objectives, not deliverables</strong> ensuring focus is on value of the product and not on simply building the product.</p><p><strong>Better and cheaper solution</strong> without last moment costly changes that may pause or completely block product development.</p><h3><strong>Perfect fit or not?</strong></h3><p>We strongly believe that<strong> short-term gains are not worth the long-term pain</strong>, and we always emphasize Discovery phase as a high priority. We do, however, understand that some Clients don’t have the time or budget and might opt for skipping it. Nevertheless, this phase is of ultimate importance for businesses with serious intent and ambition.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=41100f95fd65" width="1" height="1" alt=""><hr><p><a href="https://medium.com/maestral-solutions/discovering-your-scope-41100f95fd65">Why Discovery Phase Is The Most Important Phase In Software Development Cycle</a> was originally published in <a href="https://medium.com/maestral-solutions">Maestral, an HTEC Group Company</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Exploring A New Framework: Nexus]]></title>
            <link>https://medium.com/maestral-solutions/birth-of-a-new-species-the-nexus-framework-5769d9341199?source=rss-faffa94143e1------2</link>
            <guid isPermaLink="false">https://medium.com/p/5769d9341199</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[outsourcing]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[nexus]]></category>
            <dc:creator><![CDATA[Ajla Fijuljanin]]></dc:creator>
            <pubDate>Fri, 31 Aug 2018 13:20:35 GMT</pubDate>
            <atom:updated>2019-01-04T12:05:50.459Z</atom:updated>
            <content:encoded><![CDATA[<p>Whether it is due to frustration, creativity or combination of both, the modern age software industry is overflowing with ever-emerging frameworks and working methodologies. A few make money out of it, while others struggle to change and adapt to processes that aim ‘to magically solve their issues’. Focus on the actual work is being lost, and very often, more damage is made. Nevertheless, there is nothing wrong with frameworks themselves, but rather with people’s perception of them. Companies promoting the use of a certain framework forget that they act as guidelines and not as a set of rules set in stone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/829/1*u-Zuhtk96pyPnvkxU6QMnA.png" /><figcaption>Source: vitzteams.com</figcaption></figure><p>Once upon a time, there was a set of principles known as <a href="http://agilemanifesto.org/">the Agile Manifesto</a>. The manifesto came out as a solution provided by the seventeen frustrated software engineers, yearning for an alternative to the existing documentation driven software development processes. They presented a way all stakeholders can collaborate at all times by following a set of procedures in order to deliver quality, continuously.</p><blockquote>We are uncovering better ways of developing<br>software by doing it and helping others do it.</blockquote><blockquote>- <a href="http://agilemanifesto.org/">Manifesto for Agile Software Development</a></blockquote><p>The agile principles emerged in 2001 putting in focus linear requirements-based processes that attempted to impose predictable delivery methodologies and project management processes driven by time and output.</p><p>Improvements were seen immediately, but agile did not manage to kill off complex management layers and the embedded waterfall behaviors. Over time the agile principles have been incorporated into many management practices.</p><p>There are a number of larger scaled frameworks and their derivatives in the market place today, ranging from <em>Lean Startup, Cynefin, Portfolio Management, Right Shifting, Test Driven Development,</em> to <em>Extreme Programming, Scrum, Kanban</em> and more. Agile remains an umbrella term that means different things to different people.</p><p>Fast forward to 2018, the agile methodology<a href="https://www.scrumguides.org/scrum-guide.html"> Scrum</a> seems to be an absolute favorite in the business world. With Scrum, the product is built in a series of fixed-length sprints that give teams a framework for releasing software on a regular basis and bringing them a feeling of tactile progress.</p><p>Fixed and limited to a one month period, Scrum Sprints reinforce the importance of good estimation and fast feedback from tests, thus solving the struggles encountered by other frameworks. However, in the world where organizations need to build products that bring value, and do so better, faster and less costly, Scrum revealed not enough.</p><p>Trying to scale by adding more developers and managers harms the workflow and collaboration between teams, further affecting transparency and accountability. A potential solution comes from one of the creators of the Scrum Framework, Ken Schwaber. He created the <a href="https://www.scrum.org/resources/online-nexus-guide">Nexus Framework</a> in 2015, and refreshed it just recently in 2018.</p><p>Preserving Scrum, the Nexus Framework uses an iterative and incremental approach to scaling software and product development, but it augments it minimally with one new role and additional events and artifacts. It is used by organizations when multiple Scrum teams work on one product and struggle with cross-team dependencies and integration issues.</p><p>Nexus introduces the <em>Nexus Integration Team</em> (NIT) which is responsible for successful integration of the entire workload created by all Scrum teams. <br>It also introduces two new <strong>artifacts</strong>: <em>Nexus Sprint Backlog </em>and the <em>Nexus Goal.</em></p><p><strong>Nexus Sprint Backlog</strong> represents the sum of all product backlog items from the sprint backlogs of the individual scrum teams, and it is used to highlight team dependencies. Similarly, <strong>Nexus Sprint Goal</strong> is the composite of sprint goals of the scrum teams within the Nexus.</p><p>Four new <strong>events </strong>are introduced:</p><p>1. <strong><em>Nexus Sprint Planning</em></strong> coordinates the activities of all scrum teams in a Nexus for a single sprint. <br>2. <strong><em>Nexus Daily Scrum</em></strong> is attended by representatives from individual development teams who gather to inspect the current state of the Integrated Increment and identify integration issues and cross-team dependencies. <br>3. <strong><em>Nexus Sprint Review</em></strong> is held at the end of the sprint to gather feedback on the Integrated Increment and to adapt the product backlog if needed. It replaces individual scrum team sprint reviews.<br>4. <strong><em>Nexus Retrospective</em></strong> is a formal opportunity to look back and create a plan for improvements. The focus is on identifying cross-team dependencies, challenges and potential solutions, and agreeing on how to visualize and track identified actions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qd0SYl5VVCLFtG7suNnnfw.png" /><figcaption>Nexus Framework for Scaling Scrum</figcaption></figure><p>Additionally, unlike Scrum, Nexus makes <strong>Refinement</strong> <strong>mandatory </strong>which<strong> </strong>serves a dual purpose: it helps the scrum teams efficiently delegate backlog items across teams. Refinement is continuous throughout the sprint to ensure tasks are sufficiently independent so there is no conflict.</p><h3>The focus remains on the self-organizing teams and organizational bottom-up intelligence. In its heart lies the belief that autonomy, ownership, and continuous improvement do not need to be compromised even at scale.</h3><p>Just like other frameworks, Nexus alone is not enough for success. It stands for a minimum needed to empower teams to effectively deliver value to clients and get better at it with each sprint completed. It represents a relationship between people who appreciate each other and respect the teamwork spirit when working together toward a single goal, and it should be taken as such.</p><p>While Nexus is a promising framework which mitigates problems raised through the use of Scrum, it is down to actual teams (users) and their readiness to adapt to changes that will ultimately bring value.</p><p>Lastly, the ultimate formula for success remains constant; being stubborn on a vision and flexible on how to deliver.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5769d9341199" width="1" height="1" alt=""><hr><p><a href="https://medium.com/maestral-solutions/birth-of-a-new-species-the-nexus-framework-5769d9341199">Exploring A New Framework: Nexus</a> was originally published in <a href="https://medium.com/maestral-solutions">Maestral, an HTEC Group Company</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>