<?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 Lena Wimmer on Medium]]></title>
        <description><![CDATA[Stories by Lena Wimmer on Medium]]></description>
        <link>https://medium.com/@lenawimmer_59268?source=rss-b269a15ec89a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Sum5QvE2LQXeRswx</url>
            <title>Stories by Lena Wimmer on Medium</title>
            <link>https://medium.com/@lenawimmer_59268?source=rss-b269a15ec89a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 21:59:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@lenawimmer_59268/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[Perfect fit: The right project management tool for your team]]></title>
            <link>https://medium.com/stackfield-stories/perfect-fit-the-right-project-management-tool-for-your-team-13f49b87cb98?source=rss-b269a15ec89a------2</link>
            <guid isPermaLink="false">https://medium.com/p/13f49b87cb98</guid>
            <category><![CDATA[project-manager]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[task-management]]></category>
            <category><![CDATA[project-management-tool]]></category>
            <category><![CDATA[collaboration-tools]]></category>
            <dc:creator><![CDATA[Lena Wimmer]]></dc:creator>
            <pubDate>Tue, 13 Jul 2021 09:38:41 GMT</pubDate>
            <atom:updated>2021-07-13T09:38:41.940Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*h5yrbFv3BEObdZLFQ6PC5Q.png" /></figure><p>The way how teams carry out their projects varies from company to company, depending on the type and scope of the project and the <a href="https://www.stackfield.com/blog/project-management-methods-88">projectmanagement method</a> used. However, what all those companies have in common is that they are looking for the right tools to help them improve their <a href="https://www.stackfield.com/project-management">project management</a>.</p><p>The market is full of solutions, which is why we have already <a href="https://www.stackfield.com/blog/project-managementsoftware-compared-75">compared the most popular providers of project management software</a>. However, this article aims to show you what you need to pay attention to when choosing a suitable project management tool.</p><h3>Why do you need project management tools after all?</h3><p>In larger organizations a digital project management tool is already common practice. Cloud solutions are state of the art. In smaller companies, however, things are still different. Their projects are usually smaller and less complex. After all, conventional analog approaches still do the job, and new tools seem to only result in extra costs. This often raises the question: Do I really need a project management tool?</p><p>Basically it is true — the more extensive a project is and the more project members are involved, the more difficult it becomes to carry out the project without digital tools. Processes then become confusing and any news is quickly lost. If your team isn’t able to store crucial information in one central place, employees spend more time gathering it from different sources or miss it altogether. In fact, <a href="https://www.pmi.org/-/media/pmi/documents/public/pdf/learning/thought-leadership/pulse/pulse-of-the-profession-2016.pdf?v=e14f4e4b-6dba-41f5-a7bd-12bc71921a4c">projects fail in 30% of the cases due to a lack of communication</a> and, as a result, due to collaboration problems.</p><p>This is exactly where a project management tool comes in. It is intended to map the progress of the project clearly for all members, identify bottlenecks, document the assignment of tasks and facilitate project communication. Is it often hard to get a clear picture of how busy the employees are and to understand who is in charge of what? Does your team have a hard time keeping track of deadlines and important milestones? This is where project management tools come in!</p><h3>What project management tools will you need?</h3><h3>Goal setting and knowledge base with wiki pages</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*yQVG5gtrt6I5nOAK.jpg" /></figure><p>The cornerstone of a successful project is good preparation and planning. Key data about the project and goals must be accessible to all team members, as it is important to keep them in mind throughout the entire project in order to stay on track. Teams that lose sight of their goals, for example, tend to jeopardize the project by creating scope creeps, i.e. the uncontrolled addition of new requirements.</p><p>There is a very simple solution for this: Wiki pages where the project manager can summarize all requirements and goals and then share them with the team.</p><p>Moreover, these pages are perfect for storing any kind of information that people frequently need, such as price lists, standard texts or guidelines.</p><h3>Task assignment with task cards and subtasks</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*1Ad7c9bRHNQpzNkP.jpg" /></figure><p>The set of tasks that must be completed by the end of the project is not a one-man job. Projects require team work, because each team member has his or her own area of responsibility and is in charge of doing a certain amount of work.</p><p>A project management tool should make it easy to assign and schedule tasks so that everyone knows what tasks are assigned to whom and when the person assigned needs to do them.</p><p>This is usually done by creating task cards that specify the exact work instructions, date them and assign them to the employee(s) responsible. Good project management tools also allow you to add subtasks to the task cards, which in turn can be assigned to individual team members. This gives the team a better overview of the overall process.</p><p><a href="https://www.stackfield.com/blog/taskmanagement-101-111">Have a look at our task management 101, to learn more about the different types of tasks and how to manageme them.</a></p><h3>Time management using a Gantt chart</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*cVLj-wtSeOdkBoWS.jpg" /></figure><p>Of course, it is only one part of a well-developed project plan to simply record requirements. In addition, the chronological framework is very important, because first and foremost the team wants to complete the project on time.</p><p>A Gantt chart shows exactly where the project should be at a certain point and where it actually is. This makes it easy to check whether the team is on track or whether it is necessary to adjust the plan. To do so, tasks need to be put in the right order, taking into account their duration and dependency on other tasks. If a task is delayed, it can be assumed that any dependent tasks will follow suit.</p><h3>Time tracking</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*-aX7Q8KfW4UcD5lT.jpg" /></figure><p>The more accurately you estimate the duration of tasks, the more accurately you can create the Gantt chart. It is helpful to know how much time certain tasks or deadlines will require, so you can constantly optimize and adjust the project. Also, as soon as you know the time required for certain types of tasks and where delays may occur you will have an easy job planning future projects.</p><p>A project management tool that also has a task-specific time tracking function as well as a project-related time evaluation function would serve this purpose.</p><h3>Task views and workflows</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*OhZrQgEBhSmYaNSl.jpg" /></figure><p>While the Gantt chart provides information on how the whole project progresses, task status provides accurate information on the current processing status of each task. A project management tool should at least have an approval workflow to support both the delegation of tasks and the review of work results.</p><p>Even for projects of moderate complexity, it is often no longer sufficient to simply use a to-do list to guarantee transparency. However, the Kanban Board is a traditional and popular tool that visualizes the progress of individual tasks in the best possible way making it easy for the project team to move task via various status columns from the “to-do pile” to the “completed pile” — one after the other.</p><p><a href="https://www.stackfield.com/blog/the-5-best-kanban-board-tools-80">Find out more about the way Kanban Boards work and have a look at our comparison of 5 popular Kanban-Tools.</a></p><h3>Collaborative file management</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*vKANxT74BM7-LtvZ.jpg" /></figure><p>Word, Excel, PowerPoint, PDFs, jpg images…and many of them. This is the daily business of every project team member. Because there are many files involved, a proper file management is the least a project team should invest in. After all, only exchanging files via e-mail makes things very confusing.</p><p>Project management tools take file collaboration to a completely different level: They help to store files neatly organized and accessible to everyone, they link them to related task cards, and they help to collaboratively work on them with specific markers and comments. A project management tool serves the purpose if all files and information related to a particular task are available centrally and if changes to files can be easily tracked (versioning of files and documents).</p><h3>Smooth communication</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*ItruaP7mh3tuY0T6.jpg" /></figure><p>Often stressed, but rarely really noticed: a project fails with poor communication. This is important, so do not spoil the ship for a ha’porth of tar.</p><p>Communication solutions such as Slack, which enable real-time exchange regardless of location, are now commonplace in every company. A good approach, but still not enough for project management. Communication not only has to be simple, but also topic specific in order to function smoothly. That’s why project management tools should have a communication component that maintains coherence. You should be able to comment on all elements, such as tasks, files, deadlines, etc., individually; with a team- or project-specific news stream, team members are immediately up to date on new comments and actions. Mentions, accurate annotations and links help to communicate systematically.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*zhmJoXXZM8e4i-OU.png" /></figure><p>Within teams, where there is a lot of remote or external collaboration, videoconferencing and screen sharing is essential, because some things simply need to be discussed in more detail.</p><h3>Project tracking and multi-project management tools</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*4t7abhJqtmBZDGtR.gif" /></figure><p>Every day that you move back the end date of your project results in additional costs. Add to this, it is not uncommon for several projects to run simultaneously, which is why the status of individual projects should be available even without precise data analysis and observation.</p><p>Individual project overviews, that evaluate progress using diagrams, and cross-organizational project portfolios providing the most important key data and quick access to the individual projects are a way better approach. If a project is going off track, the status within the overview will inform you immediately so you can react.</p><h3>What else to look out for in project management tools</h3><h3>User-friendliness</h3><p>The best tool set is worthless if employees struggle to cope with it. In concrete terms, this means that user-friendliness is no less important than the variety of functions. Project management tools should be clear and intuitive, and click paths should be kept as short as possible. Otherwise, the tool would problably rather harm productivity than optimize it.</p><p>Many project management tools contain far more functions than those mentioned above. For teams that do not use all of them, it would be worth checking whether individual functions can be disabled. With this gimmick, the tool is only as complex as the team’s work ultimately requires.</p><p>Don’t buy a tool without having tested it extensively beforehand and bring employees from different areas on board. Does everyone get along with the tool? Wonderful!</p><h3>Privacy</h3><p>First and foremost, European companies must be able to guarantee compliance with the GDPR and the protection of sensitive internal company information. This also requires a careful examination of the project management tools used with regard to their security standards.</p><p>In particular, you should find out more about the encryption of data as well as about the company and server location. Can sensitive data be protected by client-side end-to-end encryption rather than by mere SSL transport encryption? Is the provider GDPR compliant and truly not affected by the US Cloud Act? Is the choice of subcontractors limited to the European region? Can you answer these questions with YES? Wonderful!</p><h3>Mobile Apps</h3><p>Location-independent working also requires the ability to work with mobile devices without complications, but with comfort and security.</p><p>Does the provider provide you with Android, iOS and desktop applications? Can mobile and desktop notifications be restricted in terms of content for security reasons? Wonderful!</p><h3>Project management tool: On-Prem or SaaS?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*tWnFLuH0vJCQ4Fmm.png" /></figure><p>For companies with particularly high demands on data protection — e.g. laywers or innovators who need to keep new developments secret from the competition — on-premise is quite often first choice. In this case, the company hosts the project management tool on its own servers. However, the downside is that self-hosted project management tools are very costly and time-consuming for the company and updates are not or not instantly available.</p><p>The good news is, once you select a tool that uses a dedicated encryption method, a cloud solution is in no way inferior to an on-prem solution. A SaaS product has the following advantages:</p><ul><li><strong>Location-independent access</strong>: The product can be used via the browser, so all that is required is an end device and a stable internet connection.</li><li><strong>Lower costs and less effort</strong>: The provider takes care of hosting, maintenance and updates.</li><li><strong>High IT security</strong>: Cloud solutions offer greater protection against data loss, as the provider stores the data in high-security data centers with security backups.</li><li><strong>Immediate availability</strong>: Cloud solutions are immediately ready for use because they do not have to be installed first.</li><li><strong>Flexibility</strong>: Cloud customers enjoy cost flexibility. They can upgrade or downgrade depending on their function and license requirements.</li><li><strong>Best support</strong>: Cloud users can benefit from expert know-how — provided by the providers themselves.</li></ul><h3>Isolated solutions, integration tool or all-rounder?</h3><p>The demands that teams place on their project management tools vary greatly. Many providers therefore specialize on a specific functional area and try to position themselves as the optimal solution for this small business area. Trello, for example, focuses solely on task management by means of a Kanban Board.</p><p>You can find such <strong>isolated solutions</strong> in many companies. At the same time, you will find some collaboration problems in these cases. If each department decides to use its own project management tool, employees from different departments will find it difficult to work together. In addition, the use of several tools in a team inhibits productivity, because this approach forces the user to constantly switch between various tools that he or she must initially become familiar with.</p><p><strong>Integration tools</strong> such as Microsoft Teams try to solve the problem through integrations. Users can still purchase different tools separately and integrate them into MS Teams using an interface. Unfortunately, this is not a good solution either, because integrations usually represent only a small functional area of the individual tool and they continue to operate separately from the systems of the integration platform. They are merely inserted, but not linked to the functions of the other project management tools. As a result, users have to copy elements, link them manually and always keep an overview of the various places where users store information. Not surprisingly, they lose sight of the bigger picture.</p><p>So there are many reasons for a company to turn to an <strong>all-rounder</strong> when looking for a suitable project management tool. Here, all information remains in one central location and the functions are linked to each other, which keeps correlations of any information and actions intact. Stackfield is a holistic project management tool that combines the really important project management, collaboration and communication functions, but with the option of disabling individual functions to keep the solution as lean as possible for departments with fewer functional requirements.</p><h3>Find the right project management tool step by step</h3><p><strong>Step 1: Take a digital team on board</strong>. Who knows the processes in the individual business areas best?</p><p><strong>Step 2: Analyze exactly how you are currently running projects</strong>. Where do you see room for improvement? How could a digital project management tool be used to improve processes? What tools should the solution at least include?</p><ul><li><strong>Visualization</strong>: list views, Kanban Boards, Gantt Charts</li><li><strong>Collaboration</strong>: workflow management, file management, document management</li><li><strong>Communication</strong>: real-time chats, screen sharing, (group) calls</li><li><strong>Knowledge Management</strong>: Wiki Pages</li><li><strong>Multi project management</strong>: Project portfolios</li><li><strong>Project tracking</strong>: detailed project overviews, Gantt Charts, time tracking</li><li><strong>Compliance</strong>: detailed role and right systems and advanced security settings</li><li><strong>Data protection</strong>: server location, DPA and encryption mechanisms</li></ul><p><strong>Step 3: Check the technical requirements</strong>. What is the own IT infrastructure like? Should you opt for an on-premise or a cloud solution?</p><p><strong>Step 4: Compare providers</strong>. Which provider offers the project management tools needed and meets all requirements regarding GDPR and IT security?</p><p><strong>Step 5: Test the software together with your digital team</strong>. To which extent can you visualize the processes in the respective areas? Is the platform intuitive or does it require extensive coaching? How big is the effort to make this software available to the company? Cloud solutions are usually ready for immediate use. With On-Prem, it would be an advantage if the provider offered support.</p><p><strong>Step 6: Make the solution ready for use</strong>: In the best case, the administrator makes all the important settings before making the tool available to employees. That way, there will be no confusion later.</p><p><strong>Step 7: Ensure acceptance</strong>: The unfamiliar can also be frightening. Short training sessions, information sheets and basic assistance prevent this. Employees should have a person to contact if questions or uncertainties arise.</p><h3>What makes Stackfield a great project management tool?</h3><h3>Security</h3><p>Stackfield is a German tool that exclusively relies on German server locations and subcontractors from the European region. Stackfield is therefore under German jurisdiction and must legally guarantee GDPR and BDSG conformity. Furthermore, users benefit from client-side end-to-end encryption, two-factor authentication (optional or mandatory), ISO 27001-certified data centers, the highest SSL standards and other <a href="https://www.stackfield.com/security">security measures</a>.</p><h3>Holistic feature suite</h3><p>Stackfield combines <a href="https://www.stackfield.com/tour">the essential functions</a> needed in a project management team and links them together to maintain coherence and overview of all internal processes. This includes various functions for task and workflow visualization (lists, Kanban Boards, Gantt Charts), collaborative file and document management, wiki pages, global reporting functions and all common communication channels (room-independent private and group chats, room-specific team chats, audio and video telephony with screen sharing and conferencing).</p><h3>Ease of use and support</h3><p>The platform should remain intuitive, which is why every new function is carefully checked for its usability. During development, the focus is on short click paths and a clear and intuitive design.</p><p>Anyone who needs help or has questions can reach the <a href="https://www.stackfield.com/contact">support</a> team by e-mail, live chat or phone, or else take a look at the <a href="https://www.stackfield.com/help">Learning Center</a>, where individual functions are described in detail. Help is offered in German and English in all cases.</p><h3>Check up on this when considering project management tools from other providers</h3><p>So far, US providers of project management tools have remained the undisputed leaders in Europe as well.</p><p>Asana, Teams or Trello? American providers are popular but are they safe? This is a question that companies all over Europe are concerned with, as they are obliged to guarantee data protection compliance in accordance with the strict requirements of the GDPR. Until July 2020, companies could still refer to the EU-US Privacy Shield Agreement, that was valid until then, when using Privacy Shield certified tools from US providers. <a href="https://www.stackfield.com/blog/privacy-shield-alternative-gdpr-114">However, now that the agreement is no longer valid, following the ECJ’s “Schrems II” decision, it is no longer possible to confirm an adequate level of data protection through this agreement.</a></p><p>Why not show that European or German project management tools are by no means inferior to US tools? Quite the contrary: they offer legal security and support in your native language.</p><p><em>Originally published at </em><a href="https://www.stackfield.com/blog/project-management-tools-119"><em>https://www.stackfield.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=13f49b87cb98" width="1" height="1" alt=""><hr><p><a href="https://medium.com/stackfield-stories/perfect-fit-the-right-project-management-tool-for-your-team-13f49b87cb98">Perfect fit: The right project management tool for your team</a> was originally published in <a href="https://medium.com/stackfield-stories">Startup stories about the experiences and the mistakes we have made.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Common bottlenecks in internal communication]]></title>
            <link>https://medium.com/stackfield-stories/common-bottlenecks-in-internal-communication-6f6cdfaf0e20?source=rss-b269a15ec89a------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f6cdfaf0e20</guid>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[internal-communications]]></category>
            <category><![CDATA[communications-strategy]]></category>
            <category><![CDATA[team-communication]]></category>
            <category><![CDATA[team-collaboration]]></category>
            <dc:creator><![CDATA[Lena Wimmer]]></dc:creator>
            <pubDate>Fri, 25 Jun 2021 15:56:13 GMT</pubDate>
            <atom:updated>2021-06-25T15:56:13.470Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/740/0*Yn-734ilIlVmf3VK.png" /></figure><p><em>No man is an island</em> — this old proverb applies to business, too. You might be working with cutting-edge technology and the best professionals out there, yet you still won’t reach your goals if good communication habits are not in place. While the managers and CEOs always put an emphasis on the technical side of things (which is, obviously, perfectly justifiable), the value of smooth internal communication is often overlooked. But in many cases, this is the crucial issue when processes begin to falter, when tasks end up inadequately completed, and when people react too late to risks and opportunities.</p><p>I think you know what it’s like when misunderstandings occur. You know how nerve-wracking it is when problems arise that could have been easily avoided with clear communication. You know that many mistakes, such as missed deadlines and improperly implemented tasks, have their origin in poor communication. So now that we all know about this — well, we’ve been there -, let’s talk about how to avoid these situations.</p><p>These are the biggest problems with internal communication:</p><h3>There is (almost) no internal communication</h3><p>Obviously, the worst kind of internal communication is no communication at all. That may be a very harsh way of putting it. However, the fact that there is too little exchange in companies is a very common problem. I don’t think I really need to mention that a massive lack of communication within a team or within an entire corporation can have serious consequences.</p><p>What is definitely worth mentioning, however, is that there can be many different reasons why silence often reigns within one’s own company, and unfortunately it is not always that easy to find out what they are.</p><p>Now, what can be the reasons for this?</p><p><strong>Employees tend to communicate very little</strong> if they do not feel valued and noticed and are therefore not confident enough to express their opinions. <em>After all, people won’t actually bother anyway.</em> The situation is very similar in a work environment where the standards are too high. Employees will only express their ideas and opinions if they feel safe and free to make mistakes. Also, it’s not really helpful if an overly competitive mindset dominates teamwork, because this leads employees to think it might be rather beneficial for them to keep great ideas a secret rather then telling their competitors. Employees will not develop a sense of community, which inevitably discourages collaboration as well. A well-functioning team pulls together and tries to work successfully with all colleagues, which, of course, also means that colleagues will support each other in achieving success.</p><p>Just as important as taking a look at the teams is illuminating the <strong>communication behavior of the management level</strong>. If they do not communicate — quite explicitly the “top-down” way — this will have a massive impact on the entire organization. They put the trust of their employees at risk and fail to fulfill their role model function. But why does company or team management fail to communicate, or why do they communicate only sporadically? Perhaps they are purposefully keeping negative information under wraps. Maybe they don’t think it’s important to get employees involved. Either way, this approach is bad for employee motivation, the sense of belonging and the work environment in general. Of course, you can’t always involve everyone in decision-making processes, BUT: employees, who are expected to work every day to achieve the company’s goals, have a right to be informed about important developments affecting the company. At least, they should feel that their opinions matter, too.</p><h3>The solution: a safe environment, appreciation and team spirit</h3><p><strong>Build a safe communication culture</strong></p><p>Encourage employees to share their ideas and views in an open and honest way. The company benefits from everyone’s input, but that’s only possible if people are able to speak in a safe environment that takes all input seriously — even if it’s seemingly “bad ideas.” If you are afraid to express your opinion because ideas are often ignored or bad-mouthed, you won’t contribute the real good suggestions either. And let’s be honest: everyone can be creative and sometimes we have good ideas and sometimes… not.</p><p><strong>Support team spirit</strong></p><p>Instead of pushing your employees to competition, you should rather focus on team spirit. You could easily support this by replacing individual goals with team goals. Employees will be encouraged to collaborate better and to communicate more. In addition, individuals feel stronger being part of a group with less fear of making mistakes.</p><p><strong>Involve employees in processes</strong></p><p>Be careful not to ignore certain employees and colleagues in joint projects and consult with them when important decisions are to be made. This way, you can convey a sense of appreciation to your teammates and also benefit from different points of view.</p><h3>Information gets lost or overlooked</h3><p>Another common problem with internal communication is this: You are aware that communication is important and also in which areas you need to pay special attention to it, however, you often find that important information gets lost or completely overlooked. The bad thing is: information that falls out of sight is worth just as much as an exchange that doesn’t exist at all — namely, nothing at all. The good thing is: Where there’s a will, there’s a way. You can fix this problem very easily with a little organization.</p><p>But first: What are the reasons for information suddenly disappearing?</p><p>In many cases, it is simply <strong>the wrong use of digital tools</strong> in internal communication. Those are actually there to improve communication, so: The more the merrier, right? No. These tools are great, no question, but they can cause your team a lot of headache if you don’t use them the right way. Not right in this case means too many and too unspecific.</p><p>Multi-channel communication is an all-time danger spot, especially in <a href="https://www.stackfield.com/project-management">project management</a>, when many people are working together on a large task. Work progress will be recorded in the <a href="https://www.stackfield.com/blog/project-managementsoftware-compared-75">project management software</a>, some things will be discussed over the phone, news is often simply forwarded by email and then there are excel spreadsheets on the drive and a separate chat tool used to discuss things in between. Can you see where this leads?</p><p>The information is scattered all over the place. If you are looking for a specific piece of information, you don’t even know where it was recorded or whether it was recorded at all. In the end, you don’t even know if your colleagues were informed about the news you received via email. And even if we don’t want to admit it to ourselves, our brains simply can’t remember everything or simply retrieve it at the right time. After all, that’s what we have digital solutions for, that store important information for us.</p><h3>The solution: a central location and clear rules</h3><p><strong>Define a central location for all information</strong></p><p>As I said, the solution to this problem is quite simple. Choose the right collaboration tool where you can store all the information in a centralized and bundled way. For this very reason, we made Stackfield an <a href="https://www.stackfield.com/blog/all-in-one-collaboration-tools-121">all-in-one collaboration tool</a>, that allows you to attach all the important files, images, and comments directly to the related tasks. This way, communication takes place directly where it should take place — on the topic. Only if this prerequisite is given, employees will know where to find all information anytime. They don’t have to keep track of multiple channels, just one, and they can be sure that updates always reach all team members involved directly.</p><p><strong>Set rules for internal communication</strong></p><p>Of course, there will still be exchanges through other channels from time to time — such as email exchanges with customers and other stakeholders, or one-on-one conversations in meetings and phone calls. The only important thing is that everything that is discussed at these meetings also ends up in the central information pool. Simple rules can help you ensure that this is the case. Encourage employees to store all details that are discussed elsewhere directly in the collaboration tool they use. How you structure the tasks is up to you. Custom fields and comments as well as subtasks may be appropriate places, depending on the workflow and process. It’s best to take a close look at internal processes first and consider how they can best be mapped in the rooms and tasks.</p><h3>Miscommunication is a major issue in internal communication</h3><p>It is what it is: we’re having a conversation with a colleague going through the next steps for the upcoming project. <em>I’ll take care of that task involving the appointment and you’ll take care of the issue that was brought up in the conference today, all right?</em> Full of drive, we get to work only to check back in with the colleague a week later for a brief consultation, and we realize: the colleague has done a completely different task than the one originally agreed upon. Perhaps he didn’t? Unfortunately, miscommunication is an everyday problem at work, and in the worst case it can lead to deadlines not being met and goals not being achieved. Sometimes you can’t avoid them completely, but you should at least try to keep them to a minimum.</p><p>But how do misunderstandings occur?</p><p>The way people articulate themselves and how detailed information is passed on is quite an issue in this regard. Thus, the colleague who “misunderstood” the instruction may not always be the one to blame. Perhaps the problem is on both sides, but that’s exactly why it’s important to be careful about being clear and concise.</p><h3>The solution: a precise and clear language</h3><p><strong>Articulate yourself with precision</strong></p><p><em>That particular topic that was discussed in the meeting</em> — this is a statement that is virtually predestined for misunderstandings. When relaying information or even work instructions, always make sure to express yourself precisely.</p><p><strong>Separate the important from the unimportant</strong></p><p>It is also very important to pass on information entirety. Of course, you shouldn’t come up with a whole-length bedtime story when it comes to short instructions, because after all, too much information can also be confusing. However, it sometimes happens that important changes or details that came up during the process are not passed on to the next person in charge — details that are actually urgently needed for processing. If the task due date changes from <em>Monday in a week</em> to <em>tomorrow</em>, that is definitely something that should be addressed explicitly — and preferably verbally.</p><p><strong>Simple is better</strong></p><p>Business rule number 1: Why keeping it simple when you can make it complicated? Every sentence is peppered with specific technical terms and abbreviations in order to appear as professional and smart as possible. But maybe the new trainee or the colleague from another department is not familiar with these terms? <em>They can ask!</em> The non-specialist colleague may also have no problem asking several times what SLA and connectivity actually mean or what the heck he is supposed to do with an “appointment slot” and a “wrap-up”. But maybe the new trainee has problems with it and feels intimidated, or the employee who is not very fluent in English? Overuse of complex terms won’t make anyone appear smarter — but it will certainly make things a lot more complicated. Wasn’t it Einstein who said, “If you can’t explain it simply, you don’t understand it well enough”? Well, he understood…</p><h3>News won’t reach every employee</h3><p>“ How come nobody told me that the system is down today? I made 3 customer appointments on this!”</p><p>“ It was announced in the meeting the day before yesterday.”</p><p>“I was on vacation.”</p><p>If important news and changes in the process workflow are not communicated to everyone involved, you may quickly run into problems. Things get especially difficult as outdated information starts to be communicated to customers, as promises are being made based on outdated processes, policies or product data, or, as in this case, as people make appointments that can’t be met due to short term deviations.</p><p>How can such situations arise?</p><p>Witha certain number of employees or team members, it is simply not so easy anymore to keep track of everything. An employee may be unable to join the info meeting or people simply forget to inform a person about certain news. Perhaps they just don’t consider that this certain piece of information could be relevant for a certain person. Either way, you need to clearly and reliably communicate to all relevant parties. A meeting is a good approach, but as we can see, there are one or two weak points here as well.</p><h3>The solution: a global channel and verification</h3><p><strong>Create a global channel that keeps everyone in the loop</strong></p><p>Any news that affects the entire team or even the entire organization should be disseminated through a global channel that everyone can actually access. The intranet would be such a channel, but so would the collaboration platform in use. It is advisable to create a room or a chat where particularly important news is posted and to tell the employees that everyone should keep an eye on it. If you use Stackfield, you can easily mark rooms as favorites in the sidebar and thus fix them separately in the upper area. This way, new activities are always directly visible.</p><p><strong>Make assurance double sure</strong></p><p>Of course, in some cases it also makes sense — it is even advisable — not to rely solely on employees keeping an eye on all messages. Two is better than one, which is why you definitely won’t go wrong with an additional announcement in a meeting and a short reminder.</p><p><em>Originally published at </em><a href="https://www.stackfield.com/blog/internal-communication-issues-136"><em>https://www.stackfield.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f6cdfaf0e20" width="1" height="1" alt=""><hr><p><a href="https://medium.com/stackfield-stories/common-bottlenecks-in-internal-communication-6f6cdfaf0e20">Common bottlenecks in internal communication</a> was originally published in <a href="https://medium.com/stackfield-stories">Startup stories about the experiences and the mistakes we have made.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Multi-project management: Run multiple projects in parallel]]></title>
            <link>https://medium.com/stackfield-stories/multi-project-management-run-multiple-projects-in-parallel-80655ee37abd?source=rss-b269a15ec89a------2</link>
            <guid isPermaLink="false">https://medium.com/p/80655ee37abd</guid>
            <category><![CDATA[resource-management]]></category>
            <category><![CDATA[project-management-tool]]></category>
            <category><![CDATA[project-manager]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[resource-scheduling]]></category>
            <dc:creator><![CDATA[Lena Wimmer]]></dc:creator>
            <pubDate>Thu, 17 Jun 2021 16:47:05 GMT</pubDate>
            <atom:updated>2021-06-17T16:47:05.774Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*ENq_SjGTC3XOQvbjLz0bgQ.png" /></figure><p>One step at a time. The best way to work is to focus on doing one thing before we head over to the next. This is actually a very good approach in almost as all matters, but unfortunately it is not always as simple as that. In companies, people usually don’t work on just one project, but on several at the same time.</p><p>Why is it important to not only focus on one thing and to keep an eye on the bigger picture in this case? How can I do that? Good questions. That’s what we’re going to deal with today.</p><h3>What is multi-project management and what is not multi-project management?</h3><h3>Definition: multi-project management, program management, portfolio management</h3><p>When several projects run simultaneously, you will most likely come across terms like multi-project management but also program management or portfolio management. Three terms for one and the same thing? Not quite.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*SlksTNjxal-QxjGz.png" /></figure><p>But let’s start with the core from which all these terminologies originate: the project itself. According to <a href="https://www.din.de/de/">DIN 69901</a>, this is defined as a “undertaking that is significantly defined by the uniqueness of its conditions overall, i.e. its goal or time, financial or personnel and other limitations, delineation from other undertakings or project-specific organisation” exactly defined.</p><p>Needless to say, these projects are quite complex matters that need to be planned down to the last detail. And this is where <a href="https://www.stackfield.com/project-management"><strong>project management</strong></a> comes into play, essentially covering all activities that are necessary to achieve the project goal: from initialization, definition, planning, control to the final conclusion.</p><p>As soon as an organization conducts several projects simultaneously, we refer to this as <strong>multi-project management</strong> (MPM), and multi-projectmanagement is extremely important. It is intended to ensure that potential conflicts between individual projects are taken into account in the course of project implementation, preventing the success of one project from being jeopardized by the requirements of another.</p><p>However, you should clearly distinguish the term <strong>program management</strong> as this essentially describes the management of several related projects that share a common, overarching goal. This means that one program emerges from several interconnected, thematically related projects.</p><p>The term <strong>portfolio management</strong> is often used synonymously with the term multi-project management in everyday usage. For others, however, it is used to describe the totality of all projects in an organization or team.</p><h3>In short: What do you need multi-project management for?</h3><p>Multi-project management aims to prevent any potential conflicts of resources or goals between the individual projects that are being carried out in parallel. The goal is to ensure that expected results are not jeopardized by requirements from other projects. Inevitably, this requires maintaining an overview of all ongoing projects — which, even considered individually, can present a complex challenge.</p><p>Now, what do you need to pay attention to exactly?</p><h3>This is what multi-project managers need to take care of</h3><p>It is important to understand that every project has certain requirements, be it human resources, work equipment or financial resources. The requirements need to be served and this only works by keeping track of what requirements each project has at any given time. The <strong>challenges</strong> that multi-project managers have to contend with are…</p><ul><li>inadequate oversight in the requirements that individual projects pose,</li><li>unclear dependencies and</li><li>incorrect prioritization,</li></ul><p>which, in turn, may lead to</p><ul><li>goal conflicts</li><li>and resource conflicts.</li></ul><p>However, for those who regularly align projects in all their stages in the best possible way and keep track of them, there are also opportunities, because this way you can efficiently use <strong>synergy effects</strong>.</p><h3>Multi-project management requires the right software solution</h3><p>A <a href="https://www.stackfield.com/blog/project-managementsoftware-compared-75">project management software</a> is crucial, especially for multi-project management, as it enables all projects to be clearly displayed and monitored. Without the right tools, it would be simply impossible to keep track of all important data, activities and changes.</p><p>Multi-project management therefore requires one thing above all: a central place where you can collect all the important information, clearly structured.</p><p>This is how Stackfield supports the monitoring and management of multiple projects:</p><h3>Projects become manageable in separate rooms</h3><p>Each project within the organization will be visualized in a <strong>separate workspace</strong> and executed in collaboration with everyone involved in the project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*DrwDHH2YZ6mT3A5n.jpg" /></figure><p>These workspaces are called <em>rooms</em> in Stackfield, and there is a very special kind of <em>room</em> for projects, but more on that later.</p><p>Each <strong><em>room</em></strong> created in an organization can be equipped with various project-related tools that best support planning and collaboration on individual project requirements. Among the most important for project operations are:</p><ul><li>the <a href="https://www.stackfield.com/help/working-with-documents-2021"><strong>pages</strong></a>, used to record project plans and important key data about the overall project</li><li>a <a href="https://www.stackfield.com/help/working-with-files-2015"><strong>file manager</strong></a> that keeps all important files — whether stored individually or originally attached to other items such as tasks — in an organized manner</li><li>a <a href="https://www.stackfield.com/help/working-with-events-2022"><strong>calendar</strong></a> that can be used to schedule important events and meetings during the project</li><li>the <a href="https://www.stackfield.com/help/working-with-tasks-2010"><strong>task module</strong></a> serving as the centerpiece of your room, allowing the team to record all requirements on functional task cards and to visualize them on a Kanban board or in lists, depending on their purpose</li><li>a <a href="https://www.stackfield.com/blog/gantt-charts-basics-116"><strong>Gantt chart</strong></a>, also called , that shows all tasks and milestones in their chronological progression while also taking into account all dependencies between tasks, thus enabling the team to quickly discover bottlenecks in order to make changes to the plan within time</li><li>and the <a href="https://www.stackfield.com/help/communication-module-2043"><strong>Communication Module</strong></a>, that serves as a project-specific team chat right inside the room — that is, inside the project itself. It keeps all information together and ensures that not only message exchange but also activities remain chronologically traceable.</li></ul><h3>Special project overviews keep up to date</h3><p>So, one room on Stackfield already offers all the basic tools needed for project work. But if you want to implement large projects or even several, you need a little bit more.</p><p>Stackfield’s <a href="https://www.stackfield.com/help/using-project-rooms-2093">project rooms</a> were created specifically for monitoring and controlling projects, and include a dedicated project overview in addition to the usual tools for requirements management and project visualization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*fDwY_ALZKjzlvFUh.jpg" /></figure><p>With the help of various graphics, it continuously informs those involved about the progress of the project and provides all the important key data — such as priorities, time budget, status and main persons responsible.</p><h3>Project portfolios support multi-project management</h3><p>A <a href="https://www.stackfield.com/help/use-everything-function-2084#Portfolios">portfolio</a> that shows all projects within your organization gives you an overall overview.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*QrMn5XBEytndV104.jpg" /></figure><p>It shows what priority has been assigned to each project, what their status is at the current time, and what progress they have made. You can see at a glance what projects overlap in time, making them particularly important to coordinate. A click on the project shows gives you quick access to all the important details of the project overview, allowing you to make adjustments as soon as necessary.</p><p><strong>Tracking and alignment:</strong> To be able to successfully carry out multiple projects, you need one thing above all: a continuous overview. A regular look at the portfolio and the project overviews as well as a consistent comparison of the project schedules (Gantt charts) will support you in this task.</p><h3>Tips and must-do’s in multi-project management</h3><p>If you want to make sure all your projects go according to plan and are optimally aligned (stay that way, too), try to keep the following tips in mind.</p><h3>Detailed project planning</h3><p>Proper project planning is not only the basis for multi-project management, but also for successful execution of the individual projects themselves. Those who do not take enough time for planning will very likely atone for this in the further course.</p><p><strong>Tip:</strong> Your project planning is essentially based on the project scope, resources and time budget. Create the <a href="https://www.stackfield.com/blog/create-the-perfect-project-plan-77">project plan</a> in detail and with foresight and also include possible risks that may arise in the course of the project. If several projects are to run in parallel, it is important to balance the resource requirements and to consider synergies in the planning. That way, you’ll be able to bundle the right projects — those that benefit each other in their execution and whose resource needs don’t get in each other’s way.</p><h3>Setting Priorities</h3><p>You need to provide for all contingencies. What if there is a resource shortage? What if time constraints arise? The correct prioritization of projects is indispensable in this regard. This includes the individual requirements within the projects, as well as the projects themselves.</p><p><strong>Tip:</strong> Determine exactly what priority the individual projects have for the overall business goals. If it comes to resource problems, you should be able to tell exactly what project has priority. Equally important is the following questions: What tasks within the projects have priority so as not to jeopardize their associated project and what projects can cope with changes and deviations better than others?</p><h3>Creating a central information base</h3><p>As mentioned, regular reconciliation and ongoing monitoring of projects are essential when it comes to multi-project management. However, this only works properly if all important information is in a central location that can be accessed quickly and easily.</p><p><strong>Tip:</strong> Choose a central project management software that allows you to visualize all projects and to track them collectively. Processes must remain traceable, which is why it is also not recommended to let the project communication run in a separate tool. Communication should always take place directly at the tasks within the project, to ensure that information is not scattered randomly and that those involved are not missing anything important.</p><h3>Keep status and key data up to date</h3><p>To be able to adjust projects if necessary for smooth execution in parallel, changes in the planning of individual projects should be obvious at all times.</p><p><strong>Tip:</strong> Deposit information on the project status and important changes to the plan, that could have an impact on capacity planning, always directly and inform the project members. Key data should always be available and up to date for everyone involved. Changes that have a massive impact on the status of the project can be noted directly in the project overview.</p><h3>Multi-project management fails with a lack of transparency</h3><p>As soon as you need to run more than one project, you need clear and transparent multi-project management. Project teams face a number of challenges, most of which can only be overcome if management maintains an overview at all times and continuously coordinates capacities as well as schedules, observes priorities and properly communicates all changes.</p><p><em>Originally published at </em><a href="https://www.stackfield.com/blog/multi-project-management-135"><em>https://www.stackfield.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=80655ee37abd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/stackfield-stories/multi-project-management-run-multiple-projects-in-parallel-80655ee37abd">Multi-project management: Run multiple projects in parallel</a> was originally published in <a href="https://medium.com/stackfield-stories">Startup stories about the experiences and the mistakes we have made.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[10 secrets that help you to make task planning hassle-free]]></title>
            <link>https://medium.com/stackfield-stories/10-secrets-that-help-you-to-make-task-planning-hassle-free-9e650db30a79?source=rss-b269a15ec89a------2</link>
            <guid isPermaLink="false">https://medium.com/p/9e650db30a79</guid>
            <category><![CDATA[task-management]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[to-do-list]]></category>
            <category><![CDATA[task-management-software]]></category>
            <category><![CDATA[kanban-board]]></category>
            <dc:creator><![CDATA[Lena Wimmer]]></dc:creator>
            <pubDate>Thu, 10 Jun 2021 14:47:54 GMT</pubDate>
            <atom:updated>2021-06-10T14:47:54.856Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*onL6pa-bzfg0du5Dc-TyPg.png" /></figure><p>“All of a sudden I have so much time! I don’t even know what to do with it.”Hands up: Anyone else who fights the strong urge to roll their eyes at these statements? Anyone else who currently feels like they’re drowning in tasks? Home office, home schooling, more housework, home cooking — working at home doesn’t necessarily mean having more time. But we can create time — with more structure and a little trickery in task planning!</p><p>Spoiler: the main way we speed things up is to dial it down a notch … or let’s say three.</p><h3>Take advantage of task planning software</h3><p>For private purposes, a simple to-do list is absolutely sufficient — depending on the purpose and scope as a memo on the fridge, on a notepad or simply using an app on your smartphone. Task completed, checked off, and off to the next item we go.</p><p>In everyday work, however, we have to deal with a larger amount of tasks, often of higher complexity — in particular when it comes to <a href="https://www.stackfield.com/project-management">project management</a>. A task planning software supports you where memo board and notepad are no longer sufficient.</p><p>It allows you to,</p><ul><li>record tasks regardless of location and time (provided you also use it via a mobile device),</li><li>set deadlines and meet them,</li><li>visualize tasks with the help of a wide variety of views,</li><li>help your memory through notifications,</li><li>keep your to-do’s organized and clear,</li><li>and to collaborate with other colleagues on tasks.</li></ul><h3>These are the features that task planning software should include</h3><p>Because task processes can become very complex, good task planning software for teams or companies does not consist of lists alone.</p><p>An advanced <a href="https://www.stackfield.com/blog/project-managementsoftware-compared-75">project management software</a> includes a variety of features that support task planning, and it provides you with various views that illustrate the workload according to different criteria.</p><h3>The basis: functional task cards</h3><p>They are the basis of any task planning tool. On the task cards, you record all the important key data about the task — such as due dates, description texts, people assignments and other information needed to complete the task. The ability to attach file attachments to tasks is also essential.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*5UZGYhKFKmHBH0a1.jpg" /></figure><p>If you want to optimize task planning in the best possible way, also make sure that the cards offer you the following features:</p><p><strong>Subtasks</strong>: Lists for subtasks allow you to break down more extensive tasks into individual subtasks. This way, you don’t run the risk of forgetting important steps without completely cluttering your view with task cards and making it confusing. Often several people are involved in a task, which is why the subtasks should also be assigned to different collaborators, and separately dated and provided with key data.</p><p><strong>Time recording</strong>: Time recording for tasks serves many purposes. First and foremost, documenting the processing time of individual tasks facilitates billing, planning and adherence to time budgets, and meeting deadlines.</p><p><strong>Labels</strong>: They are mainly used to categorize your tasks within your view, because with an increasing number of tasks it becomes more and more difficult to keep track of them. Using labels, you can assign a group of tasks to certain topics or highlight what kind of task it is.</p><p><strong>Comments</strong>: The exchange in the team on individual tasks or project topics is absolutely necessary. But to keep communication as clear as possible, it should take place directly on the topic — not in a separate chat tool, for example. Why? It is simply easier for you and your colleagues to keep the exchange comprehensible and to easily recall important decisions later on. So if you want to know if there were important decisions on a task that could affect your work, you’ll know immediately where to find them.</p><p>Of course, task cards alone do not make a good task planning tool. What’s important now: organize the task cards into meaningful views!</p><h3>Kanban, Gantt and lists: a suitable view for every purpose in task planning</h3><p>Task planning software solutions offer you different views that give you a different perspective on work processes, depending on their purpose.</p><p>The digital <strong>to-do list</strong> is the traditional form of task management and the more modern version of the notepads we all know and love. For your private agenda and small sets of tasks with workflows of little complexity, they are often quite sufficient as well. The great thing is that the task lists are often provided with a grid structure making it easy to sort them with just a few clicks, e.g. by date, status, assignment or label. This way, you can quickly see which tasks are due next for you, which tasks on a certain topic are still open, and who is working on what or might even be overloaded.</p><p>The <strong>Kanban Board</strong> (in <a href="https://www.stackfield.com/blog/agile-project-management-127">agile project management</a> often used as a special Scrum Board) goes one step further and helps you to map the individual <a href="https://www.stackfield.com/blog/safe-time-with-the-right-workflow-81">workflow</a> of your team. The <a href="https://www.stackfield.com/blog/the-5-best-kanban-board-tools-80">Kanban Board</a> consists of various status columns that your tasks pass through in the course of their processing. Basically, it is several lists that you have created to sort your tasks by topic and processing status. In this way, you’ll be able to see directly at which point a task is currently located, which step it should go through next, and what the workload is in general. A good task planning software will let you expand and name the status columns individually, so that the board later also reflects the individual workflow of your team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*jTkRIR5XNQ_9i-xg.jpg" /></figure><p>The <strong>Gantt Chart</strong> is not so much intended to map a workflow as it is to properly plan the schedule. It visualizes all tasks in their chronological progression and also takes into account any dependencies between tasks as well as major milestones towards the end of each work phase. For this reason, the <a href="https://www.stackfield.com/blog/gantt-charts-basics-116">Gantt Chart</a> is also very often used in <a href="https://www.stackfield.com/blog/create-the-perfect-project-plan-77">project planning</a>, because here it is especially important to implement requirements on time. The view is a really great tool for keeping an eye on progress and optimally integrating changes to the project schedule into the processes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*9Z5XG4Ajdr9ZxWw5.jpg" /></figure><p>So much for the basics of working with digital task planners. The question that remains is how you manage not to get overwhelmed by the huge amount of tasks — because, honestly? Even with task scheduling software, it’s sometimes not that easy to keep track of everything. That’s why we’ve put together a few tips to make your work a little easier.</p><h3>These are the #10 secrets to hassle-free task planning</h3><h3>#1 Plan how you schedule tasks</h3><p>Sound weird? Well, probably. But in fact, you’ll make your job a lot easier if you take a few hours, take a close look at your team’s processes, and think about how those processes can best be mapped in software. Good software supports your processes — not the other way around!</p><p>Look at what steps your team takes to get the job done. Examine the distribution of tasks and the structure of tasks. If this irritates you a bit, here’s an example:</p><p>You will notice that very different workflows have been integrated into different departments and teams, and that the structure of tasks and workflows within these workgroups is often repetitive. In a support team, you will need completely different types of information to complete tasks than you might need in procurement, for example. While support deals primarily with customer data and customer correspondence, procurement deals with approvals, cost centers and order forms. The task cards that the respective teams work with can take this key data into account — thanks to user-defined fields.</p><h3>#2 What you don’t record today, you’ll forget tomorrow!</h3><p>A software is meant to be used and especially so when it comes to task planning. As soon as a new topic comes up, as soon as an idea manifests in your mind, as soon as circumstances change to a task: Write. It. Down!</p><p>We often tend to overestimate our brains a bit. No offence. We are not machines, after all, and therefore our brain is also limited in its storage capacity. The <a href="https://www.stackfield.com/blog/information-overload-92">information overload</a> we increasingly have to deal with doesn’t make things any better. What you don’t write down today, you’ll probably forget tomorrow, because over the next few hours there there’s certainly more information creeping into your brain. And your brain will try to make room for it. There was some important information your boss didn’t want you to forget — gone with the wind! Your task planning software would have remembered.</p><h3>#3 A list… and another list… and another list…</h3><p>Now, that’s pushing it, you’d think! In this case, no. Be sure to separate what doesn’t belong together. I know we often tell you that Stackfield lets you keep all your information in one place. However, that doesn’t mean you should collect all tasks on one list, regardless of their subject matter. If the requirements from project A are suddenly joined by personnel tasks and accounting procedures… or even the note “Buy more toilet paper, don’t forget!”, what will the view be like? Right: CONFUSING! In any case, you don’t do your productivity any favors with that.</p><p>Therefore: Create a digital counterpart for each workspace (on Stackfield it would be rooms). Work with status lists for workflows and let me tell you: There is always a workflow. If it’s not an agile project workflow of the type <em>Backlog — Progess — Testing/QA — Release — Done</em> or an editorial plan of the type <em>Topics — To Do — Proof — Graphic — Publish — Newsletter</em>, then maybe one of the type <em>Ideas — To Do — In Progress — Done</em>.</p><h3>#4 Set feasible tasks</h3><p>“I don’t want realism. I want magic!” If you are processing tasks as if you were Blanche Du Bois her very self, you are wrong about so many things. Loss of reality has no place in task planning. Tasks have to be actionable and that requires one thing from you in particular: to stay realistic.</p><p>What sounds quite obvious is not so simple in reality. Of course we have a goal in mind and we want to achieve this goal. However, if you set your goals too high, you can quickly lose sight of them, which puts them far off in the distance. The result of success is missing and therefore the motivation decreases. This does not sound like a good approach. Staying realistic in your task planning means, on the one hand, that you think carefully about whether something can be implemented at all. On the other hand, you have to figure out how to make “seemingly impossible” tasks feasible. And that leads us to the next point…</p><h3>#5 Mammoth tasks become extinct</h3><p>I recently wrote an <a href="https://www.stackfield.com/blog/microproductivity-130">article on microproductivity</a> that deals with this very issue: breaking down seemingly unachievable mammoth tasks in a way that leaves several tasks that are quite easy to implement. Instead of unsuccessfully chasing one big goal, you suddenly record a whole series of quick wins. The approach not only increases your productivity because you can focus on one thing at a time. It also boosts your motivation.</p><p>You can easily implement this strategy by creating multiple tasks (making them interdependent or thematically linked with labels, if necessary) or by creating subtasks that you can check off one by one. Stackfield shows you the progress by means of a bar, so that you can see your achievements right in front of your eyes.</p><h3>#6 Avoid vague task titles</h3><p>What do you do when you’re assigned a task with a title that doesn’t state clearly what needs to be done? Procrastinate, probably. Even if the task was actually quite simple — it doesn’t sound simple. Our mind played a trick on us. We push the task to the very back of our minds because in order to do it, we have to examine it very carefully first. Now, what do you do when you know what needs to be done? You do it!</p><p>Always set tasks for yourself and for others in a way that makes it immediately obvious what it is actually about. What is to be done? What should the result look like? And at best: Why is this to be done? You always ask yourself these questions when you create a task and at some point you follow the scheme completely automatically.</p><p>What task would you rather work on? The one titled: “Performance analysis” or the one titled “Determine the default rate over the last three months”? I think you know what I mean.</p><h3>#7 Priorities need to be set</h3><p>Distinguishing the important from the unimportant (or let’s say “less important”) — that’s not quite a big deal. But when we’re dealing with a multitude of tasks, it becomes difficult to keep track of what’s important.</p><p>Make these tasks stand out! This works great if you either work with due dates and keep them up to date (which is important anyway) or if you simply use labels. Take a quick look at your to-do’s for the day every morning and try to complete important tasks right away.</p><h3>#8 Prepare for the next day</h3><p>Taking a quick look at your to-do’s in the morning is much more pleasant, by the way, if you keep this list up to date. This is similar to the trick of planning your clothes the day before. If you plan your tasks in a similar way and prepare your list for the next day the evening before, you will start the day more relaxed and you can start right away. This saves energy for the actual tasks.</p><h3>#9 Birds of a feather flock together</h3><p>By turning big tasks into several small tasks, we simplify our work considerably. However, there is another trick we can use. We get an overview of our tasks and realize: there are a few tasks that are clearly similar in their execution: You have to gather some more information in different places. Moreover, you have to order a few pieces of equipment. In addition, there are quite a few invoices that need to be written or processed.</p><p>Combine similar things as best you can. That way, you don’t have to constantly rethink and you’ll work much more efficiently! The great thing about it: with these small heaps of tasks, the to-do list feels much shorter.</p><h3>#10 Compliment yourself for singletasking, not for multitasking</h3><p>From many of our task planning tips, you’ve probably already guessed: Multitasking is not something you should strive for. You’re switching from one topic to another, you have to “think” your way into the topic each time, and you keep forgetting where you left off.</p><p><a href="https://www.tk.de/techniker/magazin/life-balance/balance-im-job/weniger-stress-ohne-multitasking-2007152?tkcm=ab">That we are capable of performing multiple tasks simultaneously is actually a fallacy</a>. We can perform multiple actions related to the same goal at the same time, but when we need to make decisions about different facts, our brain needs full focus for one of those decisions. Then, rather than performing multiple tasks simultaneously, we interrupt them and mentally switch to another one. Ultimately, we sabotage our brain by doing this. Instead of checking off many tasks in one go, we don’t really get anything done efficiently. Therefore, force yourself to singletasking by trying to focus on one task at a time. You’ll see that everything becomes much easier to handle.</p><p>If you want to complete your tasks sooner and with less effort, you’ll probably have to outsmart yourself from time to time and take advantage of psychological benefits in particular. The way our brain works and the way we perform tasks are inevitably related. Motivation is definitely a key aspect that you should never ignore. With our tips, you can influence this to a certain extent all by yourself, so:</p><ul><li>be aware of what you can create,</li><li>keep a record of what you should not forget,</li><li>celebrate your successes (and use all the tools that highlight them to you)</li><li>and take it one step at a time.</li></ul><p>As contrary as it may sound: slow down to finally move forward!</p><p><em>Originally published at </em><a href="https://www.stackfield.com/blog/task-planning-software-133"><em>https://www.stackfield.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9e650db30a79" width="1" height="1" alt=""><hr><p><a href="https://medium.com/stackfield-stories/10-secrets-that-help-you-to-make-task-planning-hassle-free-9e650db30a79">10 secrets that help you to make task planning hassle-free</a> was originally published in <a href="https://medium.com/stackfield-stories">Startup stories about the experiences and the mistakes we have made.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Let’s get down to the basics with agile project management]]></title>
            <link>https://medium.com/stackfield-stories/lets-get-down-to-the-basics-with-agile-project-management-ca13b09a37ec?source=rss-b269a15ec89a------2</link>
            <guid isPermaLink="false">https://medium.com/p/ca13b09a37ec</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[kanban]]></category>
            <dc:creator><![CDATA[Lena Wimmer]]></dc:creator>
            <pubDate>Thu, 06 May 2021 14:26:56 GMT</pubDate>
            <atom:updated>2021-05-06T14:26:56.484Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*hjG6IMWlDdh8VdAZWFXUXg.png" /></figure><p>Agile project management is by far the most popular methodology, and in a vast majority of cases, the one that offers the most value to organizations since:</p><ul><li>it helps to reduce product defects,</li><li>improves the productivity of the team,</li><li>and increases the value of the product and business.</li></ul><p>Now, that’s some good reasons to take a closer look at the concept!</p><h3>What is agile project management?</h3><p>Agile project management is a set of methodologies, an umbrella term for a set of frameworks and practices designed for the projects that require speed and flexibility in their process. In many cases, the projects are related to software development, but not necessarily. Agile behaviors are not beholden to any particular framework and can conceivably be implemented without one. These behaviors simply help establish a collaborative, transparent, agile environment.</p><p>It’s more than <a href="https://www.stackfield.com/blog/project-management-methods-88">project management methods</a> such as Scrum, Kanban, Lean, Extreme Programming, or Feature-Driven Development. It’s not only about roles like scrum master, project manager, product owner, or only about scrum team. Agile development is also more than practices such as sprints, stand-ups, pair programming, test-driven development, or planning sessions.</p><p>As mentioned above, agile models are based on a flexible approach. Team members work in small phases and teams to deliver a specific product or service. Each milestone or update is then tested against the customer’s needs, rather than focusing on a single final product that is only released at the end of the project. Often it’s necessary to test the different features of the service on the go and assess whether they are working or not to deliver the final solution. Divide up the various product updates, work on them separately, test them one by one, and you’ll win.</p><p>Methodologies that are a part of the agile model (Scrum, Kanban, Lean, XP programming, etc.) are especially suitable for companies and sectors involved in contexts of constant change, especially complex projects or emergencies where we do not have the time to develop the project conventionally.</p><p>In this sense, the agile approach allows you to embrace change, without prejudice, even at the ?nal development stage. To do this:</p><ul><li>It aims to deliver the highest possible business value.</li><li>It’s built based on obtaining information in real-time.</li><li>It uses comprehensive management of costs, time, and project scope.</li></ul><p>This set of methodologies is based on a value-driven approach that allows project managers to deliver results in high priority and high-quality conditions.</p><p>Making this approach a reality depends on knowing how to plan projects, tasks, and assign responsibilities. Agile project management reduces the complexity of each initiative by breaking it down according to:</p><h3>What are the origins of agile methodology?</h3><p>Agile project management is a response to the limitations of traditional methods which, by the mid-1990s, were criticized due to their lack of flexibility and adaptability.</p><p>The various elements that make up the agile project management methodology have been in place for decades. However, two events helped lay the foundation for its successful approach:</p><h3>The New New Product Development Game</h3><p>In 1986, Harvard Business Review published in 1986 an article by Hirotaka Takeuchi and Nonaka Ikujiro entitled “ <a href="https://hbr.org/1986/01/the-new-new-product-development-game">The New New Product Development Game</a>” which describes a new form of product development similar to the tactics used in a rugby match. In this project management approach, as in the field, team members can achieve their goal by continually reassessing the situation and developing a response accordingly. Therefore, projects are designed in such a way that the results obtained are fully in line with the client’s expectations and needs.</p><h3>The Agile Mani?esto</h3><p>A group of software and project experts met to discuss what characteristics their most successful projects had in common. The values and principles on which agile project management is based were extracted from their conclusions and published under the title „ <a href="https://agilemanifesto.org/">The Agile Manifesto</a> “.</p><p>The Agile Manifesto outlines <a href="https://agilemanifesto.org/iso/en/principles.html">12 principles</a> of agile. The most vital elements relate to short-term adaptability and flexibility supported by feedback culture and seamless and open communication involving all stakeholders. Flat hierarchies and motivating environment are also perceived as essential parts of any successful agile project.</p><p><strong>Teams following any agile method should value:</strong></p><ul><li>Individuals and interactions over processes and tools</li><li>Working software over comprehensive documentation</li><li>Customer collaboration over contract negotiation</li><li>Responding to change over following a plan</li></ul><h3>The most common agile methodologies</h3><p>If an agile team chooses to follow conventions that follow agile values and principles, this is when they start applying agile methodology. Let’s have a look at some methods standard within the agile movement.</p><h3>Scrum</h3><p>The Scrum methodology allows tackling complex projects developed in dynamic and changing environments flexibly. It is based on partial and regular deliveries of the final product based on the value they offer to customers.</p><p>The method is ideal for managing projects within a complex environment that demands fast results and where flexibility is a prerequisite. Scrum offers an agility that always promises added value — even when it is necessary to react to a changing competitive situation at short notice, when there is a high turnover in your own team, or when you need to systematically identify and solve inefficiencies.</p><p>In the Scrum methodology, product development has a life cycle. Each phase has to correspond with the following:</p><ul><li><strong>What and who?</strong> The product we want to achieve once we finish the Sprint and the team roles with their assigned tasks.</li><li><strong>When?</strong> The deadline and the content of the Sprint.</li><li><strong>How?</strong> The different tools to apply these agile processes.</li></ul><p>If you are now wondering how this “life cycle” is structured and what exactly a “sprint” actually is: Project teams that use Scrum work in so-called <strong>sprints</strong>. This basically means nothing other than that they divide the development process into short, usually two-week sequences (sprints), that result in the delivery of a finished intermediate product. The sprint is one of five fixed Scrum events. The other four take place regularly within the respective sprints:</p><p><strong>Sprint Planning</strong>: In the first meeting, the team determines what can be achieved within the fixed period of time that the sprint covers. At this point, requirements that need to be implemented during the project are assigned to the following sprint.</p><p><strong>Daily Scrum</strong>: During the sprint, all team members meet daily for a stand-up meeting where they plan the next 24 hours based on progress.</p><p><strong>Sprint Review</strong>: The Sprint Review takes place at the end of the Sprint to present the completed Increment (intermediate product). If necessary, the team updates the backlog (requirements catalog) and determines what needs to be done next.</p><p><strong>Sprint Retrospective</strong>: The end of the Sprint is usually the Retrospective, which is held to take a closer look at the team’s processes and to reveal what went well and what didn’t, in order to show the participants optimization options for the further course of the Sprint.</p><h3>Kanban</h3><p>“Visual cards”, that’s what the term Kanban literally means and that’s also a very accurate description of the approach. Kanban as a project management method is less complex and regulated than Scrum. The main concern: to increase efficiency through clear workflow visualization. Ultimately, the tasks to be completed should be checked off as soon as possible. To achieve this, Kanban applies three basic laws:</p><ul><li>workflows are visualized with the help of a <a href="https://www.stackfield.com/blog/the-5-best-kanban-board-tools-80">Kanban board</a></li><li>work in progress (tasks in process) are strictly limited</li><li>the processing time of the tasks is to be monitored and optimized.</li></ul><p>Three clear rules that are used to pursue Kanban’s goal of keeping the focus of work on a few tasks in order to be able to perform them as efficiently as possible. As you might expect, multitasking is no longer appreciated at all. But where is the agility? Kanban does not impose strict rules, nor does it impose rigid roles and deadlines. This means that the requirements backlog can be expanded, restricted or reprioritized at any time. Short-term changes are virtually always possible, since there are no fixed sprints that have to be executed as planned.</p><p>Both Kanban and Scrum use boards, allowing the project teams to have a good overview of their own processes. This is why the two methods tend to be confused with each other, which is also why we took a closer look at the <a href="https://www.stackfield.com/blog/scrum-versus-kanban-79">differences and peculiarities of Scrum and Kanban</a> in another article.</p><h3>Agile project management and its impact on organizations</h3><h3>Impact on people</h3><p>This way of working emphasizes communication and collaboration among those involved in the project. Therefore, more than a definition of individual roles, it is preferred to establish the goals to be achieved as a team. The disadvantages of the approach appear when individuals are not able to develop their roles under conditions of self-management, have di?cultades to work as a team, or their stress levels increase, due to the frequency of sprints and their dynamism. Making a correct selection of personnel and monitoring their performance and levels of motivation and satisfaction are keys to the success of the implementation of the agile methodology.</p><h3>Impact on progress</h3><p>As soon as you apply agile methods, processes become a secondary priority. Instead of a structure based on phases, development takes place by sprints or stages that can be modified, a much more ?exible concept that allows adapting to changes more quickly. However, a little more attention is required when it comes to documentation, because this is largely based on verbal dialogs and board communication in the agile environment.</p><h3>Impact on the product</h3><p>The effects of agile methods on products are at their best. Instead of being limited to the original design, the highest priority is to satisfy the customer’s needs at all times. There are always deliverables already in place, although with each iteration, the overall picture can continue to improve.</p><p>Only with the high degree of flexibility, that allows you to react to changes in the market at short notice, you can create the best possible product in the end.</p><h3>Advantages of agile project management?</h3><ul><li><strong>Improved product quality</strong>: These methodologies encourage a proactive approach by team members in the quest for product excellence. In addition, the integration, testing, and continuous improvement of product properties significantly improves the final result.</li><li><strong>Increased customer satisfaction</strong>: The customer is more satisfied when they are involved and committed throughout the development process. Through various demonstrations and deliveries, the customer experience the improvements applied within the process in real-time.</li><li><strong>Increased employee motivation</strong>: Self-managed teams facilitate the development of creative and innovative environment among their members.</li><li><strong>Collaborative work</strong>: The division of work by different teams and roles, together with the development of frequent meetings, allows a better organization of work.</li><li><strong>Control and predictability</strong>: The opportunity to review and adapt the product throughout the agile process, allows all project members to control their work, which improves the ability to predict in time and costs.</li><li><strong>Cost reduction</strong>: Agile project management practically eliminates the possibility of absolute project failure, because errors are identified throughout the development instead of waiting for the product to be finished and all the investment made.</li></ul><h3>Disadvantages of agile project managment?</h3><p>Not all companies have embraced agile methodologies with enthusiasm from the very beginning, because there ARE some things that might become more difficult to manage at some point than is the case with more traditional approaches like Waterfall.</p><p>There is a risk that <strong>documentation</strong> will fall by the wayside, making it harder for new employees to get started.</p><p><strong>Resource planning</strong> is more challenging because it’s not clear from day one what the final product will look like. While this benefits the final product, it obviously makes it difficult to accurately estimate costs and time. And the larger and more complex the project becomes, the more challenging this task grows.</p><p>Because agile reserves the right to remain flexible and always welcomes change, it also bears the risk your team going astray. There is no clear end and there is a lack of <strong>project boundaries</strong> why teams need a lot of experience to stay on track and to avoid uncontroled expansion or even scope creep at the end.</p><h3>How do businesses use agile projectmanagement?</h3><p>Agile project management, although created for software development, is a multi-purpose concept that can be applied to a wide variety of projects. From software engineering to HR, agile can revolutionize an organization’s approach to product development, <a href="https://www.stackfield.com/project-management">project management</a> in general, and the implementation of internal processes.</p><p>Often, we find companies using <strong>hybrid approaches</strong>, which can be a mix of several agile approaches or even a combination of agile and traditional methods. Hybrid frameworks not only include the use of different approaches depending on the phase of the project but also include options for adopting agile practices in cascading processes.</p><p>For example, you might come accross versions that blend practices of <strong>agile with a traditional Waterfall</strong> approach. While agile project management follows a repetitive development and is flexible, the traditional follows a step-by-step development process and needs meticulous planning. Hybrid methods exploit the strengths of both to achieve a predefined project schedule, yet remain flexible within the processes — through a cycled process with multiple testing and feedback loops.</p><p>Another hybrid method would be a combination of Scrum and Kanban — <strong>Scrumban</strong> so to say — merging the best features of both, to enable a flexible development that can be adapted to changing situations and continuessly improving the processes with a strikt work-in-progress-limit.</p><p>It is worth mentioning that the choice of the features of the hybrid framework may vary according to the project.</p><p>According to the <a href="https://www.stateofagile.com/?_ga=2.21791611.1722161558.1580983051-906675326.1580983051#ufh-i-521251909-13th-annual-state-of-agile-report/473508">13th Annual State of Agile Report</a>, Scrum, and other hybrid/multiple (68%) continue to be the most common methodologies used by respondents’ organizations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*T36Qxpu-iVYrhk2z.png" /></figure><h3>Agile methods and project management tools</h3><p>There are various tools on the market that support agile methods. For Scrum Jira is one of the most common ones, though being a quite complex solution it might not be the right choice for every team, especially as teams seek an intuitive tool that can be easily used by all team members.</p><p>In addition to the high level of data security, Stackfield’s greatest advantages include its high degree of flexibility and ease of use. The range of functions within the individual rooms as well as cross-organizational features can be individually combined and restricted, so that the platform is always only as extensive as the work within the respective team and organization requires it to be.</p><p>The <strong>Kanban Board</strong> can be used to store backlogs, visualize circular workflows and support agile working methods. At the same time, you can define specific approval workflows with firm rules on what status a task should have after it has been processed and by whom it should be approved. In this way, the processing of tasks can be implemented in a structured manner.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*Vb1tvwvXxle5MgH5.jpg" /></figure><p>You can comment on all elements, be they tasks, pages or deadlines, and attach files to them. The <strong>communication</strong> module provides an exact chronological history of all actions and the entire exchange within the team. At the same time, the exchange on an element can always be accessed via the element itself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*OAxKJ_U6jI5Paivy.jpg" /></figure><p><strong>Task cards</strong> can be customized to exactly fit the way the team works using the custom fields. Use checklists, create drop-down selection lists or add additional fields for dates, texts and descriptions, numbers or another user selection. This way, all important information can be stored clearly and according to the subject matter dealt with in the room.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*vsqrIF3J9XcH4kAd.jpg" /></figure><p>With the help of the Gantt chart, you can create a project schedule that shows a precise sequence for tasks, including all dependencies and milestones. This allows you to quickly and easily determine bottlenecks or opportunities for optimization, while maintaining an at-a-glance view of the project’s overall progress.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*NUJAVXqhrpueGHb8.jpg" /></figure><p>Stackfield is a comprehensive <a href="https://www.stackfield.com/blog/project-managementsoftware-compared-75">project management software</a> with <a href="https://www.stackfield.com/security">highest security measures</a> and German company and server locations, that remains as lightweight as possible despite its wide range of functions.</p><p>Our <a href="https://www.stackfield.com/tour">product page</a> gives you a more detailed impression of the tools Stackfield provides.</p><p>Choosing the right project management methodology may not be easy. When making your decision, take into account the strengths and weaknesses of the individual methods as well as those of the project itself. A generalization is hardly possible, since one method cannot be classified as good or bad across the board. It can rather be better or worse adapted to certain requirements than another. Hybrid methods in individual configurations may be necessary to optimally meet the needs of a project. An agile approach often makes sense in project management, and those who know their project and take a closer look at its characteristics are very likely to find aspects in it where agile project management adds value.</p><p><em>Originally published at </em><a href="https://www.stackfield.com/blog/agile-project-management-127"><em>https://www.stackfield.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ca13b09a37ec" width="1" height="1" alt=""><hr><p><a href="https://medium.com/stackfield-stories/lets-get-down-to-the-basics-with-agile-project-management-ca13b09a37ec">Let’s get down to the basics with agile project management</a> was originally published in <a href="https://medium.com/stackfield-stories">Startup stories about the experiences and the mistakes we have made.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Microproductivity: why small steps will lead you to big wins]]></title>
            <link>https://medium.com/@lenawimmer_59268/microproductivity-why-small-steps-will-lead-you-to-big-wins-322ce092d7b1?source=rss-b269a15ec89a------2</link>
            <guid isPermaLink="false">https://medium.com/p/322ce092d7b1</guid>
            <category><![CDATA[newwork]]></category>
            <category><![CDATA[work-life-balance]]></category>
            <category><![CDATA[task-management]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[efficiency]]></category>
            <dc:creator><![CDATA[Lena Wimmer]]></dc:creator>
            <pubDate>Thu, 06 May 2021 14:25:10 GMT</pubDate>
            <atom:updated>2021-05-06T14:25:10.951Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*WJt1Xs8ovEIvRs_r9Zrzsg.png" /></figure><p>There are some questions that keep crossing our minds… What came first: the egg or the chicken? Why do I need 5 cups of coffee to feel like a person? <em>Why is this guy having a great time at the lake while I have a whole bunch of work ahead of me? Seriously…why!!!</em> We’re still not sure about the answers to the first two questions, but we may have some clue as for the latter.</p><p>It may be hard to admit, but “this guy” might simply be a little bit more efficient in what he is doing. Then again, maybe the difference is in the nature of his tasks — lots of small tasks that can be processed rather quickly, not the monster task you’re pushing in front of you. Either way… microproductivity is your answer.</p><h3>What is microproductivity?</h3><p>MicroWHAT? Playing buzzword bingo is not our intention so, in a nutshell, microproductivity describes nothing more than breaking down large, monster tasks into several smaller tasks. Smaller tasks usually take less time and they clearly require less effort. Processing them is much easier for you, not least because you can enjoy the achievement of a goal or a small success after each small task. You have a series of “quick wins” that will continually reduce the amount of work you have to do.</p><p>“But the effort is the same, isn’t it?” you may ask. That’s true, of course, but…</p><p>Let’s say you want to exercise a little more and get in shape before summer, which is why you’ve set a goal of completing 100 squats every day. At first, 100 squats sound almost impossible to accomplish. However, what if you split those 100 squats into 5 sets of 20 squats each? Twenty squats…even my weaker self thinks that’s doable.</p><p>There’s a reason for sayings like, “Small steps also lead to success.”</p><h3>Why does microproductivity work?</h3><h3>Microproductivity provides your brain with a reset button</h3><p>Although our brains are quite limited when it comes to focusing on many things at once or simply keeping them on demand (thanks to <a href="https://www.stackfield.com/blog/information-overload-92">information overload</a>), microproductivity gives us access to a kind of reset button right inside our heads.</p><p>If we dive right into one of these monster tasks, we’ll invariably get to the point where we’re completely absent-mindedly staring into space, wondering “What was I about to do?”. What’s next on the agenda? How did I actually get here???”.</p><p>All joking aside… our brain is simply overwhelmed when we burden it with too much at once. It tumbles from one unfinished task to the next until another one pops up. We break off what we’re about to do and work our way into the next subject area. “Wasn’t there something else we were supposed to be doing?” Productivity works differently and this is exactly the reason <a href="https://www.stackfield.com/blog/the-5-best-kanban-board-tools-80">why Kanban prohibits multitasking</a>. Not only do we repeatedly tear ourselves out of focus in such moments, we also create moments in which we allow ourselves to be distracted.</p><p>Small to-dos provide a remedy because we can fully focus on working through one at a time. We hit our reset button and we can ignore everything that has nothing to do with the current task.</p><p>Of course, being human, we are not able to memorize long lists of small subtasks either, which is why you should write them down, for example on a <a href="https://www.stackfield.com/blog/update-advanced-subtasks-and-text-formatting-64">subtask checklist in Stackfield’s task cards</a>.</p><h3>We are all goal-oriented workers</h3><p>The best part is that with each task we check off, we have achieved a goal. We should not underestimate the psychological impact that this set check mark has.</p><p>When we feel progress and notice that something is moving, we also become more motivated, because reaching a goal (no matter how small the goal) <a href="https://www.news-medical.net/health/Dopamine-Functions.aspx">releases dopamine, which evokes positive emotions</a>. We want to see results — maybe even adulate ourselves a little — soon and as often as possible. To achieve that, we will work with more vigor toward our next goal. You see, our own motivation can be controlled and thus can have an immense impact on our success. Those who are constantly struggling with big tasks simply miss this opportunity.</p><p>With small goals, we also have the opportunity to better define individual work steps, because the monster task itself provides little guidance. So instead of desperately trying to implement the instruction “Create a new pricing page”, you define precise work steps that guide you during execution: “Design a precise listing with the different services provided with product A in one hour”.</p><h3>Microproductivity opens up for feedback and check-ups</h3><p>There are two ways to approach tasks.</p><p>The “Let’s see how it goes” one, is the first. In other words, simply jump into a task, start working, then react to the circumstances and act accordingly.</p><p>Then again, quite a few of us are more prone to thinking everything through in detail beforehand. We don’t want to just “somehow” complete tasks. What we undertake should have reason, so we don’t have to make corrections later on. People who act this way also tend to procrastinate more. They simply don’t know where to start because they are looking for the perfect springboard.</p><p>If you think about it, it makes a lot of sense that many people act according to the latter approach: subtasks build on each other. If we make a mistake, we might have to do a lot of corrections and we’ll have done a whole bunch of work for nothing. On the other hand, of course, you can get lost in the musings, especially if it’s one of those huge monster tasks that you’re dealing with.</p><p>This is where microproductivity comes in: When you break large undertakings into smaller subtasks, you don’t have to think everything through right away. After each subtask, you can check the result and get feedback. This way, you don’t lose the entire project in case it turns out that you’ve gone astray. If project management methods like <a href="https://www.stackfield.com/blog/scrum-versus-kanban-79">Scrum</a> come to your mind at this point, you are absolutely right and know exactly how important reviews of intermediate results and feedback loops can be for the overall success.</p><h3>How to efficiently implement microproductivity and make progress visible</h3><p>Reading about strategies to increase productivity is one thing, but implementing them is quite another. How about in this case? Actually, microproductivity is quite easy to integrate into your work processes if you take advantage of the right features.</p><p>In any case, its most important to optimally visualize all intermediate goals and results, as well as subtasks, because this way you’ll be reminded of all successes and able to keep track of everything as it progresses.</p><p>This is what microproductivity can look like:</p><h3>You work with subtasks</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*XjVEY_TP_BBE7r8W.jpg" /></figure><p>For tasks that require multiple steps to complete and include multiple components, it’s best to create a list of subtasks. They will be listed as checklists in Stackfields tasks so you can easily check them off once completed. All the key details that define the individual work steps can be added to the indivdual subtask in form of a description, a comment and a file. The great thing about it: Your task will continuously show the progress you have made by displaying a small progress bar. Only three more to go … two … one … done!</p><p><strong>Tip</strong>: You can assign and date subtasks individually. This makes it easy to <a href="https://www.stackfield.com/blog/10-tasks-to-delegate-91">delegate parts of the task</a>. After all, microproductivity is not micromanagement and therefore you should be able to hand over tasks from time to time once the workload grows out of hand.</p><h3>You create multiple tasks and relate them to each other.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*EEqJnhRWHf_DYgm1.jpg" /></figure><p>Sometimes it is not so easy to determine whether a task is actually a subtask or not, because most processes are interrelated at some point or another. For work steps that are too complex to be recorded as subtasks, it may be useful to create a separate task card instead.</p><p>In order to maintain connections, you can work with labels and links or you can set the tasks in dependency to each other. This way you can keep track of the order in which tasks have to be completed. Activate the timeline module in the room settings. This will also allow you to track all tasks on a timeline later on.</p><p>Whether you end up working with subtasks or multiple task cards depends entirely on the type of tasks and your internal processes. Find the easiest and most transparent way for you.</p><h3>You visualize great projects using sprints and milestones</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*5vV66eSo1SWlmSps.jpg" /></figure><p>When it comes to <a href="https://www.stackfield.com/project-management">project management</a>, microproductivity is a must. Here, the goal is to achieve a project goal in a given timeframe and within a set budget, which requires smooth collaboration with a high degree of transparency and precise scheduling. <a href="https://www.stackfield.com/blog/scrum-versus-kanban-79">Scrum and Kanban</a> were not mentioned in this article by accident. Modern project management methods rely on detailed structuring of task processes to prevent exactly what also microproductivity is supposed to prevent: reduced productivity due to an overwhelming workload.</p><p>Projects will be visualized in project rooms that are specially designed for this purpose. They contain a number of additional features that support process tracking, allowing you to better monitor progress. Again, use the Gantt chart to record dependencies between tasks and highlight important milestones.</p><p><a href="https://www.stackfield.com/blog/project-management-methods-88">Project management methodologies</a> such as Scrum, that rely on sprints, support microproductivity not only for individuals but for entire teams, allowing them to work with focus, at set intervals, to achieve defined intermediate deliverables.</p><p>Ultimately, comprehensive project management requires a combination of the aforementioned features to increase microproductivity: From the team’s perspective, the project becomes more tangible by dividing up the processes, while individual project participants optimize the processing of their tasks.</p><p>By introducing microproductivity into our work processes, we can keep larger tasks manageable and make them easier to accomplish. The psychological impact this approach has on us can positively influence progress — and significantly at that. Those who can see the “light at the end of the tunnel” and define their work steps in detail right from the start are less inclined to procrastinate. Of course, this can be scientifically proven, but basically we all know it from our own experience.</p><p><em>Originally published at </em><a href="https://www.stackfield.com/blog/microproductivity-130"><em>https://www.stackfield.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=322ce092d7b1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why all-in-one tools are the future of collaboration!]]></title>
            <link>https://medium.com/stackfield-stories/why-all-in-one-tools-are-the-future-of-collaboration-ed61dfa1083e?source=rss-b269a15ec89a------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed61dfa1083e</guid>
            <category><![CDATA[collaboration-tools]]></category>
            <category><![CDATA[all-in-one-platform]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[team-collaboration]]></category>
            <category><![CDATA[collaboration]]></category>
            <dc:creator><![CDATA[Lena Wimmer]]></dc:creator>
            <pubDate>Wed, 03 Feb 2021 11:16:26 GMT</pubDate>
            <atom:updated>2021-02-04T10:01:16.902Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*Zj_cJe78GkjY7OXxSezqYA.png" /></figure><p>What we realized during our last video call: We talk so much about digitalization, but we rarely think about what it has done to the business world during the last few years. You just follow the trend. You adapt to the environment. You are somehow part of the process.</p><p><em>“Lately I’ve been thinking a lot about how different things were just ten years ago,”</em> said one colleague.</p><p>Right. Ten years ago, I started my day by processing orders, all printed, of course, I spent at least one-fifth of the day in front of the scanner and copier, and the rest of the day was mainly processing e-mails … and lots of e-mails. Emails are still part of the day, but they have become less.</p><p><em>“I remember that my former colleague always helped me to decipher the work instructions of my boss. They always ended up on tiny post-its somewhere on my desk — horrible handwriting. And then you just sit there and you don’t know whether you have to prepare anything for the upcoming conference or go and get some canapés.”</em></p><p>My team was quite amused, when I told them about that. However, I wasn’t back then. Today, everything simply ends up in a digital tool, where it’s easy to find and — fortunately — the handwriting of your boss is no longer an issue.</p><p>But there are other problems today. I often hear that companies use many different collaboration tools for different collaboration purposes: Chat tools, task management tools, file storage solutions… all tailored to their specific use. But teams still have problems with collaboration and communication.</p><p>Finally, we were also talking about what we imagine the future of collaboration to be like. Clear answer:</p><p><em>“All-in-one collaboration tools!”</em></p><p>Here is why…</p><h3>The future of collaboration: all-in-one tools</h3><p>Notes and analog writing pads with to-do lists are very rare nowadays. E-mail exchange is also slowly decreasing, as more advanced communication tools become increasingly popular in businesses. Especially internal collaboration is already based to a large extent on digital collaboration tools.</p><p>The business world is trying to digitalize itself step by step and cloud collaboration tools are contributing to this to a particularly large extent. By using them, companies can improve the quality of their collaboration, increase their efficiency, retrieve information on a time and location-dependent basis and thus enable employees to work from home or remotely.</p><p>There are various tools on the market that are specialized for different purposes. Functionality and scope differ, sometimes dramatically. Teams use chat tools, meeting tools for audio and video conferencing, task management tools and methodically tailored <a href="https://www.stackfield.com/blog/project-managementsoftware-compared-75">software for project management</a>.</p><p>So far, there are still many isolated solutions in use, i.e. an organization uses several collaboration tools (often from different providers) for its specific areas of collaboration.</p><h3>Less is not always more: the 5 most common problems caused by isolated solutions</h3><p>There are companies that use Slack as a team chat, manage tasks with asana, phone via zoom and edit documents via Google Docs. These tools fulfill their respective purpose, no doubt. However, a hodgepodge of different tools for different purposes leads to a fragmentation of the individual work areas — thus causing significant productivity problems. Less is not always more. This is just the logical conclusion and it has been confirmed by numerous discussions we had with our customers.</p><ul><li><strong>Collaboration across different platforms forces users to constantly switch from one solution to another</strong>. This makes concentrated and focused work difficult.</li><li><strong>Users have to familiarize themselves with different user interfaces</strong>. This takes a lot of time, frustrates employees and leads to work processes not being as smooth as they could and should be.</li><li><strong>Information is scattered across different platforms making it difficult for users to keep it all in context</strong>. The task is located in the Kanban tool, but important information is communicated via a separate chat tool, documents end up in the cloud storage service, etc. How likely is it then to miss important information while working on something?</li><li><strong>The user and rights management will be complicated</strong>. Changes in team composition or in the area of responsibility of individual employees require access and editing rights to be assigned, adjusted and removed in several tools.</li><li><strong>You will need access and licenses for each tool</strong>. This usually means more effort in accounting and higher costs.</li></ul><h3>The most simple but decisive advantage of all-in-one collaboration tools</h3><p>For organizations that use all-in-one collaboration tools, many things are easier. For them, the problems caused by the fragmentation of individual work areas simply do not exist. All activities that take place in the team or within the organization are uniformly represented on one platform and related to each other. This way, it is possible to maintain correlations, while avoiding time-consuming research work.</p><h3>A good all-in-one collaboration tool is not the jack of all trades device</h3><p>When we talk about all-in-one collaboration tools, we are certainly not talking about a tool replacing every software solution that companies need. Such a tool would be too complex and unable to adequately map the individual functional areas. So keep your hands away from the jack of all trades device, that offers you both <a href="https://www.stackfield.com/blog/the-best-accounting-tools-compared-96">accounting</a> and project management. However, the tool should cover all the functions that employees need to work together on a daily basis, without neglecting communication.</p><h3>No alternative to all-in-one collaboration tools: integrations</h3><p>Some providers of collaboration tools address this problem by offering integration tools. In this case, a plattform provides interfaces to other tools. Hence, users can access the tools of other providers from one collaboration tool without having to change the platform. Now, are integrations a solution? Unfortunately not, because the integrations only provide access points to the tools in the platform. However, they do not provide a direct link between the differen functions of all tools. In everyday life this means:</p><p>Files can be stored in the respective solution, but they are not attached to the corresponding tasks. Commenting on files or other items may not work, or it may not appear in the message stream of the chat service.</p><p><strong>Flaws of integration tools in a nutshell</strong></p><ul><li>Integrations work separately from the functional area of the other tools. Users have to manually relate information (i.e. copy or link information from one collaboration tool to that of the others). This is inconvenient and time-consuming.</li><li>Integrations that are provided for other tools usually represent only a part of the functional range of the actual tool. To use the full functionality,you still need to use the collaboration tool separately.</li><li>You still have to define access rights individually for all tools.</li></ul><h3>What functions should the collaboration tool cover?</h3><p>To optimally illustrate the everyday work of the individual teams and to avoid any problems caused by a fragmentation of the different work areas, the tool should have a certain range of functions and reasonably link the tools with each other. This is what the collaboration tool should cover:</p><h3>Task management</h3><p>A suitable module for task management with detailed task cards is the cornerstone of a good collaboration tool. It should enable employees to enter individual tasks clearly and assign them to one or more people in charge.</p><p>Pay attention to the following features:</p><p><strong>Breakdown into subtasks</strong>: Not all tasks will be completed by a single person. Often, several team members are involved in the completion of one task, which is why it is essential to have the option of creating subtasks that can be provided with information separately and assigned individually.</p><p><strong>Flexible status options</strong>: The status options of a task should be individually customizable in order to optimally adapt the workflow to the internal processes of the team or company.</p><p><strong>File attachments and comments</strong>: In order to avoid having to search for related documents first and to keep all information centrally available, it should be possible to attach files and comments to the task — and in the best case also separately to the subtasks.</p><p><strong>Easy dating</strong>: Tasks should offer the possibility to provide a due date, a due period and an option to automatically re-create recurring tasks.</p><p><strong>Order with labels</strong>: Labels are used to organize tasks into certain categories. This makes it easier to sort, prioritize and differentiate them later.</p><h3>Task visualization/project views</h3><p>The more complex the workflows in a team are and the more extensive the projects are, the more attention you should pay to ensure that they can be clearly visualized. The most common types of project views, that are used in most teams:</p><p><strong>Kanban Board</strong>: The visual task board is probably the one most frequently used in companies, because it allows all workflows to be visualized easily and clearly.</p><p><strong>Todo lists</strong>: Lists may be the easiest way to record all tasks. However, as the number of tasks increases, they can get quite chaotic, which is why they are only suitable for personal todos and projects of a very small scope.</p><p><strong>Gantt Charts</strong>: Often referred to as timelines by providers of collaboration tools, <a href="https://www.stackfield.com/blog/gantt-charts-basics-116">Gantt Charts help to visualize a project plan in its temporal context</a>. The diagram provides information about task dependencies, potential bottlenecks in planning and helps teams to complete all tasks in time.</p><h3>File and knowledge management</h3><p>The exchange and collaborative handling of files and documents is part of everyday work in every company. Also, you should be able to centrally record all other basic information about collaboration or projects and guidelines. Hence, file management and knowledge management are two components that shouldn’t be missing in a collaboration tool.</p><p><strong>File management</strong>: You should be able to attach files to any other elements (such as tasks, appointments and other files) and comment on them individually. This way, users always have information ready to hand and can later easily see what belongs together.</p><p><strong>Wiki pages</strong>: Wiki pages can be used to centrally record project plans and goals, basic information concerning team collaboration, guidelines or frequently used key data and standard texts for all members. Since they make teamwork much easier, they should be the standard in a collaboration tool.</p><h3>Communication</h3><p>Most collaboration tools ignore this aspect. However, communication in particular is an area that shouldn’t be outsourced to a separate tool. Why? Important information and decisions on specific tasks and processes have to be directly visible at all times. If they are distributed across different platforms, the risk of overlooking essential information increases. This is what the collaboration tool should be designed for:</p><p><strong>Systematic exchange through commenting</strong>: All elements, be it tasks, files, documents or appointments, should provide the option to individually comment on them. This is the only way to ensure that no misunderstandings occur in communication, that important information remains visible and that all key data on a certain topic can be accessed with a single click.</p><p><strong>Project or topic-related communication via Team Chat</strong>: Individual departments and project groups should have their own area where they can exchange information on specific topics. A Team Chat, which is linked to the respective work areas, fulfills this purpose in the best possible way. Here, members should be informed about all new activities and messages from team members.</p><p><strong>Topic-independent exchange via direct messages</strong>: In addition to the topic-related team chat, private chats and group chats provide space for conversations that cannot be assigned to a specific area. In this way, only the relevant information ends up in the team chat and the message stream remains clear at all times.</p><p><strong>Audio and video calls and screen transmission</strong>: As soon as there is a greater need to talk about certain things, it makes sense to seek direct conversation. However, if participants are in different locations, e.g. due to home office regulations, this is not always possible. <a href="https://www.stackfield.com/blog/group-calls-audio-video-110">Conference calls</a> are an excellent alternative in these cases. A screen-sharing function allows for more detailed discussion of specific documents and the like.</p><h3>Scheduling</h3><p>Finally, a <strong>calendar function</strong> should be an integral part of a collaboration tool to enable users to schedule appointments and view them at any time.</p><h3>Project tracking</h3><p>Those who frequently carry out projects should also be able to track their progress. Some collaboration tools that are specifically designed for <a href="https://www.stackfield.com/project-management">project management</a> therefore offer useful <strong>tracking features</strong>. These include project-related diagrams and overviews that highlight all key data and status updates.</p><h3>How does Stackfield support you as an all-in-one collaboration tool?</h3><p><a href="https://www.stackfield.com/tour">Stackfield combines tools from various work areas</a> and links them to each other through functional connections. Thus, the platform enables a smooth collaboration between colleagues of individual teams, but also between employees of different departments.</p><h3>Stackfield is a project management software</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*3CjClSt7XrBB28W6.jpg" /></figure><p>… with <a href="https://www.stackfield.com/help/using-project-rooms-2093">project rooms</a> specially designed for project work, various project views and detailed diagrams that provide information on the progress of the project.</p><h3>Stackfield integrates file and document management</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*cxJy2pbQwFINswmG.jpg" /></figure><p>… and succeeds to make collaboration as easy as possible. Users simply attach <a href="https://www.stackfield.com/help/working-with-files-2015">files</a> to the corresponding element (tasks, appointments, pages, files, etc.) to store them in a central and easily to find location. The <em>Files</em> module will collect all files that are stored within a room. There you can search and sort them but also organize them in folders.</p><h3>Stackfield is a communication solution</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*dI5uoL5Mt4ANCZJL.jpg" /></figure><p>… and offers all channels for teams to exchange information in the best possible way. The room-specific Team Chat informs members about all new activities. <a href="https://www.stackfield.com/help/direct-messages-2076">Private chats and group chats allow for room independent communication</a>. <a href="https://www.stackfield.com/help/audio-video-calls-2077">Audio and video calls</a> (incl. Conference option + screen transmission) facilitate remote communication. This makes Stackfield also perfect for home office collaboration.</p><h3>Stackfield remains flexible and as lightweight as can be</h3><p>… because you can simply switch off any function modules that you don’t need. This way, the platform adapts optimally to the needs of different departments and teams within the same organization.</p><h3>On top: Stackfield is GDPR compliant and protects all data according to German security standards.</h3><p>That’s what makes Stackfield so secure:</p><ul><li>German company location,</li><li>German server location,</li><li>restricted to sub-contractors from the European area</li></ul><p><strong>Stackfield is not affected by the Cloud Act. The usage is GDPR compliant.</strong> <strong>Stackfield takes every precaution to ensure the best possible protection of user data.</strong></p><p>The future of collaboration is all-in-one tools that combine all core functions and put them into context. They ensure that information is centrally accessible and can no longer be missed. This type of collaboration tool makes working with digital solutions easier, not more complicated. That being said, I’ll go get some canapés.</p><p><em>Originally published at </em><a href="https://www.stackfield.com/blog/all-in-one-collaboration-tools-121"><em>https://www.stackfield.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed61dfa1083e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/stackfield-stories/why-all-in-one-tools-are-the-future-of-collaboration-ed61dfa1083e">Why all-in-one tools are the future of collaboration!</a> was originally published in <a href="https://medium.com/stackfield-stories">Startup stories about the experiences and the mistakes we have made.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why defining the project scope is crucial for projects]]></title>
            <link>https://medium.com/stackfield-stories/why-defining-the-project-scope-is-crucial-for-projects-ff382f21c177?source=rss-b269a15ec89a------2</link>
            <guid isPermaLink="false">https://medium.com/p/ff382f21c177</guid>
            <category><![CDATA[project-management-tool]]></category>
            <category><![CDATA[scope-management]]></category>
            <category><![CDATA[projects]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[project-manager]]></category>
            <dc:creator><![CDATA[Lena Wimmer]]></dc:creator>
            <pubDate>Thu, 21 Jan 2021 15:02:31 GMT</pubDate>
            <atom:updated>2021-01-21T15:02:31.381Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*72HB9yPrz9BG_w4s0pQuOQ.png" /></figure><p>Let’s imagine you’re developing a product for a customer. Of course you want your product to be absolutely mind-blowing, so you and your whole project team are constantly working on a number of features that make the product unique. Unfortunately, not everything goes according to plan and the project is delayed. Employees are exhausted. The project is over budget. The client wanted a simple solution and everything you and your team worked on makes the product more complex. Do you think the customer is satisfied? No?</p><p>Obviously not, because you exceeded the project scope by far, took up more time, caused additional costs and, to make matters worse, you ignored the requirements of your target group.</p><p>And the moral of this story: you don’t ignore the definition of the project scope in <a href="https://www.stackfield.com/project-management">project management</a>! You just don’t!</p><p>Learn how to easily define a project scope:</p><h3>What is the project scope and what isn’t?</h3><p>The most common problems in project management occur where project teams did not or did not clearly define the project scope. This is where uncertainty and misunderstandings arise. Then communication suffers. As long as you take enogh time to clearly define the project scope in advance, you know the requirements that are part of the project and those that are not. This may sound rather trivial, but it is absolutely essential.</p><p>First of all, keep in mind that you might come across two similar-looking but completely different concepts: product scope and project scope.</p><p>The product scope refers to all requirements that the product has to meet. It addresses the What: “What needs to be implemented in the course of the project? What does the final product contain?”.</p><p>The project scope is primarily concerned with the How: “How can all those requirements be implemented?”.</p><p>Both product and project scope naturally go hand in hand: the project scope cannot be described without a precise evaluation of the product scope. The product scope is therefore also part of the project scope.</p><p>Typically, all the project scope is defined in a project scope statement.</p><h3>This is how the project scope statement is structured</h3><p>The Project Scope Statement is used to define all project requirements in a uniform and consistent manner for all participants. These include:</p><h3>Justification</h3><p>If you want to carry out a project, there is usually a reason for this. A project needs its right to exist and this should be explicitly stated within the description. What needs does the project address and what problems does it have to solve?</p><h3>Product scope description</h3><p>The product requirements catalog is the central set of rules for each project, from which all project participants can clearly see what needs to be done and what doesn’t. The description forms a framework for the project that should not be broken. It sets limits to the team in the (creative) implementation of the requirements, thus preventing the project from being jeopardized by means of a scope creep.</p><h3>Acceptance criteria</h3><p>How is “Done” defined? In order to be able to better follow and interpret the process later on, certain criteria must be defined, according to which it is possible to judge whether goals have been achieved or not, or whether requirements are considered “done” or not. In this process, it is also important to be aware of the wishes and expectations of the target group, which is why the acceptance criteria include aspects such as price, quality and benefits.</p><h3>Objectives and Deliverables</h3><p>The definition of objectives for projects is often carried out on the basis of guidelines, whereby mostly guidelines according to the SMART or CLEAR principle are used.</p><p>SMART goals must be specific, measurable, achievable and realistic, relevant and time-bound.</p><p>CLEAR-Goals must be collaborative (support team collaboration), limited (in time and scope), emotional (inspire and motivate the team), appreciable (feasible and achievable in small steps) and refinable.</p><h3>Exclusions</h3><p>Most of the planning is concerned with the listing of goals and requirements that are supposed to be part of the project. Equally important is to determine what the project will definitely not include. A typical example from our everyday life as software providers: Our projects aim to introduce new functions. Future updates are initially not part of our initial time-limited project.</p><h3>Constraints</h3><p>The magic triangle in project management — scope, time and budget — draws clear boundaries for the project. The project is defined by these three components. If one of the variables changes, the other two will inevitably change as well. For example, if the scope of the project needs to be expanded, it will require more time and/or incur additional costs due to an increased need for resources.</p><h3>Assumptions</h3><p>The purpose of projects is to create something new. Therefore, a project team always enters unknown territory where it can only guess at certain events and developments. The way to deal with uncertainties in project management is to make assumptions — i.e. statements that are considered true or likely. It is particularly important to record assumptions because they also indicate the risks of the project. If the team knows about the risks in early stages, they can react quickly.</p><p>The fundamental principles for defining the project scope can be easily internalized. But this is only the beginning. It is one thing to initially define the project scope. Keeping it during the project is a completely different challenge. Where are the pitfalls?</p><h3>The biggest challenges in project scope management</h3><h3>Scope Creeps</h3><p>What does it actually look like in your kitchen sink? No longer used as a sink because the plates and cups and bowls pile up? “ So what? There’s still room for one more thing!” This is a typical case of “Kitchen Sink Syndrome”, which unfortunately is also a problem in project management. During implementation, the project scope increases further and further, uncontrolled and seemingly unstoppable. A so-called Scope Creep — and yes, it is actually also known as the Kitchen Sink Syndrome — develops and becomes a massive threat to the success of the project. Anyone who has been sloppy in identifying the requirements is almost certain to run right into one. But how can it be prevented?</p><p><strong>Rely on clarity</strong>: Perhaps this job seems to be nothing but time consuming and tedious. However, let me tell you one thing: just do it. Keep the requirements and goals as detailed and clear as possible.</p><p><strong>Trust in processes</strong>: Many of your ideas are reasonable, no doubt. But if you add too many new requirements, it can easily happen that you lose sight of the main goal. An idea that is worthwhile for project teams that create updated product variations: Maybe one or the other requirement is better off in the next upgraded version?</p><p><strong>Avoide upgrade traps</strong>: Viele Deiner Ideen sind sinnvoll, keine Frage. Werden aber zu viele neue Anforderungen aufgenommen, kann es leicht passieren, das Hauptziel aus den Augen zu verlieren. Ein Gedanke, der sich für Projektteams lohnt, die erneuerte Produktvariationen schaffen: Vielleicht ist die ein oder andere Anforderung im nächsten Upgrade bzw. der nächsten Version besser aufgehoben?</p><p><strong>Keep communication alive</strong>: Communication is crucial in so many ways: Important information regarding the project scope should be clearly communicated within the team. The team should always have access to it and it should be able to report problems as they occur. A digital communication solution simplifies many things.</p><p><a href="https://www.stackfield.com/blog/scope-creep-prevention-112">I would like to learn more about what Scope Creeps are and how they can be prevented.</a></p><h3>Missing tools</h3><p>You may have helpful processes in mind and you are probably aware of all the dangers that may arise during your journey. However, if you do not have the right tool, you will not be able to react immediately. Compare project management software and choose the one that supports you best.</p><p>In this way, Stackfield will help you plan the scope of the project and execute it successfully:</p><p><strong>Document the project scope on wiki pages</strong></p><p>Ensure that all important information about the project — especially the project scope — is clearly defined and centrally accessible for everyone. Wiki pages provide the perfect place for this. They can be commented and provided with files and links. The versioning function helps to keep changes to the plans transparent.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*eZun0SwbY0-wokGR.jpg" /></figure><p><strong>Clearly define requirements and process them with your team</strong></p><p>All requirements can be stored within functional task cards, scheduled, assigned to one or more members and provided with all necessary information. You can create subtasks, attach files and documents, and create entries for time recording.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*cMTg9CVz04DZ0Hzv.jpg" /></figure><p>Lists provide a simple overview of all tasks. The customizable <a href="https://www.stackfield.com/blog/the-5-best-kanban-board-tools-80">Kanban Board</a> supports the individual workflows of your team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*AerITbkNdI4tNCp7.jpg" /></figure><p><strong>Track progress with ease</strong></p><p>The <a href="https://www.stackfield.com/blog/gantt-charts-basics-116">Gantt Chart</a> ensures that the process runs as smoothly as possible. Here you will find all tasks in their chronological sequence. You can see exactly where the project should be according to plan and where it actually is. You can highlight important intermediate goals as milestones and dependencies provide information about the extent to which changes to individual tasks will affect the entire project. This is how you are always able to react as soon as possible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*23onQkD7YanFX_t_.jpg" /></figure><p><a href="https://www.stackfield.com/help/using-project-rooms-2093"><em>Project Rooms</em></a> hold all key data about the project and various graphics that support you in tracking the project. The project-specific overview shows the current status of the project. Based on the start and end dates and taking into account the progress of the project, you can see at a glance whether the team is on schedule.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*W9pZkz6iE_JRigZm.gif" /></figure><p><strong>Communicate clearly and give direct feedback</strong></p><p>The real-time chat keeps the project team up to date on all activities and news.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*GM0eW6tcg1--iRZE.jpg" /></figure><p>All elements can be commented individually. Together with the clever linking of the various functional modules, this ensures that information is easy to find and that communication is always topic-related. This not only facilitates project communication in general, but also remote collaboration.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*zqueVYLhEZXveob2.jpg" /></figure><p><strong>Centrally provide and share files</strong></p><p><a href="https://www.stackfield.com/help/working-with-files-2015">Files</a> can be attached to any kind of element. At the same time they will be <a href="https://www.stackfield.com/blog/8-secure-cloud-storage-services-68">stored together with all other files</a> within a room within the Files module. The marker function enables employees to discuss image contents systematically.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*4JsB2MGjbjtf3Brf.jpg" /></figure><p>If files are attached to tasks, marker comments are listed directly in the task cards, where they can be checked off after clarification.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*GsjgzvrG9nE9IdqL.jpg" /></figure><h3>A lack of human resources</h3><p>Another thing that you should think about right from the start: the team itself.</p><p>In the course of the project, it may turn out that the team lacks some professional skills. This is completely natural, because not everyone can do everything. For this reason, however, it is particularly important to define the required skill domains already in the project planning phase.</p><p>What you should definitely avoid is being forced to assign team members tasks according to their availability and not based on their personal skills.</p><p>You can best avoid this situation by assembling the <a href="https://www.stackfield.com/blog/project-management-roles-compared-99">project team</a> carefully in advance. Find the perfect person for each skill domain. If there are gaps, you need to strengthen the skills of your employees. Do not hesitate to offer training and further education. Employees are happy about the opportunity and the company will benefit sustainably from it in future projects.</p><h3>What have we learned about the project scope?</h3><p>There is one main conclusion we can draw: If you spend more time on planning at the beginning, you can probably save a lot of time later on in the project. A well-defined scope significantly increases the probability that the project will prove successful in the end. And to come back to the kitchen sink: Make piling plates an end!</p><p><em>Originally published at </em><a href="https://www.stackfield.com/blog/defining-the-project-scope-122"><em>https://www.stackfield.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ff382f21c177" width="1" height="1" alt=""><hr><p><a href="https://medium.com/stackfield-stories/why-defining-the-project-scope-is-crucial-for-projects-ff382f21c177">Why defining the project scope is crucial for projects</a> was originally published in <a href="https://medium.com/stackfield-stories">Startup stories about the experiences and the mistakes we have made.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating and using Gantt Charts]]></title>
            <link>https://medium.com/stackfield-stories/creating-and-using-gantt-charts-9dbe8cbc92c0?source=rss-b269a15ec89a------2</link>
            <guid isPermaLink="false">https://medium.com/p/9dbe8cbc92c0</guid>
            <category><![CDATA[gantt-chart]]></category>
            <category><![CDATA[project-management-tool]]></category>
            <category><![CDATA[timeline]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[collaboration-tools]]></category>
            <dc:creator><![CDATA[Lena Wimmer]]></dc:creator>
            <pubDate>Wed, 18 Nov 2020 11:13:07 GMT</pubDate>
            <atom:updated>2020-11-18T11:13:07.215Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*z1QEEdG2OhGFF9q5BzmtZQ.png" /></figure><p>Apart from a suitable project management method, the right tools are crucial for the success of projects. Deciding on one method and one or two tools can’t be that difficult. Well, one should at least think so.</p><p>Unfortunately, it often sounds easier than it actually is, especially when it comes to tools for task management. There are a few options: boards, lists, structure trees, timelines. But what tools do you actually need for your project? To shed some light on the subject, let’s take a closer look at a very popular tool today: the Gantt Chart.</p><p><strong>Note</strong>: The Gantt Chart is only one of the most popular project views. Its main focus is on the correct scheduling of processes within a project. To map workflows correctly, methods such as <a href="https://www.stackfield.com/blog/scrum-vs-kanban-79">Scrum oder Kanban</a> are suitable, which can be mapped with the help of a task board. In our blog, we also explain <a href="https://www.stackfield.com/de/blog/5-tolle-ideen-fuer-das-kanban-board-38">different use cases for the Kanban Board</a>.</p><h3>What is a Gantt Chart?</h3><p>A Gantt Chart is a bar chart, which is very often used in <a href="https://www.stackfield.com/project-management">project management</a> to graphically represent a project plan — with all activities and events in their chronological course. This also includes all deadlines and dependencies to other tasks.</p><p>The Gantt Chart was developed as early as 1912 by Henry L. Gantt, an American engineer. A clever man with clear visions, as it turned out. The planning of immense construction projects, for example, was illustrated with the help of Gantt Charts. Want an example? The Hoover Dam! An instrument that was used in the construction of a dam of this size is certainly helpful in other projects as well…</p><h3>What does a Gantt Chart show?</h3><p>… indeed: Gantt Charts are suitable for the illustration of various projects and their progress. With the help of the chart, the total duration of a project can be determined and team members can get a clear overview of the current status at any time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*Xlr1CCL_VE2ASGFp.jpg" /></figure><p>Basically, everything as Gantt revolves around axes: the vertical axis represents the activities/tasks/project steps, while the horizontal axis describes the chronological sequence. The correlation of the two parameters is now entered into this system in the form of bars. Depending on the duration of the activities, a different bar length can be observed.</p><p>. In addition to this classification, modern Gantt diagrams usually also contain a function to show the dependencies between individual project steps, responsibilities and milestones.</p><p>So can bar ranges also overlap? Of course, because tasks are often processed simultaneously.</p><h3>Now, what can I see from looking at a Gantt Chart?</h3><ul><li>the expected project duration: start and end</li><li>task/process duration: start and end of individual tasks/project steps</li><li>responsibilities of individual tasks</li><li>task description (title)</li><li>dependencies of individual tasks/ project steps</li></ul><h3>What does a Gantt Chart consist of?</h3><p>Depending on the project type or the software used, the terms may differ.</p><ul><li><strong>task list</strong>: is located on the vertical axis on the left side of the chart and lists all activities that are necessary to execute the project</li><li><strong>timeline</strong>: runs horizontally at the top of the diagram and represents a certain time span of the project</li><li><strong>dateline</strong>: runs vertically and displays the current date or time during the course of the project</li><li><strong>task bars</strong>: run horizontally within the diagram and represent the tasks, their duration and deadlines</li><li><strong>milestones</strong>: accentuated elements representing important events and their deadlines (usually represented as a diamond)</li><li><strong>dependencies</strong>: linear linking elements between the tasks/process steps that define a fixed sequence</li></ul><h3>What are Gantt Charts used for? Use cases and advantages</h3><p>Gantt Charts are used in almost all industries and business areas, where the scheduling of individual tasks often depends on the completion of other tasks. Here are some examples of use:</p><ul><li>for complex projects for product launches (e.g. software development)</li><li>in event planning</li><li>to carry out PR/advertising or recruitment campaigns</li><li>and as already mentioned for construction projects</li></ul><p>Those who use a Gantt Chart want to benefit from certain advantages in the planning process. The Gantt Chart definitely supports you …</p><ul><li>to keep an eye on the progress of projects,</li><li>to identify potential bottlenecks,</li><li>to improve the schedule of the project,</li><li>to optimize the entire process structure,</li><li>to predict delays and</li><li>to keep all project participants on track.</li></ul><h3>What is the difference between the Gantt Chart and the calendar?</h3><p>At this point we would like to make it clear that a Gantt Chart is not a calendar view, since there is always some confusion. Both views focus on the time-related context, but the Gantt Chart deals very centrally with the connection between the individual work steps. While the calendar only provides individual weekly or monthly views for a better overview of daily tasks, the Gantt Chart gives the user a clear overview of how changes would affect other tasks and the overall progress of the project.</p><p>The following table illustrates the differences and gives hints in which cases the calendar or Gantt Chart is more suitable:</p><p>Process criteriaGantt ChartCalendar</p><p><strong>Time limits</strong></p><p>It is a project by general definition, i.e. with start and end dates.</p><p>The project is not explicitly limited in time, i. e. it is continuous.</p><p><strong>Monitoring</strong></p><p>The aim is to complete the overall project on schedule. The project progress should therefore be monitored.</p><p>The aim is to keep an overview of upcoming to-do’s. Therefore, only an overview of all currently pending tasks should be displayed.</p><p><strong>Task processes</strong></p><p>The project consists of a number of tasks, which often depend on other tasks and therefore have to be completed in a predetermined order. Deviations in the processing of one task would inevitably affect a number of other tasks.</p><p>Tasks related to the project are usually independent of the completion of other tasks. Deviations in the completion of one task would not affect other tasks or deadlines.</p><p><strong>Target group</strong></p><p>The view should serve as a tool for all stakeholders of the project to inform the respective groups of people about the current status.</p><p>The view is designed to give the team an instant overview of what tasks are currently in the pipeline.</p><p>Of course, in certain situations both views can be helpful. However, it is important to remember that the views have different purposes.</p><h3>What should you pay attention to when creating a Gantt Chart?</h3><p>If you want to support your project management with Gantt Charts, you should pay attention to a few things. As mentioned, the view is suitable for optimizing and continuously monitoring the time component of project management. This of course requires some preparation, which is why project planning before starting the project execution is especially important:</p><p>Requirements should be clearly defined and prioritized in advance. This is the only way to ensure that the timeline later shows an accurate outline of the project.</p><p>The first step in creating a Gantt Chart is always to create a project plan. This is an exact list of all tasks/process steps, with priorities, dependencies, duration and deadlines.</p><h3>How does a Gantt Chart Software help?</h3><p>The times when the project management process was supported by sticky notes are over. Today, a large part of the process is digital. Some <a href="https://www.stackfield.com/de/blog/projektmanagement-software-vergleich-75">project management software</a>, including Stackfield, offers their own Gantt Chart views. But what advantages does a Gantt software offer, for example in comparison to a traditional creation in Excel?</p><h3>Location and time independent access to the Gantt Chart</h3><p>The probably most obvious advantage of a Gantt software is especially shown with regard to the changing world of work. What we are currently experiencing is that distributed teams are becoming more and more standard, that home offices are becoming more and more popular in companies and that, due to globalization, even collaboration between managers in different time zones is no longer unusual.</p><p>If a cloud solution is used, managers can access the Gantt Chart at any time, no matter where they are. This makes work in (globally) distributed teams much easier and enables an effortless switch to the home office.</p><p>Stackfield is a German provider with a special focus on data protection and thus absolutely GDPR compliant.</p><h3>The software links Gantt Charts with the task management in the team</h3><p>The Gantt Chart does not stand alone in Stackfield — it is linked to other tools within the platform. For everyday work, this means that all updates within the team’s task management are also directly visible on the Gantt chart. If there are changes and delays in processing, the Gantt chart does not have to be updated separately. The software automatically takes over this part for you and keeps the progress and effects of changes visible for everyone.</p><h3>The Gantt Chart keeps everything centrally available</h3><p>Since the Gantt Chart is composed of the task cards, which in Stackfield contain all key data, files and documents, the corresponding information is also directly available via the Gantt Chart. Stackfield thus prevents the team members from having to switch between the different views too often.</p><h3>Gantt Software: How to create a Gantt Chart with Stackfield</h3><p><strong>Note</strong>: Note: To create a Gantt Chart in Stackfield, the corresponding <em>Timelines</em> module must be activated in the respective room. You will find this option under the tab “Modules” in the room settings, which can be opened by clicking on the room name.</p><p><a href="https://www.stackfield.com/de/blog/erstelle-einen-perfekten-projektplan-77">A detailed project plan</a> is essential for the creation of a Gantt Chart. Create a catalogue of requirements and think carefully about which tasks need to be done during the project. Be aware that three important components of the project — the scope, the resources and the time factor — are correlated. As soon as one of the components changes, the other two will inevitably be affected.</p><h3>Create a detailed list of tasks and prioritize</h3><p>In the first step you should create a list of all tasks as precise as possible. A division into larger process sections can be useful here. Think about what is necessary to complete each process and then formulate this in the form of tasks.</p><p>You can create tasks in Stackfield directly in the Timelines module or via the Communication, Calendar or Task modules. The Board View in the Tasks module is a great way for you to get an overview of the overall workload: You can first add all tasks to the To Do status column and then simply drag and drop them in order to prioritize them as accurately as possible. This helps you to date the tasks. Labels can also be helpful if you use them to divide the tasks into broad project sections.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*ZHxJUrv0uVtc2Fz8.gif" /></figure><h3>Determine the task duration and date</h3><p>As soon as the order is determined you can start setting due dates for the tasks. You should first think about the duration of the individual tasks in detail and also take buffer times into account.</p><p>Stackfield allows you to set due dates and time ranges directly via the task cards. A more convenient option may be found in the Timelines module. Here, you can view tasks without a due date (unplanned tasks) by clicking on the calendar icon in the upper part of the view and add them to the Gantt Chart with a single click. Once you have added the task to the Gantt Chart, you can adjust its duration and move it to the right time by simply using drag &amp; drop.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*fKWl6m7ojLUf35hU.gif" /></figure><h3>Set milestones</h3><p>Important intermediate dates — or goals — can be included as milestones in most Gantt Charts. These are usually visualized in the view with a diamond symbol.</p><p>Click on the plus symbol in the Timelines module and select “Add Milestone” to add a milestone to your Gantt Chart in Stackfield.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*l1NBIHaRen3ADQbL.jpg" /></figure><p>Alternatively, you can convert existing tasks into milestones. You can do this by using the more button (icon: three dots) in the opened task card — select “Mark as milestone”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*4bFJMAQs2w-hmz9s.jpg" /></figure><h3>Create dependencies</h3><p>Finally, we come to the central part that makes the Gantt Chart a Gantt Chart: the task dependencies. In order to visualize the project plan optimally, all interrelationships between the tasks should be considered. Thus, if tasks depend on the completion of other tasks, it is important to establish a dependency relationship between them.</p><p>Dependencies can also be created in Stackfield’s Timelines module simply by dragging and dropping. Move the dependency from the predecessor task to the successor task.</p><p>To better understand the dependency relationship: The dependent task is always the task to which the dependency arrow points. The task from which the arrow points must therefore be completed first.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*oKc7HWoZHBua7Jte.gif" /></figure><p>Alternatively, you can open the corresponding task cards and enter the dependency manually using the more button (symbol: three dots). To do so, click on “Add dependency” and select the corresponding task via the search mask.</p><p>To better understand the dependency relationship: The opened task then depends on the task selected via the search mask.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*zTyoaQj8UoT0sD7_.jpg" /></figure><p>In Stackfield you can also create multiple dependencies from and to the same task, i.e. when multiple tasks depend on the completion of a task or when a task depends on multiple predecessor tasks.</p><h3>Keep an eye on progress</h3><p>With the completed Gantt Chart you will receive the total project duration.</p><p>You can display the project in a weekly, monthly or yearly view.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*qZApbqlJLkfgwVqY.jpg" /></figure><p>Various filter options help you to individualize the Gantt view. The task list, which displays the task names, start and end dates and the task duration, can be restricted and extended as desired.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*_8q0sTmd9qJAvZJt.jpg" /></figure><p>Furthermore, tasks can be grouped by status and sorted according to the various criteria of the task list.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*iVG1CcvTKMkST7_0.jpg" /></figure><p>Finally, the entire view can be narrowed down in terms of the time period (year selection), various status options and responsible members.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*UOd_GoO3hI331VrT.jpg" /></figure><p>The Gantt Chart is one of the most useful tools for tracking the progress of a project. If you take your time when creating the chart and if you do some important preparatory work in the form of a project plan, you can definitely benefit during implementation.</p><p><em>Originally published at </em><a href="https://www.stackfield.com/blog/gantt-charts-basics-116"><em>https://www.stackfield.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9dbe8cbc92c0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/stackfield-stories/creating-and-using-gantt-charts-9dbe8cbc92c0">Creating and using Gantt Charts</a> was originally published in <a href="https://medium.com/stackfield-stories">Startup stories about the experiences and the mistakes we have made.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Startup Story: 5 million recurring subscription sales.]]></title>
            <link>https://medium.com/stackfield-stories/startup-story-5-million-recurring-subscription-sales-7e5d045ce1f1?source=rss-b269a15ec89a------2</link>
            <guid isPermaLink="false">https://medium.com/p/7e5d045ce1f1</guid>
            <category><![CDATA[growth]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[success-story]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Lena Wimmer]]></dc:creator>
            <pubDate>Mon, 21 Sep 2020 07:18:28 GMT</pubDate>
            <atom:updated>2020-09-21T07:18:28.214Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5NumwgFyuP8YByGE.jpg" /></figure><p><em>In keeping with the old tradition, I would like to revive our startup stories to talk about one of our goals at the time and reflect on how we achieved a seven digits annual recurring revenues (ARR).</em></p><p>A few years ago I published an article in which I spoke in detail about <a href="https://www.stackfield.com/blog/mistakes-and-lessons-from-startup-life-31">our beginnings as a start-up company</a>. Those of you who have read it know that not everything instantly work out as expected.</p><p>Contrary to my own expectations 8 years ago, the great success hasn’t immediately come about. In my mind we had created a digital money printing machine with Stackfield: once set up, we would only have to wait for the registrations. Well, as you can imagine, my idea didn’t quite match reality.</p><p>Comparing Stackfields history to a roller coaster ride would probably be a better fit — we had many ups and downs. Since our concept has been focused on privacy and information security from the very beginning, privacy scandals have of course played into our hands a lot over the last few years.</p><p>After the NSA scandal we were declared the “insider tip of CeBIT” and the “start-up of the week” in the Wall Street Journal. We were therefore particularly frustrated when the successes we achieved did not match our expectations right from the start.</p><p>You can read about what had happened exactly <a href="https://www.stackfield.com/blog/mistakes-and-lessons-from-startup-life-31">here</a>. But this much is for sure: We haven’t performed a rocket launch.</p><p>More than 1 million ARR — to reach this goal was something we have always associated with a certain market maturity. Once you reach this size, you have established a raison d’être in SaaS circles. The own product solves such a big problem of the customers that they are also willing to spend money for it. It is also referred to as <em>product/market fit</em>.</p><h3>Success rarely comes overnight, building a B2B business usually takes many years</h3><p>The stories that you read about in the newspapers, that you hear about in the podcasts and that you can watch on TV are different from ours. Those stories are the ones everyone knows — the stories of startups that have built a business worth millions in no time.</p><p>Obviously, you cannot fail to be impressed by this. However, the glorious success stories are not the norm.</p><p>Over the years I have had the opportunity to meet many successful founders who have been in business for many years. They all agreed on one thing: building a SaaS business takes many years.</p><p>As for me, it took quite some time until I had finally understood that.</p><h3>There is also a way without venture capital</h3><p>It’s not like we didn’t try to raise venture capital within the first two years. Unfortunately, our timing for this was rather bad. We had come too far with our technology to sell a pure vision with Stackfield, but at the same time we had no revenues to present. “First of all, we want to see if you can make money with what you have built,” was the feedback we have received so many times.</p><p>So we had to improvise in order to get along with the means we had at our disposal. Of course, it was impossible for our sales to skyrocket overnight. I suppose, in retrospect, this was probably the healthier way, because that’s exactly how we learned to handle our financial resources very effectively.</p><p>Of course, it wasn’t always easy that it took a bit longer, but we were convinced that we would make it work. I think that if there had been any doubt about our concept, if we hadn’t been one hundred percent convinced of our product and if we hadn’t been certain of being able to offer the market something that no U.S. company can offer — security — the company would certainly have been liquidated long ago.</p><p>Now, if you look at the numbers of the last few years, you can see that our sales have more than doubled every year until we finally reached the magic boundary of one million ARR. Our sales didn’t skyrocket, no, but they increased slowly, steadily and above all in a safe way.</p><h3>Only hire once you really need someone, but hire the best people you can get</h3><p>The past has repeatedly shown that especially highly rated companies came under pressure to grow quickly and were ultimately unable to survive under these circumstances. I see various reasons for this.</p><p>Growth must always go hand in hand with an adjustment of organizational structures. The faster a company grows, i. e. the faster its sales increase and the more employees join in, the more difficult it becomes to adjust internal structures and the less transparent the correlation between investments and results becomes.</p><p>Our team was quite small for a long time, and in my opinion that was a good thing. We simply did not have to deal with communication problems, lack of transparency and inadequate process management.</p><p>Problems like this often occur, however, especially when the product itself is not yet very mature. A small team, especially at the beginning, facilitates communication and allows flexibility. If the product is still in the early stages of development, it becomes more difficult to maintain this flexibility with each new employee.</p><p><strong>Anyways, as far as staff growth is concerned, I think it is extremely important, to…</strong></p><ol><li>Not simply hire employees haphazardly, but only when it is really necessary</li><li>not have long pockets and short arms at the wrong time, but to get the best people for your team especially in the very early stages (provided you can afford it)</li></ol><p>When we are looking for employees today, we pay very close attention to finding someone who <strong>a) has the best qualifications</strong> and <strong>b) fits perfectly into our team</strong>. Those two aspects are absolute dealbreakers for us.</p><h3>Always keep an eye on the market, be fast and flexible</h3><p>But let’s return to the subject of flexibility: In our business area, <strong>long-term plans are difficult to implement</strong> because market conditions are constantly changing. So by keeping our team as small as possible, we were able to remain as <strong>agile and flexible as possible</strong>.</p><p>We still try to maintain this as far as possible, because a number of advantages became apparent for us: Information can be passed on quickly. Plans can be adapted. We have always been able to react quickly and even today we sometimes cast away some of our ideas if we discover at short notice that other things make more sense or plans do not work out as expected.</p><p>Why it makes sense not always to follow plans meticulously was something we noticed at the beginning of the Corona crisis. Numerous companies shifted their work to the home office, which justified a timely expansion of our telephony functions. So without further ado we moved the conference calls up the priority list and put other things on the back burner. Being a secure provider from Germany, we had a big rush on our tool and found ourselves in a <a href="https://www.stackfield.com/blog/corona-impact-on-stackfield-102">rather fortunate situation during the pandemic</a> — at least economically speaking.</p><h3>Often timing is crucial too</h3><p>Edward Snowden and the NSA spying scandal, the enactment of the GDPR, the ECJ ruling that invalidated the privacy shield, the Corona pandemic — events like these have obviously played into our hands from a strictly commercial point of view.</p><p>What’s important then is to take the moment and react quickly.</p><p>The society is facing new data protection problems and has to distance itself from US providers who are not entirely legally secure. We offer the alternative. A large number of companies is forced to switch to the home office because of COVID-19 and suddenly everyone needs a secure collaboration platform. We can provide it. Timing is everything — in terms of marketing but also in terms of integrating new features.</p><p>As Stackfield is requested as a secure alternative to US vendors, it is natural that there will be requests for features and integrations from competing products.</p><p>Now, better be quick and shift the requests to the developer team’s to-do?</p><p>This one we had to learn: The more extensive the tool becomes, the more complex it becomes, the more complicated it becomes.</p><h3>There are only compromise decisions</h3><p>New functions, no matter how great the ideas may be, always need to be reasonable and provide added value for the majority of customers. For this reason, we involve customers when developing new updates. However, we always actively check suggestions for their relevance and feasibility.</p><p>This means that we record and collect every wish. If functions are requested very frequently, we think about whether users actually need the function or whether they just feel they do. Often it’s not that easy to decide. However, if we discover that the ideas would greatly enrich the use of Stackfield, we also start to implement them.</p><p><strong>The willingness to compromise is worth it. But it is only worth it if new functions are not implemented at the expense of user-friendliness.</strong> Nobody wants to work with a tool in which you cannot find your way around.</p><p>We have noticed that a clear and friendly interface is more important than ever for users today — perhaps even more important than the individual functions. People are overwhelmed by masses of information on a daily basis, and that alone is quite a challenge for the human brain. Stackfield is designed to make the job easier, not more complicated.</p><p>Now, what does this mean for our work:</p><h3>Polish, polish, polish</h3><p>We do not implement any function until we have found a user-friendly way to embed it. Existing functions are constantly being fine-tuned and optimized to keep click paths as short as possible and usage as simple and intuitive as possible.</p><p>There is no tool that can do everything. You have to be aware of that. So instead of frantically adding functions, we concentrate on our strengths.</p><h3>Long-term existing customers are more important than new customers</h3><p>One area in which we are two steps ahead of our competitors is customer support.</p><p>Any customer who tries to personally contact an US provider will probably not be very successful. Here, support is mainly based on forums and articles.</p><p>In contrast, we use a considerable part of our resources to support our customers and offer individual and personal support (in English and German). This is especially important for customers during the trial and introduction period. We have noticed, for example, that people simply don’t notice some functions once the tool reaches a certain size or scope. However, the more clearly we communicate the potential of our platform to our users, the more likely it is to win them as customers in the long term.</p><p>I want to emphasize the importance of the word “long term”. Outstanding support also increases the user experience and leads to new customers becoming loyal customers.</p><p><strong>I consider our long-standing customers to be particularly important.</strong></p><p>New customers are important — no question. But the biggest mistake that can be made, in my opinion, is to neglect existing customers in favor of acquiring new customers.</p><p>Granted, we have put rather little money into the sales area and might have been able to generate a little more here and there. Yet our customer base has grown steadily — slowly but steadily. Why?</p><p>Because <strong>recommendation brings a higher trust value</strong> and in many cases, this can have more effect than intrusive sales calls — at least that’s been our experience.</p><p><strong>Learn from your customers</strong></p><p>When I recall how we used to work in the past and how we work today, I see one thing above all that has always remained the same: from the very beginning, we have been close to our customers, we have maintained direct contact and from my point of view, this is something that must not change.</p><p>Without direct contact to our customers, we would have missed out on much of what our business is based on today — starting with our on-premise product. The public cloud has become increasingly popular in companies. It was predicted that the self-hosted software solutions would soon come to an end, but thanks to our customers, we have realized that this is not the case: <strong>On-Prem isn’t going the way of the dodo bird at all.</strong></p><p>To a significant extent, this is due to the fact that the topic of data protection is now more important than ever. Many companies simply have no choice but to opt for an on-premise solution. Since many other software providers no longer offer this option, it has become an extremely profitable business for us.</p><h3>What are our next goals?</h3><p>Now that we have achieved a certain level of market penetration, our ambition is to significantly increase awareness of the brand Stackfield and scale the business model. Quite often we’re told: “Your product is great, but why have we never heard of you before?”.</p><p>Since we passed the seven digits mark, we have seen a clear upward trend in growth, not only due to corona. We have not yet completely passed the 5 million barrier, but we are growing every month to such an extent that we are confident of reaching this and our next goal in the not too distant future — 10 million ARR.</p><p>A big thank you to our team for their passion and conviction and of course to our customers for the trust they have placed in us.</p><p><em>Originally published at </em><a href="https://www.stackfield.com/blog/from-0-to-5-mio-arr-115"><em>https://www.stackfield.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7e5d045ce1f1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/stackfield-stories/startup-story-5-million-recurring-subscription-sales-7e5d045ce1f1">Startup Story: 5 million recurring subscription sales.</a> was originally published in <a href="https://medium.com/stackfield-stories">Startup stories about the experiences and the mistakes we have made.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>