Spekfy — system management of it projects
Hello, Habr! Today I would like to share the story of Eugene ebartashevich that represents the project Spekfy.
His goal is to develop a better tool to manage it projects, which allows you to consolidate all requirements and objectives, cost and timing of implementation with specification. We invite all interested people under the cat — the story will go from the face of Eugene.
/ photo Mark Hunter CC
Thoughts on the launch of such a service appeared in the course of my work as an independent developer. I started my career as a system administrator, then worked as a tester, and the last 10 years I have been freelancing. Here is my my profile upwork.
Any experience on working on their own startups I was not, and in fact I made this service for myself. This pushed me experience with customers from different industries. The tasks were very different from developing a CRM for managing projects, publishing and realizing the defect tracker for the construction company.
All these projects (even at the testing stage) involve gathering product requirements and developing a system of cases for testing based on them. At the moment there are a variety of tools (e.g. Atlassian Confluence), which allow us to achieve this objective, but only in isolation from the management of the project as a whole.
With this problem I faced when I had to assess the structure of the order for the development, cost and timing of implementation for one of our clients on upwork. Here I suggested him to enter the draft in my system spekfy to in the first place, the client could decide what he needs.
One of the regular customers offered to bring my project to the public. I appreciated its potential and modified it to form the completed prototype product. The total time that I spent with breaks, was about 2 years.
the
As I said above, quite a long time I worked exclusively in the. From the point of view of a customer interaction with a freelancer involves two main tasks — saving money together with the receipt of the decision, which will be performed at a decent level of quality.
For the performer there is a certain difficulty. It is not always possible to show your level of competence solely through examples of work performed — the coolest cases are usually under NDA, but for budget approval and timing still need somewhere to start communicating with the client.
It is at this stage and included in our decision — Spekfy. It can be used in order to show the client how much it will cost the implementation of certain parts of his project (as he will be able to assess their needs for budget savings development) and demonstrate a General understanding of the structure of the task (to show their level of competence).
An example of such a case — one of my orders Upwork. He was to develop CRM for the company, leading a variety of courses and private lessons.
Classic situation: the customer is long and systematically prepares and gathers requirements, but in the end they are too superficial to start work. There are still high expectations on the timing and cost of implementation.
During the crushing of the project on its components, we not only made detailed requirements for each of these parts, but found that part of the functionality of the customer simply forgot. These calculations were sent for approval of client colleagues, and then began the discussion.
As is usually the case, we began to entangle each other by chains of neglected correspondence, missed phone calls and endless negotiations. All this managed to stop one willful decision to move to Spekfy.
Structured approach to the analysis of all the nuances allowed us to track all required final approval, work together to eliminate unnecessary requirements and start the development process.
Ultimately, we found that initial expectations on the timing and cost of implementation has been underestimated several times, and the customer had the opportunity painless rejection of a piece of functionality through its input into subsequent versions of the project. This move will allow to find a compromise solution.
the
Now we have moved away from completely "naked" MVP and we offer this tool to everyone who works with it projects and would like to estimate the expected effort to implement those or other problems. Today you can create your projects, tasks, requirements and use-cases. Plus we have integrated with Zapier.
In the future we plan to adapt Spekfy to work with agile methodology / waterfall, start integration with bitbucket / jira, slack, and MS Project. In addition, we understand the need to provide custom project templates. Above all this plan to work, improving the overall level of usability of the service.
P. S. we Invite everyone to participate in testing and share your opinion on Spekfy in the comments, in addition to this here you can ask any question to developer — ebartashevich.
Article based on information from habrahabr.ru
His goal is to develop a better tool to manage it projects, which allows you to consolidate all requirements and objectives, cost and timing of implementation with specification. We invite all interested people under the cat — the story will go from the face of Eugene.
/ photo Mark Hunter CCHow did the idea
Thoughts on the launch of such a service appeared in the course of my work as an independent developer. I started my career as a system administrator, then worked as a tester, and the last 10 years I have been freelancing. Here is my my profile upwork.
Any experience on working on their own startups I was not, and in fact I made this service for myself. This pushed me experience with customers from different industries. The tasks were very different from developing a CRM for managing projects, publishing and realizing the defect tracker for the construction company.
All these projects (even at the testing stage) involve gathering product requirements and developing a system of cases for testing based on them. At the moment there are a variety of tools (e.g. Atlassian Confluence), which allow us to achieve this objective, but only in isolation from the management of the project as a whole.
With this problem I faced when I had to assess the structure of the order for the development, cost and timing of implementation for one of our clients on upwork. Here I suggested him to enter the draft in my system spekfy to in the first place, the client could decide what he needs.
One of the regular customers offered to bring my project to the public. I appreciated its potential and modified it to form the completed prototype product. The total time that I spent with breaks, was about 2 years.
the
Where it is used
As I said above, quite a long time I worked exclusively in the. From the point of view of a customer interaction with a freelancer involves two main tasks — saving money together with the receipt of the decision, which will be performed at a decent level of quality.
For the performer there is a certain difficulty. It is not always possible to show your level of competence solely through examples of work performed — the coolest cases are usually under NDA, but for budget approval and timing still need somewhere to start communicating with the client.
It is at this stage and included in our decision — Spekfy. It can be used in order to show the client how much it will cost the implementation of certain parts of his project (as he will be able to assess their needs for budget savings development) and demonstrate a General understanding of the structure of the task (to show their level of competence).
An example of such a case — one of my orders Upwork. He was to develop CRM for the company, leading a variety of courses and private lessons.
Classic situation: the customer is long and systematically prepares and gathers requirements, but in the end they are too superficial to start work. There are still high expectations on the timing and cost of implementation.
During the crushing of the project on its components, we not only made detailed requirements for each of these parts, but found that part of the functionality of the customer simply forgot. These calculations were sent for approval of client colleagues, and then began the discussion.
As is usually the case, we began to entangle each other by chains of neglected correspondence, missed phone calls and endless negotiations. All this managed to stop one willful decision to move to Spekfy.
Structured approach to the analysis of all the nuances allowed us to track all required final approval, work together to eliminate unnecessary requirements and start the development process.
Ultimately, we found that initial expectations on the timing and cost of implementation has been underestimated several times, and the customer had the opportunity painless rejection of a piece of functionality through its input into subsequent versions of the project. This move will allow to find a compromise solution.
the
future Plans
Now we have moved away from completely "naked" MVP and we offer this tool to everyone who works with it projects and would like to estimate the expected effort to implement those or other problems. Today you can create your projects, tasks, requirements and use-cases. Plus we have integrated with Zapier.
In the future we plan to adapt Spekfy to work with agile methodology / waterfall, start integration with bitbucket / jira, slack, and MS Project. In addition, we understand the need to provide custom project templates. Above all this plan to work, improving the overall level of usability of the service.
P. S. we Invite everyone to participate in testing and share your opinion on Spekfy in the comments, in addition to this here you can ask any question to developer — ebartashevich.
Комментарии
Отправить комментарий