Let's start in order
What this figure means a bit later, but for now let's start with an introduction.
On a cold February day, nothing foreshadowed trouble. A group of innocent students came for the first time to a couple on a subject that they decided to call "Methodology for organizing the design and development of information systems." There was a regular lecture, the teacher talked about flexible development methods, such as Scrum, nothing foreshadowed trouble. And at the end, the teacher announces:
I want you to experience all the hardships of teamwork yourself, divide into groups, come up with a project, appoint a leader and go through all the stages of design together. In the end, I expect a finished product from you and an article on Habré.
This is where our story begins. Like balls in a pool table, we bounced off each other until the energy of the blow dissipated and a group of 7 people gathered together. Perhaps this is too much for a training project, but in order to better distribute the roles, that's it. A discussion of ideas for the project began from "Let's take a finished project" to "Emulator of the formation of space objects." But in the end, the idea passed, the name of which you read in the first picture.
Stop Procrastination - what it is, what it is eaten with and how we developed it and what came of it
The story will be conducted on behalf of the project manager, to whom, fortunately or unfortunately, I was appointed. So what idea came to our mind? Inspired by SupperCommon's popular "Shake the Alarm" alarm clock, namely the function to completely block the smartphone until the user performs a certain action that will most likely wake him up, we decided to create a similar application that will help get rid of phone addiction, on the same principle as "Shake the Alarm Clock"
Principle of operation
User sets timers
- Time that can be spent on a smartphone
-Time without smartphone (blocking period)
When the timer expires, an overlay appears on the screen that cannot be minimized
-To close the overlay, you need to pass a small test (enter a password on a confusing keyboard, solve a math problem, shake your phone for a couple of minutes)
After unlocking in this way, the time that you can spend on your smartphone is halved, and so on up to one minute
Building a team
To begin with, it was necessary to determine who would do what and in what language it would all be written. I think it has little to do with project management, because when you assemble a team for a real project, you immediately assemble those who you need. As a result, I also took on the burden of a designer, chose one team leader who had good experience in developing applications, three programmers were assigned to him, and two more became testers. Of course, the programming language was chosen according to skills. As a result, it was decided to use Java, since all programmers were familiar with it.
We set tasks
On the recommendation of the teacher, a task board was created on a free service . It was planned to work according to the Scrum system, where each stream would be a kind of finished application.
However, in reality, one big and long stream came out of all this, in which edits, additions and corrections were constantly made.
We write specs
Under the influence of Savin's book "Testing.com", I had my own idea in my head about how everything should be eliminated. It all started with writing specifications, as I believe, without a clear description of what we expect, what and how it should work, nothing will work. Programmers will program everything as they see it, testers will test something else, the manager was waiting for the third, and it will turn out, as always, the fourth.
Writing specifications is not easy, you need to think through all the details, all the nuances. Of course, nothing happened the first time around. As a result, the specifications were supplemented, altered 4 times. You can find the last option at the end of the article, in the links section.
We draw the design
Design in a mobile application is the most important thing. However, not everyone understands this, including many from my team zealously arguing with me that the design is not needed, that this is the most unimportant part of the application, etc. You shouldn't be so naive. Firstly, a ready-made design is a simplification of the programmer's work, he does not need to think about what to put where and where, he just takes and typesets what is drawn. Together with the specifications, the design almost completely frees the programmer's mind from unnecessary things, and gives him the opportunity to concentrate on the logic. In general, a prototype (terrible) design was first drawn:
But then the design was combed and brought back to normal.
(Link to all design elements at the end of the article).
Programming
Programming is difficult, but possible. I will omit this moment, since I personally did not do this. The programmers did a great job, without which everything would be meaningless. Of course, we managed to realize some of the ideas. And the program still needs improvement. Lots of bugs and features to fix. If we had more time, we would get out of deep alpha, but for now, you can test the application at the end of the article.
Well, about testing
What is the most important thing in programming? In my opinion, the main thing is that everything works and looks the way it should. As it should, it does not always and not immediately. This requires testing. To my testers, I proposed a testing model using test cases. First, test cases are written in full accordance with the specifications, and then they are tested. You can see what came out of it in the links below.
Thanks for reading. I hope you found at least something useful here, maybe an idea for your startup, or maybe a good piece of advice or a tool.
Links:
Recent ones .
Design on .
и .
The application itself . - The app was built under the name HandsOff, don't even ask why (because Stop Procrastination is too long).
Well, at the end
Do you think it all made sense?
Only registered users can participate in the survey. , you are welcome.
Is such a practice needed in educational institutions and how useful and applicable it is in real life
-
Need invaluable experience
-
Necessary, although a little experience
-
Almost useless, maximum you will understand the common features of teamwork
-
Waste of time and effort
2 users voted. There are no abstentions.
Source: habr.com