<?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 Grzegorz Bartman on Medium]]></title>
        <description><![CDATA[Stories by Grzegorz Bartman on Medium]]></description>
        <link>https://medium.com/@grzegorz.bartman?source=rss-22c0146477d1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*LAzpvKC2xwX3pjpK2FousA.jpeg</url>
            <title>Stories by Grzegorz Bartman on Medium</title>
            <link>https://medium.com/@grzegorz.bartman?source=rss-22c0146477d1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 10:38:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@grzegorz.bartman/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[Effective software delivery? Remote SCRUM team]]></title>
            <link>https://medium.com/@grzegorz.bartman/effective-software-delivery-remote-scrum-team-droptica-com-6e491c8db75?source=rss-22c0146477d1------2</link>
            <guid isPermaLink="false">https://medium.com/p/6e491c8db75</guid>
            <category><![CDATA[scum]]></category>
            <category><![CDATA[php]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Grzegorz Bartman]]></dc:creator>
            <pubDate>Fri, 15 Jun 2018 12:43:17 GMT</pubDate>
            <atom:updated>2018-06-15T12:47:29.997Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rlz1vfFT3i7KMRGe38K3EQ.png" /></figure><p>The deadline is today. A remote development team have worked for several weeks on your software. You obtain the long-awaited access to the system. You check it and you are not satisfied with the achieved results.<br> All that was needed to avoid this problem is a team with experience in technology and working using SCRUM.</p><h3>What is SCRUM</h3><p>Wikipedia defines SCRUM as an agile framework for managing work. It is an approach used in many companies to develop software. Full definition can be found here <a href="https://en.wikipedia.org/wiki/Scrum">https://en.wikipedia.org/wiki/Scrum</a></p><h3>SCRUM solves most of the problems arising during software development</h3><p>This is my opinion and many people agree with it. I have been developing commercial projects since 2008. I started as a programmer. Currently, I am supervising high-level projects.</p><p>Introduction of the SCRUM method in Droptica solved most of the problems. Which ones exactly?<br> Here are the most important of them:</p><ul><li>The client was not regularly informed about the progress of works — the client was not satisfied. Sprints, review, backlog refinement — all this compels a constant contact with the client</li><li>The tasks were not thought through before starting them, therefore they took a long time to finish — the client was not satisfied. Backlog refinement and planning — these events ensure that the team has to really ponder on completing each task.</li></ul><h3>SCRUM saves money</h3><p>You can ask yourself: how is that possible if you do not know the exact duration and cost of the project at its beginning? The answer can be found in the previous paragraph:</p><ul><li>Regular meetings with the client (Product Owner) force them to think about which tasks are actually needed and which can be rejected.</li><li>Analysis of tasks by the team together with the PO, often allows to come up with better ways to implement or reject them.</li></ul><p>SCRUM is often called the art of maximising work not done. You maximise the rejection of the tasks that are unnecessary from the point of view of your business. You do only the things that bring particular value to the system. Everything else goes straight to the waste bin.</p><h3>Why so many meetings?</h3><p>Planning the sprint, daily scrum, retro, review, backlog refinement. The list of meetings is long. There is no doubt that they take time. The client often expects to pay for programming, not for conversations and meetings.</p><p>I used to think the same way. However, after a test implementation of SCRUM in one of the projects, I have changed my mind. Now I want to develop all our projects — for clients and internal — using SCRUM. I see that it saves great amount of time and money. The same can be confirmed by the clients with whom we now work using SCRUM, while we did not have a specific way of working before.</p><p>Abraham Lincoln once said, “If I had eight hours to chop down a tree, I’d spend six sharpening my ax.”</p><p>The meetings guarantee a good rethinking of tasks, sticking to a common direction and pursuing the same business goals. It is definitely worth it.</p><h3>How long will it take and how much will it cost?</h3><p>Every client asks this question at the beginning. It is not easy to answer it. The pace of each programmer is different, there are different working conditions, holidays, leaves, the requirements change (from the client, legal requirements, etc.). A longer project also means a frequently changing specification. Such changes change the cost and time.</p><p>Story Points is a solution to the problem. It is a very good tool for estimating the number of tasks that can be performed in a sprint (stage). After just 2–4 sprints you can see the team’s average pace. After such a time the team knows the project well, knows the client well and plans for the future. The team can very accurately estimate the tasks waiting in the Backlog. Product Owner, knowing the pace of the team can count the number of sprints and the total cost.</p><p>Compared to creating a detailed specification at the beginning of the project, such an approach gives better estimation results.</p><h3>SCRUM is not enough if the team does not have the experience with the technology</h3><p>If the team will work using SCRUM, but will not be familiar with the technology, it will not be able to provide good quality software within a reasonable time. Only the combination of SCRUM and the team experienced in using the given technology ensures significant effects. The customer will definitely be satisfied with such a combination.</p><h3>Why a remote team is better?</h3><p>What is the difference between a remote team and a local team? Actually — just their location. If you can have a local team, it is worth choosing this option. It will be more convenient.</p><p>However, in today’s IT market it is difficult to complete a team of 2, 3 or more specialists in a short time for a larger project. That is why you should think about a remote SCRUM team. A team that already has the experience in working with a remote client. By expanding the options to the whole world, you have more choices.</p><h3>How can I monitor what a team thousands of miles away is doing?</h3><p>SCRUM has a way to do it: Sprint Burndown Chart. It is a chart that is updated daily. It shows the regular peace of project development. It shows whether the team implements the sprint plan. It is the best tool for monitoring the progress of works. Using Waterfall, you usually find out about delays at the end of a larger stage. With SCRUM, the client can check every day what progress the team has made. They can be sure that the team works and delivers consecutive parts of the software.</p><h3>How to communicate with the team?</h3><p>At Droptica we have 3 ways to do that: — Jira — it is the main communication system; here we have all User Stories and tasks — Slack — for short text questions, used practically every day</p><p>- Skype/Google Hangouts/Zoom — for video calls with screen sharing</p><p><em>Originally published at </em><a href="https://www.droptica.com/blog/effective-software-delivery-remote-scrum-team/"><em>https://www.droptica.com/blog/effective-software-delivery-remote-scrum-team/</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6e491c8db75" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a big website? Here are ten reasons why you should be using Drupal | droptica.com]]></title>
            <link>https://medium.com/@grzegorz.bartman/building-a-big-website-here-are-ten-reasons-why-you-should-be-using-drupal-droptica-com-5fccdaa62faa?source=rss-22c0146477d1------2</link>
            <guid isPermaLink="false">https://medium.com/p/5fccdaa62faa</guid>
            <category><![CDATA[website]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[cms]]></category>
            <category><![CDATA[drupal]]></category>
            <category><![CDATA[php]]></category>
            <dc:creator><![CDATA[Grzegorz Bartman]]></dc:creator>
            <pubDate>Mon, 09 Apr 2018 07:02:08 GMT</pubDate>
            <atom:updated>2018-04-09T07:02:08.687Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KP_7EbS7KwJlvudo5tIkww.jpeg" /></figure><p>When you’re building an advanced website, you can choose from among many technologies. Usually, the first choice is the programming language (PHP, Python, Java, ASP.NET, etc.) and then we decide whether we should code everything from scratch or use a framework to do all the heavy lifting. There is also a third choice, a more comprehensive solution –so-called CMF systems, which stands for content management framework. <strong>Drupal 8 is one of these systems</strong>. In this article, I will tell you why it’s worth it to choose Drupal as the basis for any large and advanced website.</p><p>By <strong>large and advanced</strong>, I mean one that is changed frequently. Content changes are carried out by at least one editor, supported by at least one developer (along with a QA tester and a sysadmin), who’s responsible for continuous development of the website, adding new functionalities, fixing the emerging bugs and so on.</p><p><strong>Some</strong> <strong>examples of large and advanced websites:</strong></p><ul><li>A website of a medium or a <strong>large production or service company</strong>, offering hundreds or thousands of various products or services. The website’s content should be updated on a continuous basis, including information regarding products, services, promotions, availability and so on. The website is one of the key sales tools and is managed by the company’s marketing department.</li><li>An <strong>informational website</strong>, for example, run by a <strong>paper or magazine</strong>. The new content for the website, which is published on a daily basis, is created by a team of editors. The content creation process has a number of steps (draft, proofreading, approval, publication on a given date, etc.)</li><li>An <strong>internal web application for managing processes </strong>in the company, such as a CRM system, a system supporting the activities of regional sales representatives or a number of company’s branches, intranet system. A system with a variety of data types. The application is available only to users who are logged in. Users create large amounts of data every day.</li><li>A <strong>website of a school or university</strong> publishing information from lecturers and teachers for students and employees. There are many types of information divided into categories and displayed in many ways.</li><li>A <strong>system feeding content to other systems</strong> — an API with content for other websites and mobile application. There is a need to manage many different types of data and quickly providing them to other external systems.</li></ul><p>​</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*XtSYL6pO6C6BybGe.png" /></figure><p><em>(Source: </em><a href="https://w3techs.com/technologies/market/content_management"><em>https://w3techs.com/technologies/market/content_management</em></a><em>)</em></p><p>The opinions about Drupal found in many articles only confirm the data from the chart above: Drupal is chosen for building large websites more often than WordPress.</p><h3>Why should you use Drupal 8 for building your website?</h3><p>Because:</p><ol><li>It’s a<strong> tried and proven system</strong> used by large international companies and organisations. Some examples of Drupal users include:</li><li>Drupal 8 is Open Source. <strong>It’s completely free</strong>. What is also free are thousands of modules available at <a href="https://www.droptica.com/blog/building-big-website-here-are-ten-reasons-why-you-should-be-using-drupal/www.drupal.org">www.drupal.org</a>. You don’t have to cover any licensing costs like you would have to do with commercial software.</li><li><strong>Thousands of companies</strong> around the world work hard on adapting Drupal to customers’ needs (installation, setup, creating templates and modules, hosting). By choosing Drupal, <strong>you are not limiting yourself to cooperating with just one company</strong> for many years (usually a website is built for 3–6 years).</li><li>As a project, Drupal is developed by a <strong>community spanning the entire world</strong>. Over 100,000 users actively develop Drupal core and its modules. 100,000 developers are definitely more than 10 or even 100 coders working on a given commercial solution. What is more, over <strong>1 million</strong> users are registered with <a href="https://www.droptica.com/blog/building-big-website-here-are-ten-reasons-why-you-should-be-using-drupal/www.drupal.org">www.drupal.org</a>, helping the development by making change requests for the core and the modules.</li><li><strong>From the technological standpoint</strong>, Drupal 8 was developed in PHP (it uses PHP 7, which is blazing fast), uses Symfony Framework components (believed to be<strong> the best solution</strong> for developing complex applications in the PHP ecosystem) and Twig template engine, which streamlines front-end works and improves security.</li><li><strong>Drupal Security Team</strong> is a special group of people who take care of the security of both Drupal and its modules. The team <strong>constantly checks Drupal in order to find any and all bugs</strong>. In the case of a security hole, the team quickly publishes bugfixes and updates. Notifications announcing new updates are visible in the website’s administration panel, they can also be received via e-mail. Every Drupal-based website automatically checks whether they have the most current version of Drupal and all the modules. If a new version is released, the administrator gets informed about it at once.</li><li><strong>New versions</strong> of Drupal 8 are released every six months. Drupal 8.0 was released at the end of 2015. Currently, we are in version 8.5. Every new version introduces new bugfixes, as well as new functionalities and modules available in Drupal core. The Drupal development team aims for adding new functions to expand its usability and capabilities. By choosing Drupal 8 you ensure getting new functions for your website — completely free of charge!</li><li><strong>Webservices</strong> — You can use Drupal to build APIs and<strong> communicate with other systems</strong>. Thanks to this, you can easily fit your new solution into existing systems in the company. You can also use Drupal as a backend for so-called headless systems — Drupal will take care of feeding all the data and content, while they will be displayed by other systems.</li><li><strong>Modules and functions in Drupal core</strong> — there are many of them, but the most important of them are:</li></ol><ul><li>creating any number of <strong>data</strong> <strong>types</strong> with any structures, along with relations between various data types</li><li>extensive <strong>categorisation</strong> of content (categories, tags, tree structure, many categories for one type of content),</li><li><strong>version</strong> <strong>control</strong> — tracking changes in the content,</li><li>activity <strong>logs</strong> in the system, user activity history (who logged in and where, when was the content added, etc.),</li><li>extensive <strong>user</strong> <strong>management</strong>, roles and permissions,</li><li>support for many <strong>languages</strong>,</li><li><strong>multisite</strong>: the ability to build many copies of a single website on a single installation, e.g. for a given country, or separate versions of the website for each product or service,</li><li><strong>media</strong> management (photos, videos),</li><li>convenient content management: <strong>CKeditor</strong> — a WYSIWYG editor, content moderation, quick edition and others,</li><li>views and fields — flexible data structures and displaying,</li><li><strong>mobile</strong>-friendly system, responsive images,</li><li><strong>migrate</strong> API: the core includes a mechanism allowing for convenient content and data export to Drupal,</li><li>he capability to block users based on IP, e-mail, hostname.</li></ul><p><strong>10. Additional modules</strong>. There are thousands of them and you can download them for free at <a href="https://www.droptica.com/blog/building-big-website-here-are-ten-reasons-why-you-should-be-using-drupal/www.drupal.org">https://www.drupal.org/</a>. The most interesting and noteworthy modules are:</p><ul><li><strong>Paragraphs</strong> — enables flexible content creation. At first, the developer creates various types of recurring elements. Then, editors have the option to use these elements to build their subpages. The subpages can have any number of these elements arranged in any way. You can read more <a href="https://www.droptica.com/blog/flexible-and-easy-content-creation-drupal-paragraphs-module/">in our blog post</a>.</li><li><strong>Metatag</strong> — enables managing meta tags for all your SEO needs. You can create tags separately for each subpage or define templates, based on which Drupal will automatically create tags for new subpages.</li><li><strong>Google</strong> <strong>Analytics</strong>: integrate your website with Google Analytics, you can go for simple or complex integration in order to learn more about your users.</li><li><strong>Pathauto</strong>: enables automatic creation of URL aliases based on a given template (e.g. /news/category(title)).</li><li><strong>Webform</strong>: enables creating forms using Drupal administration panel. Thanks to that module, you can create a form for gathering your users’ data or a survey within minutes.</li><li><strong>SitemapXML</strong>: creates an XML map with your website’s structure, required by Google and other search engines.</li><li><strong>Captcha</strong>: add captcha tests to any form in order to protect your website from spam.</li><li><strong>Panels</strong>: enables the creation of new subpages using the drag&amp;drop methodology. You can define a new page, decide its layout (e.g. 3 columns) and add content to each of the elements.</li><li><strong>SMTP</strong>: enables sending e-mails from Drupal using external servers. You can also set it up to send e-mails with HTML content. It’s very useful when you send a lot of e-mails to your users and you want for example to track their statistics using external services.</li><li><strong>Search API + Solr</strong>: enables you to connect Apache Solr to Drupal. This significantly speeds up searching your website, especially if you have a lot of content.</li><li><strong>Scheduler</strong>: enables to you schedule publication of your content to a given date.</li><li><strong>AddToAny</strong> share buttons: allows for quickly adding icons to share your content on social media.</li><li><strong>Commerce</strong>: a module that is used to build online stores.</li><li><strong>MailChimp</strong> or Freshmail: integration with popular newsletter systems.</li><li><strong>Focal point</strong>: cropping photographs before publication.</li></ul><p>You can find the<strong> full list of modules </strong>at <a href="https://www.drupal.org/project/project_module">https://www.drupal.org/project/project_module</a>. Above, I listed my take on the ten most important reasons for using Drupal. There are, however, many more benefits to using that framework. The best way to discover them all is to try it yourself. In this case, it would be also best to install additional modules to learn the full extent of its capabilities.</p><p>Soon, we are going to release a distribution (consisting of Drupal core and additional modules) including much more functionalities than the bare core and, on top of that, a <strong>very pretty user interface</strong>. We’ll share more details on our blog and at <a href="http://www.droopler.com/">www.droopler.com</a></p><p><strong>Already a Drupal user?</strong> Tell us in the comments what are the most important reasons and why do you consider it worthwhile to use Drupal!</p><p>Sign up for out newsletter and get e-mails of stories like this.</p><p><em>Originally published at </em><a href="https://www.droptica.com/blog/building-big-website-here-are-ten-reasons-why-you-should-be-using-drupal/"><em>https://www.droptica.com/blog/building-big-website-here-are-ten-reasons-why-you-should-be-using-drupal/</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5fccdaa62faa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Jak prezentować sponsorów podczas konferencji]]></title>
            <link>https://medium.com/@grzegorz.bartman/jak-prezentowa%C4%87-sponsor%C3%B3w-podczas-konferencji-32c3d3bb77fa?source=rss-22c0146477d1------2</link>
            <guid isPermaLink="false">https://medium.com/p/32c3d3bb77fa</guid>
            <category><![CDATA[polish]]></category>
            <category><![CDATA[po-polsku]]></category>
            <category><![CDATA[it]]></category>
            <category><![CDATA[sponsoring]]></category>
            <category><![CDATA[konferencja]]></category>
            <dc:creator><![CDATA[Grzegorz Bartman]]></dc:creator>
            <pubDate>Sun, 11 Jun 2017 13:57:44 GMT</pubDate>
            <atom:updated>2017-06-11T13:57:44.672Z</atom:updated>
            <content:encoded><![CDATA[<p>Od prawie 10 lat uczestniczę w różnych konferencjach, głównie związanych z branżą IT. Od 2012 roku jestem jednym z współorganizatorów konferencji DrupalCamp Wroclaw. Przez ten czas zebrałem trochę wiedzy odnośnie organizacji konferencji. W tym krótkim poście chciałbym pokazać sposoby prezentacji sponsorów w czasie konferencji. Może się to przydać w momencie negocjacji z potencjalnym sponsorem. Jeśli przygotujemy dużo różnych sposobów prezentacji firm to one chętniej zostaną sponsorami konferencji.</p><p>Sposoby na prezentowanie sponsorów podczas konferencji (na DruapalCamp Wrocław i podpatrzone na innych konferencjach):<br>- bannery sponsorów na scenie, warto tak je ustawić aby były w kadrze kamery (jeśli wykłady są rejestrowane kamerą), <br>- bannery sponsorów przed wejściem do sali konferencyjnej, <br>- nazywać sale konferencyjne nazwą sponsora, tą nazwą posługiwać się na programie konferencji i zapowiedziach wykładów (np. Teraz wykład o WordPress w sali Droptica),<br>- slajd ze sponsorami na prezentacji otwarcia,<br>- jeśli w miejscu konferencji na korytarzach są ekrany to można tam wyświetlać na przemian slajd z programem i slajd ze sponsorami,<br>- social media: piszemy o sponsorach przed konferencją, w trakcie i po konferencji,<br>- loga sponsorów na gadżetach, np loga na torbach i ulotkach z programem. Nie dawaliśmy nigdy sponsorów na koszulkach aby ludzie jednak chętniej je nosili po konferencji,<br>- ulotka sponsora dodawana do pakietu startowego dla każdego uczestnika konferencji,<br>- stoiska sponsorskie obok sal konferencyjnych. Warto zadbać aby było coś ciekawego na stoisku. Z ciekawszych stoisk widziałem takie z rowerkiem stacjonarnym, po przejechaniu X kilometrów można było otrzymać specjalny gadżet od sponsora (nie pamiętam już co to było),<br>- wykłady prowadzone przez sponsorów — ważne aby to nie była prezentacja “jaka firma jest fajna i super” tylko aby przekazać wiedzę przydatną uczestnikom konferencji. Widziałem kilka takich prezentacji, gdzie była tylko mowa o firmie. Takie prezentacje były bardzo źle oceniane przez uczestników.</p><p>Jeśli ktoś zna inne ciekawe sposoby prezentacji sponsorów to chętnie o nich przeczytam w komentarzach. Już planujemy DrupalCamp 2018 i każdy pomysł na usprawnienie konferencji się nam przyda.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=32c3d3bb77fa" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>