Anyone uses Scrum or works in a company that uses Agile software development? How much is important today working by following this stuff?
-
Welcome to B4X forum!
B4X is a set of simple and powerful cross platform RAD tools:
- B4A (free) - Android development
- B4J (free) - Desktop and Server development
- B4i - iOS development
- B4R (free) - Arduino, ESP8266 and ESP32 development
Agile software development & Scrum
- Thread starter Emme Developer
- Start date
- Similar Threads Similar Threads
I do.
It depends on the project / team size.
The larger the project the more you feel the need of utilizing such frameworks.
https://www.scrumalliance.org/why-scrum
It depends on the project / team size.
The larger the project the more you feel the need of utilizing such frameworks.
https://www.scrumalliance.org/why-scrum
Yes I know, I finish to read Scrum book from Jeff Sutherland. Very good book
Here!
I started as a professional sw developer in the early 9ies. What we did was to work "agile" and with some kind of "scrum". No big thing as we used to talk to each other in that decade
We were very fast and knew what we did. No meetings (except it was really needed). If I had a question I just talked to people. I tested on my own before I asked the testers to take a look. I was allowed to install my programs on my own having the full responsibility for it.
Then there was a time which this was seen as "bad" and "we need structured processes". So my work was devided in several tasks which were handled by different people. Over that there was a "release management" installed. Of course everything has to be documented. As a result the time to finish sw was multiplied by 10. Only "some" people were allowed to install sw. So at the end noone was responsible, the development time increased a lot and the cost situation was ridiciolous.
After some they "discovered" that "too many people" are needed to fulfill that process. The "time to market" was to long and the costs too high (what a surprise). So guess what. They wanted us to work "agile" with methods we were using in the 9ies by intuition and without any explanations. Very funny.
However. This is the main reason why I use B4x. I'm free to develop what I want. No restricitions or other people (except the customer) telling me what and how to do (ok, maybe Erel or some of you guys teaching me a better way to do this or that - but this is an honour).
I started as a professional sw developer in the early 9ies. What we did was to work "agile" and with some kind of "scrum". No big thing as we used to talk to each other in that decade
We were very fast and knew what we did. No meetings (except it was really needed). If I had a question I just talked to people. I tested on my own before I asked the testers to take a look. I was allowed to install my programs on my own having the full responsibility for it.Then there was a time which this was seen as "bad" and "we need structured processes". So my work was devided in several tasks which were handled by different people. Over that there was a "release management" installed. Of course everything has to be documented. As a result the time to finish sw was multiplied by 10. Only "some" people were allowed to install sw. So at the end noone was responsible, the development time increased a lot and the cost situation was ridiciolous.
After some they "discovered" that "too many people" are needed to fulfill that process. The "time to market" was to long and the costs too high (what a surprise). So guess what. They wanted us to work "agile" with methods we were using in the 9ies by intuition and without any explanations. Very funny.
However. This is the main reason why I use B4x. I'm free to develop what I want. No restricitions or other people (except the customer) telling me what and how to do (ok, maybe Erel or some of you guys teaching me a better way to do this or that - but this is an honour).
This is one of the reasons that has convinced me to learn b4x!
I'm happy to discover that the way i have taken is the "right" way, think Agile is a great stuff for team management in different jobs (not only in sw developing).
Have you never used Test Driven Development practice? I'm tryng to learn it, but i really don't understand how can i write test before write the code
In my previous job we used Agile. In some situations (eg: having the team determine the plan & be responsible for milestones) it worked well, however the concept of "Minimum Viable Product" was an issue for me as a Product Manager because the sales people used it as an excuse to try & ship "product" that wasn't necessarily functional & stable. Also, our morning stand-up meetings always ran much longer than I wanted...
- Colin.
- Colin.