<?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 Daniel Cojocari on Medium]]></title>
        <description><![CDATA[Stories by Daniel Cojocari on Medium]]></description>
        <link>https://medium.com/@danutsrl?source=rss-8ca67d3efa30------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*PwBAcqYqQnobf-vgZsqNxQ.jpeg</url>
            <title>Stories by Daniel Cojocari on Medium</title>
            <link>https://medium.com/@danutsrl?source=rss-8ca67d3efa30------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 11:18:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@danutsrl/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[Tpoint Project Management Retrospective]]></title>
            <link>https://medium.com/@danutsrl/tpoint-project-management-retrospective-792fdfebc6e9?source=rss-8ca67d3efa30------2</link>
            <guid isPermaLink="false">https://medium.com/p/792fdfebc6e9</guid>
            <category><![CDATA[squash]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[retrospectives]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Daniel Cojocari]]></dc:creator>
            <pubDate>Wed, 15 Apr 2020 10:25:28 GMT</pubDate>
            <atom:updated>2020-04-15T10:25:28.425Z</atom:updated>
            <content:encoded><![CDATA[<p>Here we are, a few days/a week before the official project ending and the official launch of Tpoint Courts and Application. And as a new tradition, I will write the project management retrospective, which will include what went good, what wasn’t quite good and what lessons I’ve learned/ways to improve my management work in the next projects.</p><h3>Who am I and what is Tpoint?</h3><p>Let’s start with the beginning. I am a Junior Project Manager at Titanium Soft. Junior because this is just the second IT project I managed and I am just for one year and a half in the Industry.</p><p><a href="http://titanium.codes/"><strong>Titanium Soft</strong></a> is a growing IT company that works on building quality IoT and Blockchain Solutions. Most of the projects are outsourcing projects, but lately, we started to work on our in-house products.</p><p><a href="http://tpoint.club/"><strong>Tpoint</strong></a> is a group of people that loves Squash and are eager to make this sport more popular and accessible in the world. And to start, they decided to build Squash Courts in open, accessible spaces, where people can enter and play. And to start playing the user will have to Download the App, Register and book his game. Below is the video promotion of Tpoint:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FrBmqowmaH3I%3Fstart%3D4%26feature%3Doembed%26start%3D4&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DrBmqowmaH3I&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FrBmqowmaH3I%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/a466dccebcb1b9d869075de88848ad0a/href">https://medium.com/media/a466dccebcb1b9d869075de88848ad0a/href</a></iframe><p>There will not be interacting with any human (except when support is needed) and all steps like:</p><ol><li>Registration</li><li>Booking a game</li><li>Pay for the reservation</li><li>Invite a friend to play</li><li>Enter and see game statistics</li><li>Regulate court temperature, light, and music</li></ol><p>will be managed through the mobile app.</p><p>I and my Titanium Team were in charge of building this application and here is a preview of it:</p><figure><img alt="Tpoint App Initial Design" src="https://cdn-images-1.medium.com/max/1024/0*rOx9qwiBdZ7KNiA2.jpeg" /></figure><p>After about 6000 hours of development on this project, the time came to make some kind of recap retrospective and below is my perspective on how the project went.</p><h3>What went good in the project management:</h3><ol><li><strong>Very good product specifications.</strong> Usually, you get a very broad image of how should be the final product and the specifications. We got from the product owner a very well described document, where even the tables’ fields and properties were described.</li><li><strong>A good QA involved since the beginning. </strong>Even from the initial phases, we involved our good QA, which helped us understand the gaps in the documentation and forecast the issues with future development.</li><li><strong>Good specialists, open to discuss “a better way” than implement just “what’s required”</strong>. We had often long dialogs with the development team, as they were finding gaps in the specifications or thought about a way to have a better delivery. In that way, we presented often to the client solutions that were not thought since the beginning, but better actually for the business.</li><li><strong>Interesting Industry.</strong> As a service provider company and employees, not always the project we get are interesting for ourselves as individuals. Tpoint wasn’t the case. We’ve got a nice idea, with interesting implementation and great future impact. Seeing how the court is built and imagining how people will play using our app, was always a good feeling for all the team.</li><li><strong>Readjusted the processes once they were getting worse. </strong>Based on the issues we encountered with planning and estimations, we changed our way of working, and some of the changes were: Feature-based releases, Enough time estimated for testing and bug fixing, a better description for the requirements, risk forecasting and more.</li></ol><h3>What wasn’t good during the project implementation:</h3><ol><li><strong>We started to develop without an approved design. </strong>This was one of the very first mistakes. We were developing the registration flow for example, while the client was still changing the settings and requirements. This led to a 3–4 weeks project delay, as we had to develop again the same user flows again and again.</li><li><strong>The project plan was based on Raw Estimations.</strong> Raw estimations were made to draw a draft plan, and have an initial agreement with the client. In our case, our plan for some months was based on them.</li><li><strong>Didn’t plan time for testing and bug fixing.</strong> Despite the fact that the QA engineer was working full time on the project, all sprint deliveries were of poor quality and full of bugs. All of that because the QA Engineer was testing in the current sprint, the previous one, and time for bug fixing we simply didn’t have and no way to squeeze them in the plan.</li><li><strong>Sprints/Releases were not features based, but time-based.</strong> Our sprints were for one week. Each week we had to deliver. However, the features were not readily developed/tested to be deployed and close the sprint. Thus, the next sprint had half of the previous one’s features.</li><li><strong>Not a standardized communication channel with the client.</strong> Just after one month of work, the client told us that the email we’re communicating with him, is not his main one, and he’s not checking it often. Besides, communication was spread through different channels (email, WhatsApp, Slack) and information was getting lost.</li><li><strong>Inexistent Risks &amp; Issues Management Plan.</strong> There were many issues in the project that could be forecasted and we could prepare some mechanisms to prevent them, however, this kind of plan wasn’t developed. Forecasting issues regarding third-party services that we were using, or simply regarding public holidays in the country where the 5 days sprint is transformed into a 2 days sprint, could prevent a lot of trouble.</li><li><strong>Bad Features Description and missing Acceptance Criteria.</strong> The good documentation kept us confident that everything is clear when actually a lot of times we were over-developing / under-developing features.</li><li><strong>Documentation wasn’t updated.</strong> Project plan, schedule, specifications document, and all the other documents didn’t pass through constant and quality updates and when a new developer was onboarded, to understand the actual product and user flow was a nightmare.</li><li><strong>Internal communication mismanagement.</strong> Developers are meant to solve issues and develop features. Often, communication isn’t their strongest asset. That is why many times we had changes on Backend, without the Mobile Team being aware of it, as on Stand Up meeting wasn’t mentioned.</li></ol><h3>How would I improve for future projects as PM:</h3><ol><li><strong>Design everything and get the magical “Approved” from the client.</strong> Many times on new screens we were using the same components, different arrangements, and sometimes that was working, but when it didn’t was super painful. A designer can get a screen view faster than a developer.</li><li><strong>If there is no design — NO ETA (estimated time of arrival).</strong> The raw estimations are good for an overall understanding of the period needed for the development but not as a deadline. Agile means adapting to change, but without design, there will be too many changes that could be better planned and time/resources saved.</li><li><strong>Hybrid — no, thank you.</strong> There are 2 big giants in the project management methodologies: Agile and Waterfall (at least at that moment in our company). Each of them has its Pros and Cons, and each of them is better for a specific type of project and goals. And of course, there is the Hybrid — You Plan everything, You design, and then for development -&gt; You use Scrum Events. And if in theory, it looks great, in practice you cannot embrace change when you already have deadlines, and to work with CRs (Change Requests) it’s a headache. In the end, you cannot catch two rabbits at once.</li><li><strong>Always send by email the summary of all the Skype, WhatsApp, Telegram, Meet, WhatEver call</strong>. Many times we had agreements on a call, regarding certain functionality, and then “Why have you done it this way?”. Plus, everyone forgets things, Google (in this case Gmail) doesn’t.</li><li><strong>Always make sure you got the full, right answer.</strong> “In squash, you never play alone” transformed into “In squash, you never play alone, but you can play with a friend that will not use Tpoint app” and this had to change a whole bunch of the app.</li><li><strong>Managers have a plan, developers have another.</strong> You might hear from the client that he has a presentation in 2 days and you need to give him a stable build, but developers have their process, and if you try to force it / hurry it too much, you might regret it. <em>Of course, letting them be slow and lazy is not what I mean here!</em></li><li><strong>Befriend your QA Engineer.</strong> For planning is important to always know all the Use Cases, and to make sure you don’t have any gaps. As PM, at this point, the QA is the best to help you.</li><li><strong>Always include a buffer for bug fixing. </strong>We’ve made estimations for the development of every task. However, we didn’t consider the time to test and fix the bugs.</li><li><strong>Refine and Replan. </strong>Many issues and risks with the schedule and not only, were forecasted before they actually occurred, however, our mechanism to work with them was to push and fit the deadline rather than refine the backlog and replan the estimated delivery time. Of course, that led to a huge failure. We didn’t fit the deadline, we didn’t deliver a high-quality product.</li><li><strong>Kepp documentation updated.</strong> Agile means <em>“Working software over comprehensive documentation”</em>, however, that doesn’t mean no documentation at all. When you need to onboard a new developer, it takes ages if you don’t have product documentation and technical documentation. Here, as PM, I have to work on both directions, keep product documentation updated and keep track that the Devs are updating the technical one.</li><li><strong>Write clear, comprehensive user stories/features with full description.</strong> Even if you might look that the design is clear, a clear description and user flow should be part of the description for a user story or feature. Acceptance criteria is important for the test case writing and testing process, but also avoiding cases when the client wanted the feature or user story to work differently.</li><li><strong>Improve team communication by setting some basic, important rules.</strong> Do not deploy before letting the whole team about it. When you change something, let the team know about it. When there is an update from the client, everyone should know about it immediately. Those are a few of the rules that will be set in my future projects.</li></ol><h3>Where are the application and the courts now?</h3><p>The application is in the process of being deployed to the App Store and Google Market. Once is there, I will update this section.</p><p>The court status is as you can see in the picture below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*N_LxpQxFQuo0WEA7" /><figcaption>Picture from Tpoint Facebook Page</figcaption></figure><p>The courts are located in Israel, Tel Aviv for now (soon, all around the world). For more information and updates, you can <a href="https://www.facebook.com/tpoint.club">follow the Tpoint</a> team on Facebook.</p><p>Update: Due to Covid-19, new features were added to the app, and the courts launching is postponed.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=792fdfebc6e9" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>