<?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 Selcan Yavuz Kadioglu on Medium]]></title>
        <description><![CDATA[Stories by Selcan Yavuz Kadioglu on Medium]]></description>
        <link>https://medium.com/@yavuzselcan?source=rss-a2434b78f677------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*3ssHEKL7eZRGX_F3gitGWA.png</url>
            <title>Stories by Selcan Yavuz Kadioglu on Medium</title>
            <link>https://medium.com/@yavuzselcan?source=rss-a2434b78f677------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 19:56:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@yavuzselcan/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[Timeboxing is like healthy diet: Eat your time in smaller portion and more often!]]></title>
            <link>https://medium.com/@yavuzselcan/timeboxing-is-like-healthy-diet-eat-your-time-in-smaller-portion-and-more-often-27a9fbbeeccf?source=rss-a2434b78f677------2</link>
            <guid isPermaLink="false">https://medium.com/p/27a9fbbeeccf</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[time-management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Selcan Yavuz Kadioglu]]></dc:creator>
            <pubDate>Thu, 07 Sep 2017 09:48:52 GMT</pubDate>
            <atom:updated>2017-09-14T06:29:06.048Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PJURdfWBahGUxcnEJVyhxQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/vVIwtmqsIuk?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Curtis MacNewton</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Do you have many things to do but not enough time? Me too :). Actually all we have the same amount of time which can be wasted easily. And for using the time effectively, “<strong>timeboxing”</strong> is definitely my favorite technique.</p><p>Although initially I have used it with agile practices at work, currently I use it all my daily life. For example, I edit the drawers in 10 minutes everyday. In the past, I edited them at weekends which could get tiresome hours. Now drawers are always tidy and I don’t get bored, because I know I’ll stop after 10 mins. Another example is the tidying up the toys. With my kids we set the chronometer for 5 mins, and our aim is to put all the toys into the correct boxes before going to bed every night. This is a funny game for them, not a boring task :) Win-win! There are more examples: brushing the teeth in 2 mins with a sand-glass, walking/running everyday for 30 mins, etc..</p><h3>What is timeboxing?</h3><p><a href="https://en.0wikipedia.org/wiki/Timeboxing">Wikipedia </a>defines <strong>timeboxing</strong> as allocating a fixed time period, called a <strong>timebox</strong>, to each planned activity. An <em>activity </em>can be considered as a(n):</p><ul><li>Meeting</li><li>Iteration of a product development</li><li>Course, training</li><li>Houseworks (tidying up, cooking, cleaning.)</li><li>Playing game/sport, …</li></ul><h3>How timeboxing helps for effectiveness?</h3><p>Let’s have a look from the scientific view for the human behaviour to understand how it increases the productivity and efficiency. The main behavioural reasons behind timeboxing are the <a href="http://iisit.org/Vol7/IISITv7p489-494Smith805.pdf">Student Syndrome and Parkinson’s Law</a>.</p><p><strong>Student syndrome</strong></p><p>We tend to delay tasks as much as possible. We often don’t complete a work ahead of schedule even if we are able to. We prefer to postpone the start of time if we have more than enough time to accomplish. Mostly the students start to apply themselves to an assignment at the last possible moment before its deadline.</p><p>I was also suffering from Student syndrome when I was a student — of course I wasn’t aware that it was a <em>syndrome. </em>When I had an assignment with a deadline for 5 days after, I always focused it in the last 1–2 days, especially the last hours. In case I started as soon as I got it, I wasn’t productive. Having chance to postpone the completion causes to loose the focus.</p><p><strong>Parkinson’s law</strong></p><p>“Work expands so as to fill the time allowed”</p><p>According to the Parkinson’s Law, if you are not suffering from the Student’s Syndrome and you can start a task whenever you get it — or earlier, you may not complete it properly until the last minute.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*CqMcoVyPNLbQhhzn-OP_2Q.jpeg" /></figure><p>We can minimize the effects of <em>Student Syndrome</em> and <em>Parkinson Law</em> with limiting the time as shortest as possible in which the productivity is the highest.</p><h4>Four main rules for effective timeboxing:</h4><h4><strong><em>1. Limit the time as short as possible</em></strong></h4><p>You cannot extend the defined time, although you don’t complete the task. You should stop when the time is up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-7p41liTrplwJuQR-EWmMw.jpeg" /><figcaption><a href="http://wallpapercave.com/wp/AYQhetv.jpg">http://wallpapercave.com/wp/AYQhetv.jpg</a></figcaption></figure><h4><strong><em>2. Have a clear goal for each boxed time</em></strong></h4><p>You should focus the aim of the task. It is necessary to set a goal before starting. You treat every timebox like a challenge. This turns a boring task into more of a game, and helps motivate you to work faster. Avoiding multitasking is also important for this rule.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XcsF17_Ns_GhS7eA8hwc4A.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/xqBllPa7XEs?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">asoggetti</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h4><strong><em>3. Review the progress</em></strong></h4><p>Review the progress and improve it.</p><ul><li>Was the defined time enough to complete the task?</li><li>Did you reach the goal?</li></ul><p>If at least one of the answers is NO, you should evaluate the reasons and adapt your definitions for time and/or goal.</p><h4><strong><em>4. Have a sustainable pace</em></strong></h4><p>You should not only walk but run without getting so tired :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YQHwnDrfdMt07gArXWEcgg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/Zp-wTck-3Zw?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Francesco Gallarotti</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h4>Timeboxing in Agile Mindset</h4><blockquote>A <a href="https://www.agilealliance.org/glossary/timebox/">timebox </a>is a previously agreed period of time during which a person or a team works steadily towards completion of some goal.</blockquote><p>Within Agile mindset, timeboxing has great importance since the agile methodology is the best for the projects where the time is the main constraint. <strong>Agility </strong>is the best way of doing work when we have a <strong>fixed time</strong> but <strong>flexible scope</strong>.</p><p><strong>Timeboxing Examples</strong></p><p>The timeboxing for the necessary meetings and activities within Agile Scrum framework can be as following:</p><ul><li>2 weeks for Sprints (If it is suitable for the project 1 week can also be a good option, I don’t suggest more than 2 weeks)</li><li>15 mins for Scrums</li><li>2–4 hours for Sprint Planning (Max 1,5 hrs per week of Sprint)</li><li>2–4 hours for Sprint Review (Max 1 hr per week of Sprint)</li><li>1–2 hour for Retrospective (Max 45 min. per week of Sprint)</li></ul><p>The short timeboxes on agile projects mean that the next deadline is never far away and this helps people focused.</p><p>I liken timeboxing to healthy diet which you eat more often and with small portions which is enough for your health.</p><p>Eat your time in smaller pieces and do it often :)</p><p>Bon Appetite!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=27a9fbbeeccf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Highlights of the ING’s Agile Transformation Journey]]></title>
            <link>https://medium.com/@yavuzselcan/highlights-of-the-ings-agile-transformation-journey-59020f1c5e0a?source=rss-a2434b78f677------2</link>
            <guid isPermaLink="false">https://medium.com/p/59020f1c5e0a</guid>
            <category><![CDATA[people]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[finance]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Selcan Yavuz Kadioglu]]></dc:creator>
            <pubDate>Wed, 22 Feb 2017 07:33:01 GMT</pubDate>
            <atom:updated>2017-02-22T07:33:51.177Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/638/1*fhATppA6yBB_pfq0VaTHwg.jpeg" /><figcaption>New Agile Organization — image credit: ING</figcaption></figure><p>Changing the working style with Agile paradigm maynot be a straight-forward decision for the non-tech organizations. Even it is not easy for software companies to setup an agile culture. It is not easy to change the habits. But, I think “being agile” is not just a choice or decision, but an obligation.</p><p>Although there are many stories of how to be/adopt agile for the software/tech companies, it is nice to have such good examples on different industries, like banking &amp; finance. Let’s be enlightened by the ING’s agility adventure :)</p><p>There are useful points in the<a href="http://www.mckinsey.com/industries/financial-services/our-insights/ings-agile-transformation"> interview with the ING executives (CIO and CTO) by McKinsey</a>. I just want to summarize the highlights of this interview here. First of all it is worth to mention that they inspired with a model used at various technology companies, which they then adapted to their own business. Being agile is not just about changing the IT department or any other function on its own.</p><p>The summary of the transformation process by <strong>Bart Schlatmann is:</strong></p><blockquote>We gave up traditional hierarchy, formal meetings, over-engineering, detailed planning, and excessive “input steering” in exchange for empowered teams, informal networks, and “output steering.”</blockquote><h3>The motivation for the transformation is the customer behavior &amp; expectations not directly the money!</h3><p>The reason is not directly related with the financial results but the customer behavior.</p><blockquote>Customer expectations were being shaped by digital leaders in other industries, not just banking.</blockquote><h3>Main improvements with “Being Agile”</h3><ul><li>Time to market</li><li>Boosted employee engagement</li><li>Increased productivity</li><li>Reduced impediments and handovers</li><li>Improved client experience</li></ul><h3>What is Agility for ING?</h3><blockquote>“Agility is about flexibility and the ability of an organization to rapidly adapt and steer itself in a new direction. <strong>It’s about minimizing handovers and bureaucracy, and empowering people.</strong> The aim is to build stronger, more rounded professionals out of all our people. “</blockquote><h3>4 Pillars of the Organizational Transformation</h3><ol><li>Cross-platform and self organized teams</li><li>Clarity around the new roles and governance</li><li>Continuous delivery in IT and DevOps</li><li>New people model</li></ol><p>As it can be seen, the 3 of 4 important elements are mostly related with the people. It is obvious that the Agile transformation is centered on people and the mindset, not only with some defined process. However the process, frameworks and the best practices are the starting points for the evolution :)</p><blockquote>What matters is how people deal with<strong>knowledge</strong>. A big part of the transformation has been about ensuring there is a good mix between different layers of <strong>knowledge and expertise.</strong></blockquote><p><em>“Being agile is not just about changing the IT department or any other function on its own. The key has been adhering to the “end-to-end principle” and working in multidisciplinary teams, or squads, that comprise a mix of marketing specialists, product and commercial specialists, user-experience designers, data analysts, and IT engineers — all focused on solving the client’s needs and united by a common definition of success.</em></p><p><em>IT and commercial colleagues sit together in the same buildings, divided into squads, constantly testing what they might offer our customers, in an environment where there are no managers controlling the handovers and slowing down collaboration.”</em></p><blockquote>We have spent an enormous amount of energy and leadership time trying to role model the sort of behavior — <strong>ownership, empowerment, customer centricity</strong> — that is appropriate in an agile culture.</blockquote><p>Additionally, in order to have a clear strategy and an agile mindset, they analyzed the best practices and adopted them in an open office with open minded people, evolved into transparent management, re-positioned the employees, measured the results with a neutral outsider, setup more flat organization with squads, and they are still evolving with making mistakes and learn. I am looking forward their progress and the new results :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59020f1c5e0a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I passed the PMI-ACP exam]]></title>
            <link>https://medium.com/@yavuzselcan/how-i-passed-the-pmi-acp-exam-db9d18056814?source=rss-a2434b78f677------2</link>
            <guid isPermaLink="false">https://medium.com/p/db9d18056814</guid>
            <category><![CDATA[certification]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[pmp]]></category>
            <category><![CDATA[agile-project-management]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Selcan Yavuz Kadioglu]]></dc:creator>
            <pubDate>Sun, 15 Jan 2017 21:20:58 GMT</pubDate>
            <atom:updated>2017-09-14T14:28:55.871Z</atom:updated>
            <content:encoded><![CDATA[<p>I passed the PMI-ACP exam on 12th of January 2017 on my first attempt.</p><p>First of all it is worth to mention my agile background and exam preparation studies. Then I will specify some keynotes from the exam.</p><h3>Background</h3><p>I have been working on projects which realize/try to realize Agile software development methodologies since 2006 within large-scaled and multinational teams, as a developer, scrum master, project manager and agile coach. Until 2013 we, the projects I involved, tried to be agile with a transition from traditional software development to agile which was a customized approach. For the last 4 years, I have been working on different projects which have been developing with Scrum and Kanban frameworks by applying the best practices.</p><p>I have also given Introduction to Agile Software Development training internally in my company several times. Nowadays, I am supporting some projects as an agile coach. During the preparation period, I studied various articles, blogs, webinars about agile and the best practices.</p><p>I have also the PMP certification since 2009.</p><h3>PMI-ACP exam preparations</h3><ol><li>On March 2013, I completed the online PMI-ACP exam preparation course from <a href="http://www.mindedgeonline.com/page/course&amp;cid=1013">MindEdge</a> to provide the 21 mandatory hours training requirement as a prerequisite. It was a helpful training to have an overview in a well ordered and classified way.</li><li>I got the <a href="http://www.linkedin.com/in/mikegriffiths">Mike Griffiths</a>’s PMI-ACP exam preparation book one month before. I read it once and solve the practice questions two times. Before the exam day, I solved the online sample exam, with 60 questions, requested in the book. This sample exam was a little bit similar to the real one. I can say that just reading this book may not be enough to pass the exam, you need to internalize :) This book improves the agile mindset which is really necessary to pass the exam. I wish there were more sample situational questions or some case studies in the book.</li><li>I solved the free sample questions in <a href="http://www.izenbridge.com/pmi-acp/free-exam/">iZenbridge</a>.</li></ol><h3>Keynotes from the exam:</h3><ul><li>It wasn’t an easy one :)</li><li>90% of the questions were situational. I have already faced with most of the situations told in the questions, so I had investigated the solutions in the real life many times with discussing experts and reading some articles, blogs, forums, etc. Therefore my Agile experience was the key parameter of passing the exam.</li><li>Similar to PMP exam, the aspect of PMI-ism for Agile should be gathered to pass the exam.</li><li>With having PMP based change management aspect, it is hard to answer correctly most of the question. Understanding the Agile mindset for responding the changes is really important .</li><li>The roles and responsibilities of Scrum Master/Agile Coach/Team Lead, Product Owner, Sponsor, Agile Practitioner should be clearly understand.</li><li>Most of the questions were asking “what should have been done” for a case with an unwanted result, therefore considering preventive actions was necessary.</li><li>As in PMP exam, some questions have more than one correct answers, the best one should be chosen.</li><li>For some questions the best known answer was not available in the choices, therefore I had to decide the nearest correct answer.</li><li>Some questions includes different words for the well-known terms. For the examiners who are not native speakers, this may be a problem (i.e “jeopardy” was used instead of “risk”).</li><li>I completed all the questions in 160 mins and I had only 20 mins for reviewing the marked questions only.</li><li>I did not take any break.</li></ul><p>I can try to help for details, if you contact me.</p><p>Wish to success for the ones who will attend the exam.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=db9d18056814" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>