I mean, not really? I truly feels like it still holds true to the Reddit idea. All the div elements are in the same place for the most part. I guess the font is what would make it appear to be a social feed.
But the main takeaway for your question is the last bit: > Even though many people are confused by these terms and consider them the same, they are slightly different. A sprint is a short, time-boxed period, during which the scrum team needs to complete a designated amount of work. Sprints are the very heart of agile and scrum methodologies, and getting sprints right will assist your agile team in shipping a better product with fewer headaches.
>On the other hand, an iteration is a defined time-box applied in an iterative project model. In this case, the entire solution is developed throughout a project. Simultaneously, snapshot views or "work in progress" are presented to stakeholders or sponsors for feedback at the end of each time cycle or iteration.
Oh, don't worry; I'm mostly being facetious. I exaggerate the feeling of many developers† that project managers don't actually provide value but merely tell others what to do and survive on their work. (Although, actually, almost every project/program manager I met in my career before I joined FAANG was totally useless and provided no value, and I was continually amazed they convinced people to pay them anything at all. I have a lot of respect for them here, though. Based on his posts, I expect our friend falls into the former group, if indeed has actually has a job in the first place.)
There's certainly a clear division between the roles of a project manager from the roles of a tech leader. In small companies, however, things tend to get mixed up sometimes. Not rarely, the formal idealized organizational charts won't reflect the actual layout of occupations. There is simply not many people around, so no one can specialize in doing one specific thing and the dynamics in the working environment become very organic. I have also been in this situation in the past.
Hired as "Computer Analyst" (don't ask me what a "Computer Analyst" is - no one ever succeeded in clearly explain it to me), but I think "swiss knife" would better describe my position in the company, which was a very small one (6 people only). I had to do everything: analysis, modeling, programming, maintenance, client support, etc. Hard work, but an incredible chance to learn more about the different phases of the software development cycle. Later on, all the effort paid off when all that I learned helped me to get jobs as tech leader and software architect.
​
>I would definitely ask for a raise.
You sure should.
Figured White labeling out: Use the Self-hosted plan and you can adjust the code and change logo CSS files etc.:
https://activecollab.com/self-hosted-project-management
For a team this size I would recommend https://activecollab.com/. It's pretty darn powerful and probably has some features you won't need, but overall it's great. You can also check out Trello as someone else suggested here but in my opinion it's best for teams of 2-5 people and personal to do-s. I also know that Asana is popular and is supposed to be good for bigger teams, so feel free to check that out too, though I haven't personally used it on an ongoing basis. Activecollab also has Slack integration.