<?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 Doğan Güneş on Medium]]></title>
        <description><![CDATA[Stories by Doğan Güneş on Medium]]></description>
        <link>https://medium.com/@dogan.gunes?source=rss-d86177afa3b8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*mlPIRSfTY8siyfoPaLObfA.png</url>
            <title>Stories by Doğan Güneş on Medium</title>
            <link>https://medium.com/@dogan.gunes?source=rss-d86177afa3b8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 19:54:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dogan.gunes/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[My favorite statement of Deming]]></title>
            <link>https://medium.com/@dogan.gunes/my-favorite-statement-of-deming-b87f0c712ad7?source=rss-d86177afa3b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/b87f0c712ad7</guid>
            <category><![CDATA[deming]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[kanban]]></category>
            <category><![CDATA[pdca]]></category>
            <category><![CDATA[kanban-system]]></category>
            <dc:creator><![CDATA[Doğan Güneş]]></dc:creator>
            <pubDate>Wed, 28 Oct 2020 21:25:26 GMT</pubDate>
            <atom:updated>2020-10-28T21:25:26.754Z</atom:updated>
            <content:encoded><![CDATA[<p>I am sure many of you heard name Deming as PDCA cycle or understanding of variation in Kanban Systems as special causes and common causes</p><p>While reading the Book — Out of Crises, W. Edwards Deming, I noted down some statements from the book.</p><p>1. “Quality begins with the intent, which is fixed by the management.”</p><p>2. “Best effort is not sufficient, everyone must do the right thing rather than their best.”</p><p>3. “Seek long terms accords with supplying.”</p><p>4. “Constant improvement of their incoming quality is possible if vendor and purchaser work together.”</p><p>5. “You cannot build quality by inspection, but when the quality is not there, inspection may be the only answer.”</p><p>6. American managements approach: “How long may we go in quality without losing customer.” whereas Japanese management approach: “They just go right ahead and improve the process without regard to figures.” Japanese thus improve the productivity, decrease costs, and capture the market.</p><p>7. “<em>A common disease that afflicts management and government administration the world over is the impression that “Our problems are different.” They are different, to be sure, but the principles that will help to improve quality of product and of service are universal in nature.</em>”</p><p>8. To introduce a major change: “<strong>Support of top management is not sufficient. </strong>They must know that it is that they are committed to, that is what they must do. Those obligation cannot be delegated. Support is not enough, action is required.… and if you cannot come, send nobody”</p><p>Frankly, I was so surprised to see how much Scrum, Kanban and SAFe was influenced by this book.</p><p>Item Number 8 has been my favorite! What is your favorite statements? Do you agree with him?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b87f0c712ad7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Glimpse of Leadership in Transformational Change]]></title>
            <link>https://medium.com/@dogan.gunes/a-glimpse-of-leadership-in-transformational-change-3dcd6ddb6437?source=rss-d86177afa3b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/3dcd6ddb6437</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[leanagile]]></category>
            <category><![CDATA[agile-transformation]]></category>
            <category><![CDATA[change-management]]></category>
            <dc:creator><![CDATA[Doğan Güneş]]></dc:creator>
            <pubDate>Thu, 20 Aug 2020 10:53:30 GMT</pubDate>
            <atom:updated>2020-08-20T10:53:30.379Z</atom:updated>
            <content:encoded><![CDATA[<p>Any transformational change without a clear vision will not convince people to take part in it due to the challenging change journey. Therefore, the leaders who introduce the change should address:</p><ul><li>The current pain-points</li><li>The transformational change journey</li><li>The future state (A.K.A Vision)</li></ul><p>First, the more the current pain points hurt, the easier it is to gain followers and allies for the change. The dissatisfaction of the status-quo should create a sense of urgency for the change such as bad quality, higher customer dissatisfaction, long time to market, long lead times etc. Even though the sense of urgency would trigger people to be in favor of the change, the leaders should communicate the future state clearly in order to attract people to work on and own the change with them. Let us keep in mind a good vision will depict the future state where the current pain-points are solved.</p><p>After making people believe in the vision and convincing them to support it, design principles of the change need to be crafted and internalized by everyone. Design principles may vary from journey to journey, nevertheless Inspect &amp; Adapt, which the progress is reflected towards the goals and adjustment is done in case of variations from the goals, is an essential one for those journeys in the complex domain where we do not know what we do not know. (A.K.A <a href="https://www.youtube.com/watch?v=N7oz366X0-8&amp;feature=youtu.be">unknown-unknowns</a>)</p><p>Next, the journey of the change needs spectacular leadership where the leaders would create an environment where people can take more responsibilities and try out new things. Leaders need to provide trainings for new skills and a new way of working, in case people need to unlearn and learn new things. Therefore, the leaders should use their power to invoke the power within their teams. Especially when it comes to unknown-unknowns things, Leaders should provide a safe-to-fail environment to enable a learning organization. Thus, people could learn from their failure without fear and adjust their action accordingly towards the desired state.</p><p>To sum up, we need a sense of urgency towards the change, a strong leadership to influence people to drive the change together and communicate the desired state. Last but not least, we need design principles to create a safe-to-fail environment so people are not afraid of trying out new things.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3dcd6ddb6437" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OKRs — Objectives and Key Results]]></title>
            <link>https://medium.com/@dogan.gunes/okrs-objectives-and-key-results-809de29dc22e?source=rss-d86177afa3b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/809de29dc22e</guid>
            <dc:creator><![CDATA[Doğan Güneş]]></dc:creator>
            <pubDate>Wed, 29 Apr 2020 08:53:55 GMT</pubDate>
            <atom:updated>2020-04-29T08:53:55.358Z</atom:updated>
            <content:encoded><![CDATA[<h3>OKRs — Objectives and Key Results</h3><h4>What is OKRs</h4><p>OKR (Objectives and Key Results) is an goal setting tool to <strong>align </strong>people and engage them around measurable and ambitious right goals. OKRs are frequently set, tracked and re-evaluated — usually quarterly.</p><blockquote>The goal is to ensure that everyone is going to same direction with clear priorities and constant pace.</blockquote><p>OKR concept came from Intel and spread to other companies in Silicon Valley. Google adopted it in 1999 and is still using it. Besides Google not only digital companies such as Spotify, Twitter, Linkedin, and Airbnb are using OKR but also non digital companies such as Walmart, Target, The Guardian, Dun and Bradstreet and ING Bank.</p><p><a href="https://en.wikipedia.org/wiki/John_Doerr">John Doerr</a> is an American investor and venture capitalist. He started his career in intel and went on investing in other companies such as Google and Amazon. He introduced Google to OKR and is the author of <em>Measure What Matters,</em> a book about goal-setting.</p><blockquote>A decent goal describes both what you want to achieve and how you are going to measure it. The goal without measurement is only an desire.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/809/1*mjIZUikCQBL-rgKxlVuzHA.png" /><figcaption>Doerr’s Goal Formula</figcaption></figure><p>I will (Objective) as measured by (this set of Key Results).</p><p><strong>Objectives </strong>are what you want to achieve. And they are memorable, qualitative, short, inspirational and engaging. An objective should motivate and challenge the team.</p><p><strong>Key Results (KR)</strong> are metrics to measure the progress towards the Objectives. Each objective should have a set of 2 to 5 KRs. All KRs have to be quantitative and measurable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/730/1*ggAsoA_O_ozCywhPZPOS1A.png" /><figcaption>Marissa Mayer, a former Google’s Vice<br>President</figcaption></figure><p><strong>Example 1:</strong></p><p><strong>Objective:</strong><br>Create an Awesome Customer Experience<br><strong>Key Results:</strong><br>➔ #KR1: Improve Net Promoter Score from X to Y.<br>➔ #KR2: Increase Repurchase Rate from X to Y.<br>➔ #KR3: Maintain Customer Acquisition cost under Y. (Countermeasure)</p><p>Create an Awesome Customer Experience is a good objective but how are we going to measure it? Remember that it is not a goal without measuring it.</p><p>#KR1 and #KR2 are good options to measure if our customers feel good to recommend us and buy again from us. However, we want to make our customer happy while keeping cost under control. There is a limit on the price of keeping customer happy. That is why we create #KR3 as counter-measure.</p><p><strong>Example Two</strong><br>Now consider a team that wants to increase the engagement with a digital service:<br><strong>Objective:</strong><br>Delight our customers<br><strong>Key Results:</strong><br>➔ Reduce revenue churn (cancellation) from X% to Y%.<br>➔ Increase Net Promoter Score from X to Y.<br>➔ Improve average weekly visits per active user from X to Y.<br>➔ Increase non-paid (organic) traffic to from X to Y.<br>➔ Improve engagement (users that complete a full profile) from X to Y.</p><h4>What Are The Benefits Of Using OKRs</h4><ul><li>They use shorter goal cycles, thus companies can adapt and respond to change</li><li>It is very easy to understand and adopt to lightweight process that reduces time spent on creating Goals from month to days.</li><li>They are transparent as the Primary purpose of OKR is to create alignment in the organization. <strong>The CEO’s or Board of Management’s OKRs are should be available on the Intranet.</strong></li></ul><h4>OKR Nested Cadences</h4><p><strong>OKR’s strategic cadence</strong> is at enterprise level with long-term, high-level and usually annual</p><p><strong>OKR’s tactical cadence </strong>is at team level with shorter term and usually quarterly</p><p><strong>OKR’s operational cadence</strong> is usually weekly and is for the tracking the initiatives.</p><h4>OKR’s Goal Settings</h4><p>Despite the fact that traditional goal setting tools are designed as top down approach, OKRs do not cascade. The goal setting in OKR is <strong>bidirectional </strong>(top-down Strategic OKR’s and bottom-up tactical OKRs are aligned). By applying bidirectional goal setting, we ensure engagement and better understanding of strategy. Having the teams in touch with the managers while creating their tactical OKRs should result in roughly %60 contribution to strategic OKRs.</p><blockquote><strong><em>OKRs Strategic Cadence(Yearly)→ Enterprise Level</em></strong></blockquote><blockquote><strong><em>OKRs Tactical Cadence(quarterly) → Team Level</em></strong></blockquote><blockquote><strong><em>OKRs Operation Cadence (Weekly) → Check-ins for tracking results.</em></strong></blockquote><p><strong>Types Of Key Results</strong></p><p>Activity based KRs are based on measurement of completion of a task or delivery whereas value-based KRs are based on measurement of the value delivered to organization or to customers.</p><blockquote><strong><em>Activity Based KRs are output oriented whereas Value-based KRS are outcome oriented.</em></strong></blockquote><p>Examples of <em>Activity Based KRs;</em></p><ul><li>Launch new training program</li><li>Create customer Database</li><li>Develop a new campaign</li></ul><p>Examples of <em>Value Based KRs;</em></p><ul><li>Improve Net Promoter Score from X to Y.</li><li>Increase Repurchase Rate from X to Y.</li><li>Maintain Customer Acquisition cost under Y.</li><li>Reduce revenue churn (cancellation) from X% to Y%.</li><li>Increase Net Promoter Score from X to Y.</li><li>Improve average weekly visits per active user from X to Y.</li><li>Increase non-paid (organic) traffic to from X to Y.</li><li>Improve engagement (users that complete a full profile) from X to Y.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/852/1*Aimxp6vuR7wcL6H5QVRH_A.png" /><figcaption>Structure of a Value-based KR</figcaption></figure><p>Below is a list of examples of Activity-based Key Results and the equivalent Value-based Key Results.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/820/1*iZWhdADVVUimYNO8Dz5C1g.png" /></figure><p>Even though we wish to have value-based KRs, it is ok to start with activity-based KRs in order to create basis and start collecting metrics for the KRs.</p><blockquote>When your organization adopts OKR, you are going to have big challenges at creating value-based KRs. My recommendation is teaching the organization right OKR set-up structured on value-based KRs, and letting them know using activity-based KRs for transition phase to collect metrics is okay, too.</blockquote><p><strong>Objectives, Key Results, and Initiatives</strong></p><blockquote>Objectives: What we want to achieve.</blockquote><blockquote>Key Results: How are we going to measure our progress towards the objective(s)?</blockquote><blockquote>Initiatives: What we are going to do to reach our OKR</blockquote><p>Initiatives are anything such as projects, tasks or activities that change the numbers we have in KR(s) to track the progress. If it does not change, then the initiatives must change.</p><h4>Moonshots vs. Roofshots</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/813/1*-g8z9-jGur2mtTR5_3oqQw.png" /><figcaption>Moonshots vs Roofshots</figcaption></figure><p>Moonshots are a foundational building block of OKR, but they require a lot of organizational maturity. Otherwise moonshots can cause a few issues:</p><ul><li>Demotivate the team by only achieving %60 of the OKRs</li><li>Lack of accountability and commitment due to accepting it as stretch goal</li></ul><blockquote>Decoupled OKRs and Compensation: OKR is a management tool, not an employee evaluation tool. As such, a second tenet of the OKR framework is to separate OKRs from compensation and promotions.</blockquote><h4>The Check-in Structure</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/811/1*_nEgz5_tkJkRrbqgJT5Ujw.png" /></figure><p>Check-in is recommended to be a short and often ceremony. Weekly or bi-weekly not more than 30 minutes. During the Check-in, the team goes through each element for each Key Result:</p><ul><li><strong>OKR Progress:</strong> Is there any change in KRs since last check-in?(Quantitative)</li><li><strong>Impediments:</strong> Is there any <strong>external </strong>factor, blocker that inhibits the progress?</li><li><strong>Initiatives</strong>: If there is no progress on KRs, what else are we going to do to improve results?</li><li><strong>Confidence Level:</strong> How confident are we that we will reach each KR? (Qualitative)</li></ul><p>This article is highlights from “The-Beginners-Guide-to-OKR, by Felipe Castro”. If you want to learn more, please read the main source.</p><p>Dogan Gunes</p><h4>Reference:</h4><p>The-Beginners-Guide-to-OKR, by Felipe Castro</p><p><a href="https://en.wikipedia.org/wiki/John_Doerr">https://en.wikipedia.org/wiki/John_Doerr</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=809de29dc22e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Distributed Team PI Planning]]></title>
            <link>https://medium.com/@dogan.gunes/distributed-team-pi-planning-e9475442f104?source=rss-d86177afa3b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/e9475442f104</guid>
            <dc:creator><![CDATA[Doğan Güneş]]></dc:creator>
            <pubDate>Fri, 20 Mar 2020 08:59:14 GMT</pubDate>
            <atom:updated>2020-03-20T09:03:17.170Z</atom:updated>
            <content:encoded><![CDATA[<p><em>I have decided to write down the highlights from the books and article I read. Please go to the main resource if you would like to learn more.</em></p><p>· Unless there is pandemic such as corona virus, gather people together anywhere possible. If travel cost are so high for oversea trips then bring those people in different locations in the same cities or in the same countries.</p><p>· Create agenda per different time zones</p><p>If it is not possible to have the planning simultaneously, then we have briefings simultaneously in order to create alignment. Let us remember that Alignment is one of the 4 core values of <a href="https://www.scaledagileframework.com/">SAFe</a>.</p><p>· If it is not possible to have all the team attends the briefings at the same time, an alternative is to record and deliver the briefings ahead of the time then use a smaller portion of overlapping time for questions.</p><p>· Assure that people who start earlier than usual have access to offices</p><p>· Provide food and beverage and transfer for people who stays late in the night.</p><p>· For every tool is being used, there should be the backup.</p><p>· Use online spreadsheet as a way to present teams’ draft and final plan. It increase the visibility for remote employees.</p><p>· Have a named facilitator at each location.</p><p>· RTE (a.k.a Chief Scrum Master) should work with Scrum Master and do a dry-run of the event, considering some of the different scenarios that might arise and the steps that should be taken to resolve them.</p><h3><strong>References</strong></h3><p><a href="https://www.scaledagileframework.com/distributed-pi-planning/">Distributed PI Planning - Scaled Agile Framework</a></p><p>#SAFe #PIPlanning #DistributedPIPlanning</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e9475442f104" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Reasons Behind Why Agile At Scale Does Not Succeed]]></title>
            <link>https://medium.com/@dogan.gunes/the-reasons-behind-why-agile-at-scale-does-not-succeed-a97e14e5c406?source=rss-d86177afa3b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/a97e14e5c406</guid>
            <category><![CDATA[scaled-agile-framework]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[failure]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[safe]]></category>
            <dc:creator><![CDATA[Doğan Güneş]]></dc:creator>
            <pubDate>Wed, 13 Nov 2019 12:47:27 GMT</pubDate>
            <atom:updated>2020-04-12T21:14:16.910Z</atom:updated>
            <content:encoded><![CDATA[<p>The <strong>Reasons</strong> Behind Why Agile At Scale Does Not Succeed.</p><p>I am going to share my opinion on the reasons behind of Why Agile At Scale Does Not Succeed.</p><p>Even though I use vocabulary of SAFe (Scaled Agile Framework), I believe the reasons are common for Scaling Agile endeavors</p><p><strong>Knowledge Worker: </strong>The worker who knows his/her job more than his/her manager.</p><p><strong>Cost Of Delay: </strong>it is the partial derivative of the <em>total expected value</em> with respect to <em>time</em>. Cost of Delay combines an understanding of value with how that value leaks away over time</p><p><strong>SAFe:</strong> Scaled Agile Framework for Lean Enterprises</p><p><strong>ART: </strong>Agile Release Train (Team of teams including several additional role in SAFe)</p><p><strong>WSJF (Weighed-Shortest-Job-First): </strong>It is a prioritization model used to sequence jobs to produce maximum economic benefit.</p><p><strong>Value Stream:</strong> A value stream is a long-lived series of steps used to deliver value, from concept or customer order to delivery of a tangible result for the customer.</p><h4>1. <strong>The organization does not know WHY they should transform the company to agile.</strong></h4><p>Most of the enterprise organizations start Agile Transformation without understanding it because other companies have already started it .</p><p>Agile way of working is proved to be effective and powerful especially at VUCA world. That is why whoever understands agility and applies it to their organization has big advantage on the changing market and demand by keeping switch cost low. Those organization that acting agile has almost no chance in long term in the market unless they understand the reason of being agile.</p><h4><strong>2.</strong> <strong>Management does not understand its role in transformation</strong></h4><p>Crucial managerial roles are leaders-as-service roles (servant-leader) in agile world. Thus, managers must gain leadership skills such as coming-up with vision to trigger change, challenging status quo, lifelong-learning, spreading trust by walking to talk, giving major part of his/her power to the team, using his/her power to awake the power of his people and so on.</p><p>Leaders try to bring the transparency especially on decision making with very clear understanding of centralize and decentralize decision-making. Therefore everyone know what decision can be done by them. When it comes to decision with very high Cost Of Delay (CoD), the response time is very crucial. Knowledge workers most of the time work on the item with high CoD.</p><p>Managers either don’t understand their new role or they don’t want to change their role since they do not want to lose control power.</p><h4><strong>3.</strong> <strong>Management does not create an eye-to-eye level</strong></h4><p>Managers don’t empower their people. Managers make decision even though knowledge workers know the work they do much more than his/her line manager. In such a working environment, knowledge worker are not able to raise a case or come up with an unique solution due to lack of eye-to-eye level with their manager.</p><p>Knowledge worker will be ineffective and will shut-up unless managers act like a leader and create safe environment so that people are not afraid to raise an issue to answer a change nor fix a problem when they have different opinion than their manager.</p><h4><strong>4.</strong> <strong>There is lack of trust</strong></h4><p>Most of the trust issues’ root cause is the political climates in the organizations. When we dig into politic we see that the main reason is the lack of transparency. A wise man said that “It is very hard to manage the secret” therefore leaders should start with building transparency by walking their talk, treating everyone fairly, creating safe-to-fail environment, accepting their own failures. If leaders do not inspire the organization to build trust, trust will not come by itself. With lack of trust it is not possible to have well-performing teams or team-of-teams. Let me remind you that all the five values of scrum and the three pillars of scrum is to build trust.</p><h4><strong>5.</strong> <strong>The teams are not organized around value stream or no value stream at all</strong></h4><p>Every enterprises want to achieve shortest sustainable time to market. There is why organization scale up to create end-to-end flows.</p><p>A value stream is a long-lived series of steps used to deliver value, from concept or customer order to delivery of a tangible result for the customer. Most of the lack of success of Agile Scaling is either wrong value stream mapping or no value stream mapping at all. Organizations ignore this step or diminish it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/605/1*AM49esEEMjBzDhmPMFyEjg.png" /></figure><p>Once value stream is mapped correctly, all the needed part organize around it to define, build, test and deploy with the minimum dependency.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/605/1*83R7jeFxdaKBPMo4IfmRrw.png" /></figure><h4><strong>6.</strong> <strong>The team of teams have not all the relevant skill</strong></h4><p>The teams and team-of-teams have lack of relevant skills to [define-build-test-deploy] without dependency on others. The main reasons are lack of value stream mapping, lack of self organizing, assigning people to the teams, lack of silos breaking, missing skills or departments (silos) around value streams. Lack of continues learning causes missing skills as well. Most of ARTs ignores Innovation and Planning Iteration (IP Iteration), therefore the team members cannot improve their skills. As one of the Agile Manifesto’s Principle states that “Continuous attention to technical excellence and good design enhances agility.”</p><h4><strong>7.</strong> <strong>Instead of breaking all the silos, new silos are built in the scaled agile frameworks especially between IT and Business Units.</strong></h4><p>It is very hard to organize around value stream while the rest of the organization consists of silo departments. Because there is power-game and politics around value stream. People are fighting for their department not for the whole value stream. The teams, individuals even leaders feel unpowered since there are different decision making authorities. Especially when it comes to interaction between teams, department heads place barrier between teams.</p><h4><strong>8.</strong> <strong>All team members are assigned to teams by the management instead of self-organizing.(The teams are neither empowered nor encouraged to self organize around value stream)</strong></h4><p>What is expected from Leaders is to come-up with business context, latest market situation and vision for the product. Therefore, people self-organize around value stream regarding to predefine constraint such as having at least one ios developer, one android developer, one UX designer, one PO, one SM and etc. What we see is that managers assigns roles to individual and assign them to a specific team. Not only there is no pull principle on choosing Scrum Master Role, Product Owner Role, Development Role, but also there is no empowerment to choose their own team.</p><h4><strong>9.</strong> <strong>Product managers act like traditional line manager and they assign all the features &amp; stories &amp; epics to the teams in advance with limited detail or no detail at all.</strong></h4><p>They prepare all the objectives which are kind of sprint goals that should be created by the teams and assign each of them to the teams. Instead of coming up with new ideas and hypothesis that create benefit for customers who are ready to pay for it, they assign product backlog items ,which have lack of detail, no acceptance criteria, no benefit hypothesis to the individuals. Product managers are supposed to continuously explore the market with the new hypothesis to create new capabilities that will create new market and increase the market share.</p><h4><strong>10.</strong> <strong>Influence of line management as micro-management on the team member of scaled agile teams</strong></h4><p>At scaling agile teams, all capabilities and empowerment should be within the team. During the big room planning team members commit to Program Increment Objectives however when they go back to their department, line managers assign them another works to prevent them to work for what they commintted during the big room planning.</p><h4><strong>11.</strong> <strong>Applying phase-gate approach at first glance. (No increment at the end of sprint, iteration, program increment)</strong></h4><p>There is almost no value stream mapping. And the teams are created by the managers. On the other hand teams are component team rather than product team.</p><p>No single source of product backlog since teams are not capable to pull the highest prioritozed item from the backlog. Therefore there are multiple product backlogs. There are big amount of dependencies between team that lead time of a PBI is getting high and high. Since teams are not cross functional, prioritisation based on WSJF does not create advantage to the organization. Market shrinks or customer satisfaction decreases</p><p><a href="https://agilemanifesto.org/">https://agilemanifesto.org/</a></p><p><a href="https://www.scrumguides.org/scrum-guide.html#values">https://www.scrumguides.org/scrum-guide.html#values</a></p><ul><li><a href="https://www.scaledagileframework.com/">SAFe 6.0 Framework</a></li><li><a href="https://en.wikipedia.org/wiki/Cost_of_delay">Cost of delay - Wikipedia</a></li></ul><p><a href="https://www.scaledagileframework.com/wsjf/">https://www.scaledagileframework.com/wsjf/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a97e14e5c406" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Notes From Essential Upstream Kanban Book]]></title>
            <link>https://medium.com/@dogan.gunes/notes-from-essential-upstream-kanban-book-cb918e720ea2?source=rss-d86177afa3b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb918e720ea2</guid>
            <category><![CDATA[lean-kanban]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[upstream]]></category>
            <category><![CDATA[kanban]]></category>
            <category><![CDATA[lead-time]]></category>
            <dc:creator><![CDATA[Doğan Güneş]]></dc:creator>
            <pubDate>Sat, 21 Sep 2019 11:56:27 GMT</pubDate>
            <atom:updated>2019-09-21T11:56:27.597Z</atom:updated>
            <content:encoded><![CDATA[<p>In this story I am going to share my notes and highlights from Essential Upstream Kanban Book written by Patrick Steyaert.</p><p>I assume whoever reads this article has fundemantal kanban knowledge.</p><p>Once we build System Kanban by visualizing significant amount of value flow, establishing WIP limit and measuring the KPIs, (First, a kanban system with no measurement is not Kanban System. Second, even though measuring is must in Kanban Systems, we must improve the figures of measurements. The purpose of enterprises are to achieve shortest sustainable lead time to market with high quality and value to customer. Therefore if we are going to measure one thing, it must be lead time.) Now the questions are “What should we work on now? What can wait until later? What should we discard together?”</p><p>“If relieving downstream delivery workers from overburdening made sense, did it also make sense to relieve upstream creative workers, those who must discover the concepts and ideas, from similar overburdening? And It emerged that what was more important with upstream creative activities wasn’t limiting the number of options in development but to signal the replenishment of ideas at a given stage of elaboration . It was necessary always to have enough options from which to choose, sufficient choice to make the best commitments and facilitate the triage process.”</p><p>“Upstream Kanban is to have embedded options. Thus, It is not so much about managing flow as seen with downstream, Delivery Kanban systems. It is instead marshaling options-having enough choices at the right time, without overburdening the system and creative workers who generate those options by asking them to maintain too many of them.”</p><p>Business agiltiy requires the fast paced upstream kanban and the low paced downstream kanban to be tuned.</p><p>There is a case study of an IT maintanence team in the book to show why just improving the speed of delivery is not sufficient due to difference between plain agility an business agility.</p><h3>System Kanban Success</h3><p>“The IT maintenance team that we use in a case study handles<br>change requests and also delivers small projects across Enterprise<br>Resource Planning (ERP), Business Intelligence (BI), Electronic<br>Data Interchange (EDI), and Java applications. Historically the<br>team has been coping with a persistently large backlog (+80 items,<br>see Figure 1) and long, unpredictable lead-times.<strong> End-to-end<br>customer lead-times</strong> (the time from <strong>“request” </strong>to <strong>“ready to deploy”</strong>)<br>have been varying <strong>between less than 1 week and 30+ weeks</strong>. Also<br><strong>system lead-times</strong>, i.e. the time from <strong>“Ready to develop”</strong> to<strong> “Ready<br>for UAT (user acceptance testing)”</strong>,<strong> have been long (+13 weeks)</strong><br>and variable.”</p><p>System Kanban implements flow by allowing people to pull work rather having work being pushed onto them. Pull is implement either setting WIP limit or using explicit Kanban Token.</p><p>“WIP limits emphasize the importance of constraints to enable the collaboration that is necessary for a steady flow. In other words, the team needs to work together to keep WIP low and lead-times short and predictable (and flow stable). Explicit Kanban tokens emphasize the importance of feedback signals. The Kanban token is a signal that new work can be started, or that no new work can be started. It signals that team members need to work together to finish work before starting new work.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/951/1*sD3-sjfHm96qqn-gURo4lw.png" /><figcaption>Figure 1: System Kanban</figcaption></figure><p>System Kanban limits the success due to constraint of agiltiy at the team level. Collaboration within teams and between team and its customers must be enhanced not on just about work that is being performed but also on incoming and outgoing work. They need to collaborate to have end-to-end stabile flow.</p><p>System Kanban focuses on the flow of work within established service. While workers may be pulling the work in System Kanban, the customer still push the orders (i.e. pushing request, ideas, requirements)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_z-VbAQSOmiZmzFWhei7mg.png" /><figcaption>Figure 2: System Kanban in the context of the end-to-end flow</figcaption></figure><p>Implementing System Kanban without end-to-end flow, customers create large amount of demand in front of the System Kanban while the team complaints about the work delivered but has not accepted by the customers. The only way to sustain steady end-to-end flow of value is to shift mindset to where customers pull value rather than just pushing orders.</p><h3><strong>A Deeper /Wider Look</strong></h3><p>The purpose of the Upstream Kanban is to manage the stream of incoming requests before being able to commit the work for execution downstream.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wxchZxa_pUcKg5bof0l2sA.png" /><figcaption>Figure 3: Upstream + Downstream Kanban</figcaption></figure><p>“When only a limited number of requests can be assessed, there is quite some pressure to pick the right alternative to assess before the assessment even takes place. In the end not all value is alike; and should not be treated alike. When uncertainty is low (as in low value/low risk requests) there is no risk in expending the full analysis and assessment effort in one go. When uncertainty is high (as in high value/high risk requests) it is advisable to stage the assessment effort. In more technical terms this means that for low uncertainty requests, we can commit the full analysis and assessment effort once we decide to assess the request. For high uncertainty items, we first create an option (i.e. an initial limited effort assessment) before committing the full analysis and assessment effort.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1005/1*dY3yg46-zAl_qSd3PmrC4g.png" /><figcaption>Figure 4</figcaption></figure><h3>Pushing The Boundaries</h3><p>The purpose of the Upstream Kanban is to prepare work items by evaluating differtent options. As we can see the large WIP in the “Analysis ongoing” column. As the findings of the investigation in the case study show the reason of large area of analysis ongoing (the light blue in CFD shown in Figure 5.) is due to lack of preparation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/709/1*4jpKjVZswN7pQHaL3YFsfg.png" /><figcaption>Figure 5: CFD Charts of a team in the case study</figcaption></figure><p>The team decide to model two processes for upstream process to distinguish the different processes for synthesis and analysis. The first step -synthesis- is to find consensus for different users and their conflicting and fragmented demands. Only after that the detailed analysis could be applied to the concept and if needed it is broken down to smaller work items to be executed. The role of proper synthesis is crucial to prepare high value/high risk items whereas this steps is skipped for low value/low risk items.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/734/1*w5r0mvT8ItccuB7xTor7Pw.png" /><figcaption>Figure 6: Upstream process for high value / high risk requests.</figcaption></figure><h3>Customer Kanban</h3><p>“From customer push to customer pull”</p><p>Neither Upstream Kanban alone is sufficent nor downstream kanban. Even though Upstream Kanban assure the sufficient options of the variety at all times, it doesn not prevent customer from pushing orders onto the team. Often business users use all their powers to get to work start on those requests however they are not available when the team need them for their inputs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/708/1*5ZnajbAidhIeikjs7pydkA.png" /><figcaption>Figure 7:Customer Kanban.</figcaption></figure><p>“In the ideal world the rate of demand matches the rate of finishing<br>work; in the real world this is seldom the case. Customer Kanban<br>engages the team and the customer to address this problem.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/733/1*WTW9gSWSW9cEgRdmfVkOkA.png" /><figcaption>Figure 8: Customer Kanban vs System Kanban</figcaption></figure><h3>Business Agility</h3><p>Business Agility is the capability to anticipate and collaborate to fulfill demand and extract the highest possible value out of that collaboration.</p><p>What is needed is a close collaboration to identify the best possible options that can be worked on to deliver most value for the customer and the organization; to ensure that at all times a good diversity of options is available; and to collaborate to deliver against those options. What is needed is a customer that pulls value rather than pushing requests.</p><p>References:</p><p>Essential Upstream Kanban, Patrick Steyaert.</p><p><a href="https://www.kanban.university/">https://www.kanban.university/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb918e720ea2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stacey Matrix]]></title>
            <link>https://medium.com/@dogan.gunes/stacey-matrix-ddaf7122cc9c?source=rss-d86177afa3b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/ddaf7122cc9c</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[stacey-matrix]]></category>
            <category><![CDATA[lean-startup]]></category>
            <category><![CDATA[kanban]]></category>
            <dc:creator><![CDATA[Doğan Güneş]]></dc:creator>
            <pubDate>Sun, 10 Mar 2019 23:32:47 GMT</pubDate>
            <atom:updated>2019-03-11T19:22:33.152Z</atom:updated>
            <content:encoded><![CDATA[<p>Merhabalar, bu yazımda size Stacey Matrix hakkında bildiklerimi anlatacağım.</p><p>Geliştiricisinin kim olduğunundan başlayıp,</p><p>Neden Stacey Matrix’ e ihtiyaç duyuluyor ile devam edip;</p><p>Stacey Matrix’ i nasıl kullanabileceğimizi örnekler üzerinden anlatacağım.</p><p>Stacey Matrix, Ralph D. Stacey tarafından geliştirilmiş bir karar verme aracıdır. Ralph D. Stacey uzun yıllar kurumsal ticari firmaların planlama birimlerinde çalışırken, verilen kararların sonuçlarını kestirememeleri onu bu çalışmaya sevketmiştir. Özellikle liderlerin, politika yapıcıların ve yöneticilerin aldığı kararların sonuçlarını kestirmekteki yanilmalari onun bu çalışmaya başlamasında çok büyük etki yaratmıştır. Çalışmasını yaparken organizasyonların ve yönetimlerin Complex Adaptive Systemler olduğunu ve ve organizasyonların aksiyonlarinin tahmin edilemeyen, kendiliğinden ortaya çıkan processler sonucu ortaya çıktığını modellemistir. Yaptığı gözlemlerde liderler, politika yapıcılar ve yöneticiler kağıt üzerinde planladıkları başarıyı planlanmış şekli ile elde edemiyorlarsa elde ettikleri başarı için nasıl bir yol izledikleri soruları onun çalışmalarını sekillendirmistir.</p><p>VUCA Dünyası’nda globalleşme ve digitallesme ile farklı problemler ortaya çıkmıştır. Problemler farklılaştıkça, problemlerin çözümleri de birbirinden farklılaşıyor. Stacey Matrix ‘ i farklı problemlere karşılık gelecek muhtemel çözümleri bulmak için kullanıyoruz.</p><p>Aşağıdaki Stacey Matrix’te gösterildiği gibi, X ekseni: Teknoloji’ nin &amp; Bilgi’ nin kesinlige yakınlığını ve uzaklığını göstermek için kullanılırken, Y Ekseni: Gereksinimlerde uzlaşmanın anlaşmaya yakınlığını ve uzaklığını göstermek için kullanılmaktadır.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KAIp6nWrRJngVr1672IquQ.jpeg" /></figure><h4><strong>Stacey Matrixi 4 bolume ayirabiliriz.</strong></h4><ol><li><strong>Simple</strong>: Teknolojiyi nasıl kullanacagimiza dair bilgi seviyemiz kesinlige çok yakın, ve burdaki ihtiyaçlar üzerindeki anlaşmada uzlaşı hakim sürmektedir. Bu bölgeye düşen problem ile çözüm arasındaki neden-sonuç ilişkisi çok açıktır. Simple bölgesini <strong>Bilinen bilineler (Known knowns) </strong>olarak ta gösterebiliriz. Burada X yaparsak Y bekleriz gibi best practices çözümler hüküm sürer.</li><li><strong>Complicated</strong>:Bu alanda ya Teknoloji &amp; Bilgi kesinlikten uzak yada Gereksinimler üzerindeki uzlaşı anlaşmadan uzak diyebiliriz. (Bu alanı orijinal Stacey Matrix’ ten farklı ele alacağım. Complicated alanları yukardan aşağı sıralarsak; ilkinde politik karar-verme hakim iken, ikincisinde Önyargılı karar-verme hakimdir. Detaylı bilgi için <a href="http://www.gp-training.net/training/communication_skills/consultation/equipoise/complexity/stacey.htm">http://www.gp-training.net/training/communication_skills/consultation/equipoise/complexity/stacey.htm</a>) Complicated alanını<strong> Bilinen Bilinmeyenler (Known unknowns) </strong>olarak gösterebiliriz. Bu alanda neyi bilmediğimizi bildiğimiz için, buraya denk gelen problemlerin neden-çözüm ilişkisi analiz ve expertiz gerektirir. Bu alanda geçmişteki neden sonuç ilişkileri ile gelecek tahmin edilebilir.</li><li><strong>Chaotic</strong>: Bu alanda Teknoloji &amp; Bilgi kesinlikten tamamen uzak ve Gereksinimler üzerindeki anlaşma da uzlaşıdan tamamem uzaktadır. Burda kaos hüküm sürer. Burda olmanın maliyeti çok yüksektir. Burada neden-sonuç ilişkisi yoktur. Burdaki olaylar o kadar karışıktır ki bilgiye dayalı cevap beklemek yanlış olacaktır. Burda aksiyon bazlı çözümler hüküm sürer. Yani ilk önce bir aksiyon alınır. Aksiyonun sonuçları kavrandiktan sonra cevap vermeye çalışılır. Burada ilk aksiyon ağır yaralı birinde ilk önce kanamayı durdurmaya benzer. Chaotic alan çok masraflı ve yorucu bir alan olduğu için, burdaki problemleri biran önce diğer alanlara taşımak gerekir.</li><li><strong>Complex</strong>: Bu alan Complicated ve Chaotic alanları arasında kalan bölgedir. Bu alanda Teknoloji &amp; Bilgi kesinlikten uzak olup, Gereksinimler üzerindeki anlaşma da uzlaşıdan uzaktır. Burda ki problemlerin çözümdeki neden-çözüm ilişkisi arasındaki ilişki ancak retrospectivelerle gozlemlenebilir. Burda deneysel çözümler geçerlidir. Deneyler çok kısa zaman aralıkları ile uygulanır ki; riskler ve kayıplar minimize edilir. Liderler<strong> safe to fail</strong> (hata yapmaya uygun)ortamlar sunmalidirki çalışanlar riske girebilsinler. Sabit sıklıkta <strong><em>Inspect &amp; Adapt</em></strong> teknikleri ile çözüme ne kadar yakın olup olmadığımız gözlemlenir. Bu alanı <strong>Bilinmeyen bilinmeyenler (Unknown unknowns)</strong> olarak ta gösterebiliriz.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/559/1*VWvPsrxlsrUr80nz-v-cYw.png" /></figure><h3>Stacey Matrix Nasil Kullanilir?</h3><p>VUCA dünyasında kurumsal şirketler ve startuplar marketten pay kapmak, yeni marketler oluşturmak için kıyasıya yarışmaktadırlar. Bu yarışı yaparken Stacey Matrix’ ten nasıl faydalanabilecegimize bakalım. Yukarda yazdığım üzere farklı problemlerin farklı çözüm yöntemleri olduğunu bilip, problemi doğru tespit ettikten sonra ilgili çözüme bakmak gerekir..</p><p><strong>Chaotic:</strong>Bu alan için <strong>Discovery (Keşif)</strong> alanı diyebiliriz. Bu alanda amaç müşterinin ihtiyaç duyabileceğini ürünü veya hizmeti kesfetmektir. Bu alan için Design Thinking teknikleri kullanılmaktadır.</p><p><strong>Edge of Chaos:</strong> Bu alan hakkında birşeyler yazmadık. Bu alan Complex ve Chaotic bölge arasındaki şeriti temsil eder. Bu alanı<strong> Define (Tanım)</strong> olarak ta gösterebiliriz. Bu alanda Keşfedilen çözüm tanimlanmaya çalışılır. Bu alanda <strong>MVP </strong>ve <strong>Lean Startup</strong> etkili yaklaşımlardır.</p><p><strong>Complex</strong>: Bu alana <strong>Development (Geliştirme)</strong> alanı da diyebiliriz. Bu alanda tanımlanan çözüm müşterinin gereksinimlerine göre geliştirilmeye çalışılır. Burda müşterinin gereksinimlerini bildigini farz etmek dogru olmaz. Müşterinin gereksinimi ve çözüm arasındaki ilişki ancak retrospectivelerle iliskilendirilebildigi için bu alanda emprik deney yolu ile geliştirme yapılmaktadır. Bu alanda <strong>Scrum, Extreme Programing</strong> etkilidir. Bu bölgede geliştirme yapmak için <strong><em>Transparency, Inspect ve Adapt</em></strong> kaçınılmazdır.</p><p><strong>Complicated: </strong>Bu alana <strong>Delivery (Servis)</strong> alanı da diyebiliriz. Burda complex alanda geliştirilen sistem için servis dağılımı yapılıyor diyebiliriz. Bu alanda analiz ve expertiz gerekebilir. Bu alanda<strong> Kanban ve Scrum </strong>etkilidir. Burdaki servis hizmeti için anlaşma geçmiş datalarin yardımı ile yapılır.</p><p><strong>Simple-Obvious: </strong>Bu alan için de<strong> Delivery (Servis)</strong> alanı diyebiliriz. Burda problemlerin çözümleri formülüze edilebilir durumdadır. Burda amaç kullandığımız kaynaklarda boşuna kullandığımız kaynakları minimize etmektir. Bu alanda<strong> Lean ve Kanban</strong> etkilidirler.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aL13r87p44t_Hbei9TsNkw.jpeg" /></figure><p><strong>Discovery(Keşif) →Define(Tanımlama) →Development(Geliştirme) →Service(Servis) </strong>olarak sıralarsak<strong>;</strong></p><p>Stacey Matrix’ teki eğilim Chaotic Alan’ dan Obvious Alan’a doğru hareket etmektir ki; problemlerle yaşayabilir ve değer üretebiliriz. Burdaki en önemli şey problemimizi doğru tanimlamaktir. Problemi yanlış tanimlarsak, cevaplarımız da uzun dönemde yanlış olacaktır.</p><h3>Stacey Matrix Alanlari Icin Ornekler</h3><h4>Birinci örneği çamaşır yıkama üzerinden vereceğim.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iobR1YprHMkzJFP6BnBK1Q.jpeg" /></figure><p><strong>Chaotic</strong>: Burdaki alanda kirli çamaşırlar,su, temiz çamaşırlar, deterjan, insanlar, yemekler, içecekler vb herşeyin var olduğunu düşünelim. Burda müşterinin neye ihtiyacı olabilir diye düşünmek gerekir. Yani bir çok değişkenin olduğu yerde müşteri ile empati kurup; Müşterinin temiz çamaşır giymek isteyeceğini bulmak gerekir. Böylece kirli çamaşırları, deterjan ve su ile yikayabilecegimizi kesfedelim. Keşif tamam!</p><p><strong>Edge of Chaos: </strong>Burda Kesifin üzerine çözümün tanımı yapılır. Burda çamaşırları yıkayacak&amp;temizleyecek küçük bir ürün üzerine çalışılır. Burda amaç MVP (Minimum Viable Product) geliştirip müşteriden erken feedback almaktır. Keşif ne kadar iyi olursa olsun, müşterinin para ödeyip kullanacağı bir çözüm değilse, yapılan bütün yatırıma ve zamana yazık olacaktır. Burda amaç çamaşırları yıkayacak ürün için müşterinin para ödeyerek kullanmaya hazır olup olmadığını öğrenmektir.</p><p><strong>Complex</strong>: Burda tanımlanan ürünün geliştirmesi yapılır. Burada Çamaşır makinesi geliştirilir veya çamaşır makinesi için yeni <strong><em>MMP(Minimum Marketable Product)</em></strong> özellikler geliştirilir. Burda müşterinin ne istediği, neye ihtiyaç duyacağı önceden bilinmez. Gelistirmelerden sonra geriye bakarak bu ilişkiler yapılır. Mesela çamaşır makinesine kurutma özelliği geliştirmek, müşterinin işini kolaylastirip kolaylastirmayacagi ancak bu geliştirme tamamlandıktan sonra ilişkilendirilir. Çok sıcak iklimlerde olan müşteriler için kurutma bir dert olmayıp, bu özellik için ekstra ücret ödemek pek mümkün olmayabilir.</p><p><strong>Complicated</strong>: Bu ürün gelistirildikten sonra müşterinin farklı kıyafetler veya kirlilik dozajina göre kıyafetlerini nasıl yıkamaları gerektiği, kıyafetlerin ne kadar temizleneceği, yıkamanın ne kadar süreceği bu alana girmektedir. Burda yıkama üzerine servis verilir diyebiliriz.</p><p><strong>Simple-Obvious:</strong> Burda çamaşırların kirlilik oranları, deterjan ihtiyacı, yıkama sıcaklığı herşey makine üzerinde yapay zeka ile otomatik gerçekleşir. Burda bir seferde en az enerji ile ne kadar çamaşır yıkanabileceği denenebilir. Maksat gereksiz kaynak tüketimini azaltmak olabilir.</p><p>Umarım çamaşır örneğim yerinde bir örnek olmuştur. Eklemek yada katkıda bulunmak istediğiniz bir nokta varsa lütfen bana bildiriniz.</p><h4>İkinci Örneği Basit Matematik İşlemleri üzerinden vereceğim.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aV9N5nCP6r8yUlR_wDkEgQ.jpeg" /></figure><p><strong>Chaotic</strong>: Bu alanda sayılar (1,4,7,132,970), harfler (a,X,g,m, Sel), işaretler (&amp;,#,!,+,-,*) karışık bir biçimde olduklarını varsayalım. Burda amaç müşterinin toplama işlemini kullanmak isteyeceğini bulmak gerekiyor. İhtiyaç tespit edilir.</p><p><strong>Edge of Chaos:</strong> Burda toplama işlemi tanımlanır ve müşterinin bu işlemi kullanacağı müşteriden alınan geri bildirim ile öğrenilir.</p><p><strong>Complex</strong>: Burda müşterinin problemi toplama işlemi üzerindeki x+y= z denklemine indirgenir. Burda x ve y arasındaki ilişki z ye ulaştıktan sonra sağlanabilir.</p><p>Yani; x=3 için y=-1 ise z=2 dir. Burda X ve Y için verdiğimiz değerler için müşteriden geri bildirim alınır. Müşterimizin ekşili sayılarla hiç işi olmadığını öğrenirsek denklemimizin müşteriden aldığımız geri bildirim ile değiştiririz.</p><p><strong>Yeni denklem; x+y= z and x,y,z&gt;0</strong></p><p>Burda gördüğümüz gibi x,y,z herşey olabilir. x=6 için y=2 ise z=8 bulunur. Burda x ve y değerleri işlem yapıldıktan sonra bulunur.</p><p><strong>Complicated</strong>: Complex alandaki denklemi bu alana taşımakla bir bilinmeyeni elimine etmek gerekiyor. Denklem bu alanda x+y=8 indirgenir.</p><p>Burda x ve y arasındaki işlem matemetik expertligi ile çözümlenebilir.</p><p>x’e ve y’e verdiğimiz değerlere göre birden fazla doğru çözüm vardır.</p><p>x=2 ise y=6, x=3 ise y=5 gibi.</p><p><strong>Simple-Obvious:</strong> Burda da bir değişkenin daha gözlemlerle sabite baglanabildigini görmüş sayalım.</p><p>Bu durumda denklem x+2=8 ise bu işlemin tek çözümü vardır ve herzamam doğru olmak zorundadır diyebiliriz.</p><p>Umarım verdiğim örneklemeler yardımcı olmuştur.<br> Başka bir yazıda görüşmek dileğiyle.</p><p>Doğan.</p><h3>References:</h3><ul><li><a href="http://www.gp-training.net/training/communication_skills/consultation/equipoise/complexity/stacey.htm">The Stacey matrix</a></li><li><a href="https://en.wikipedia.org/wiki/Ralph_D._Stacey">Ralph D. Stacey</a></li><li><a href="https://en.wikipedia.org/wiki/Cynefin_framework">Cynefin framework - Wikipedia</a></li></ul><p><a href="https://improuv.com/en">https://improuv.com/en</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ddaf7122cc9c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>