Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "scrum"
-
We have new scrum master. First meeting together.
Project owner:
- I would give them time to wensday (2 days away) days to do migration
Manager:
- delivery is in Tuesday. can we have two teams to work on it so it will be done twice as fast?
Scrum Master:
- do you really think that if you get 9 women pregnant they would deliver you baby in a month?7 -
I work in a scrum team of 6 persons.
We have the same IP address and we get ads based on what everyone else was searching. Sometimes shit just gets akward10 -
!rant
So this happened in the zoom meeting today. 2 colleagues were arguing on something.
A : "Do I look like f**king joke to you?"
B : " No, you don't look like a joke , your camera is off. But you sound like one. "
A : "I am so tired of you , f**k you man"
B: " Hey you can't f**k me without my consent, I said I am not interested."
Me : "Uhm guys this is scrum meeting."
B: "No shit captain obvious, we all know that. "
I am so speechless.....36 -
My scrum team was discussing about how our workspaces are basically the size of a large coffin. Our scrum master then chimed in to try to calm everyone down and said they are much larger. Closer to the dimensions of a prison cell he says.2
-
Our product owner's equivalent of "It's not a bug, it's a feature" seems to be "It's not a new requirement, it's a clarification."
:-/2 -
Let's build a house with no blueprint, no idea how it should look but have daily meetings about the bathroom... #Scrum3
-
This happens nearly every sprint.
TEAM: So, are you happy with how we are going to make this feature?
Business: Yeah, we really need it! It's exactly list that! Quick build! 🏗
TEAM: You're sure.... remember what happened last time...
Business: yeah, yeah, yeah
TEAM: ☕️💻
one week later....
Business: Oh yeah, that thing, we changed our mind we don't want it can you do something else?
TEAM: ...
Business: Agile!!!!!!!!!
TEAM: 🤦♂️
Found out they all went on a 2 day course to learn SCRUM...5 -
I was asked by our tester and scrum master to ignore some failing unit tests yesterday. The tester literally said "no time for tests, we need the build now". The scrum master is also a tester and agreed. I dont think I can respect either of them as testers anymore.3
-
During scrum, we have a remote QA Engineer who literally includes what she and her child do during her lunch breaks.
"Yesterday during lunch, little Jimmy and I went clothes shopping during lunch and I got him some new shirts and they're 100% cotton"
NOBODY FUCKING CARES!!12 -
You know scrum is working when the dev team are feeling that scrum isn't working because they have nothing to do because the product team can't keep up with the pace.4
-
Didn't finish morning run in time for morning scrum call. Looks like I'm answering the call from here.8
-
Appretnly for 5 devs + 1QA we need now :
A project manager
A scrum master
A VP of engeneering
Another person I don't remember title.
yep 2023 will be "productive"9 -
OH: "We reduced daily standups to tuesday and thursday. Otherwise we have to stand up too much and this nearly counts as sport."
-
>me on first day as temporary scrum master
>gets invited to 'optional' scrum master meeting
>meeting is with all SMs globally
>at 6PM local time
>POs also joining because why
>first topic is discussing a defect
>a PO has stroke of genoius
>"Our code base would be much easier to maintain if it didn't have bugs!"
>this gonna be a long meeting4 -
Me, complaining about being single: It would just be nice to have someone who cares how my day went every day
Scrum master: Hey...
Me: No5 -
Scrum Master: Let's estimate the task. Chose your estimations individually, then we will reveal at the same time and discuss
- variety of votes, ranging from 1 to 8
Product Owner: I don't agree, this should be a 1 or 2.
Dev Team Lead: Agreed, this is why I chose 2. Let's vote again.
- All votes now are 1s or 2s
Good fucking job 🤨11 -
So I studied for a long time about scrum, convinced my boss, his boss and our team to consider it, everyone liked it but seems to don't understand it very well.
I organized meetings about it and everything...
This week the majority of our team will attend a Google event about scrum in another city.
Guess who is not going?11 -
No, I do not wish to work on your Scrum-managed project.
I do not wish to contribute to the Taylorism of my profession.
I do not wish to be an interchangeable cog in your software sausage machine.
I do not wish to be tracked by some pointless metrics like a call-centre worker.
I do not wish to bust my tight, cute ass to sprint after some idiotic management request that could have been factored in earlier.
I do not wish to obtain some piss-ant qualification that "authorises" me to do my job.
I do not wish to be party to your lie that technical debt will be avoided by refactoring---whatever the cost.
I do not wish to contribute to the death of software engineering to have it replaced by software development.
Agile? Sure. I can pick up the phone and talk to the client, users and fellow devs. After all, that's what it FUCKING MEANS. Communi-fucking-cation.
See that burndown chart? See your anus? Know what's happening next?
Fuck Scrum and every fucking bottom-feeder that is scamming a living by promoting it. You're killing this business.
Hugs and kisses,
Platypus15 -
worst part of working in scrum: trying to remember what you worked on Friday for Monday morning's stand-up meeting.2
-
Devops here, Devops there ... Stop with this bullshit, less than half of the guys with Devops on their CV truly are Devops.
Same shits for Fullstack or Scrum Master, and I think I know why.
Because recruiters and companies absolutly ignore what it truly is : "Devops ? That's the new name for sysadmin hipster, believe me we're not hiring Sysadmin anymore but Devops now.".
So now they want more and more people with these profiles.
This is just leading everyone to become what they're not.
Please get your facts straight before fucking everything up.4 -
When job requirements say:
Programming Languages:
CSS
Scrum
Git
jQuery
JSON
...who tf writes these requirements!?9 -
Pro tip to scrum masters: bringing a scrum suitcase to your sprint meetings is more useful than bringing scrumbags.1
-
Manager: we should arrange regular catchups, I have several Monday morning, how about 10:30, that'd be 9:30 your time?
Me inside: dude, we both know I struggle to be up in time for the scrum at 10, do you really think I'm going to be any better at 9:30?
Me outside: How about 10:30 after scrum?
Manager: OK, that works, I have half an hour between meetings
Me: Thank fuck.4 -
Every scrum meeting where I can't figure out what I should claim that I did yesterday...
"Scrolled devRant and 9GAG" obviously isn't an option!5 -
Why does Scrum feel like micromanagement?
I seriously hate daily standup, ours go on for half an hour, sometimes longer and I have to listen to completely unrelated shit I don't know anything about. I cannot explain how disconnected I feel. I'm the only dev working on their website. Some days I don't even need to check in, I have nothing to say.24 -
My team has regular daily meetings they all call scrum. Meetings like 1+ hours. I wanna immolate myself in protest!2
-
So...my first experience with Scrum. How many fucking energy and productivity draining meetings can you squeeze in to two weeks?!!!! Agile? Hahaha. Don't get me started! Leave me alone and let me get some work done!4
-
Client: we are using Scrum. Next week we have sprint review organized by the project manager.
Me: it’s not Scrum.
Client: in the next sprint we work on a mockup not releasable in production.
Me: it’s not Scrum.
Client: sprint backlog is changed again, at the end we must do everything that is written in the contract with that fixed amount of money.
Me: definitely not Scrum.
Client: we are using Scrum.
Me: Ok.1 -
Daily scrum
Today, the Scrumpy Master was not here, so I leaded the daily scrum meeting,
rephrasing the 3 standards questions a little bit: the results where amazing.
Here my questions in case somebody want to use them:
- What the fuck did you do on Friday?
- What the fuck do you think you are doing today?
- What is your fucking problem?
We managed to keep the meeting very short and after the meeting everybody was sooooo concentrated I couldn't believe it.
Beeep Beeeeeep 7:00 o'clock. Shit. I was dreaming. Must wake up and go to work.
Scrum master will be there too.8 -
SERIOUSLY WHAT THE FUCK IS SCRUM, WHY DO MANAGERS KEEP USING IT, WHY DO YOU WANT ME TO MICROMANAGE AND MEET ARBITRARY DEADLINES THAT ARE TANGENTIAL TO THE MAIN PROJECT???!!!?!12
-
When your daily scrum takes an hour because your senior developer co-worker gives unnecessary and incredibly detailed updates...
"Well, first I tried hiding the button, but it wouldn't come up when I needed it to, so then I made an options menu, but the sliding transition was difficult to implement, so then I..."6 -
I think I just hit my lowest point.
Spent ALL of last week trying to get my WAMP server to call a PHP script via AJAX and I kept getting 404s. Spent at least 10 hours on stack overflow trying to figure out why the server wasn't accessing it only to find out today that I was both looking at the wrong directory and also working the file name wrong.
I think I just need to walk away from programming for a while... 😧3 -
My team's "Scrum" daily stand-up meeting lasts for 1 hour. We spend the first 30 minutes listening to the Product Owner's "updates"5
-
Scrum is terrible. Is there another agile technique that isn't as bad? Like maybe one that will let us do our "scrum" once a week for like an hour? My current project really doesn't lend itself to once a day scrums. Literally my scrum input is "I worked on what I have been working on, and I'm gonna work on it more today. Impediments are literally the same as they always are because my life is no longer my own."5
-
Once upon a time we were normal remote professionals and our sprint meetings were characteristically professional, no more, no less.
Until.
one of our juniors, a Southern sports-bro type, suddenly started saying "SIR" to the scrum master in literally every sentence.
"Good morning sir". "Yes sir." "Thank you sir." "I can do that sir."
SOMEHOW this plague caught on to half of the male members of our team like we're in the military or something. We have ONE veteran and ZERO Indians and I can't think of a logical explanation for why we're suddenly sir-ing each other and people who aren't even high level executives.8 -
Had a conference call and one of the guys said something along the lines of "I can handle the load (ticket load)" didn't even thought about it my mouth instinctively reacted with "that's what she said".
A couple of guys laughed but the other few just "wooooow"ed like if I had thrown a 9/11 joke.
This is not a rant perse, just a reminder that if I ever launch my own startup I shall look to hire "joke sensitive" people to make my scrum meetings as awkward as possible.4 -
A coworker during scrum today: "Last week, I worked on the new feature. Also, I have an announcement for everyone: I'm going through a divorce so I moved in with my parents and will be working remotely for a while. I have no blockers...except for the divorce."1
-
A delicious Sprint Planning 😋
It was a hard sprint (SCRUM methodology), but finally we were on our next’s sprint planning meeting. We had a lot of tasks to define and estimate. For the first one, we all estimated the task with 5 points, and for the second one we voted for 3 points. We were coordinated XD so, our boss said “let’s do something, if all of you vote, let’s say, 5, and another votes for a different number, he or she’s gonna buy us a six pack of beer”. Challenge accepted.
Two partners and I have to buy beers for this friday after work 😂 I don’t even mad 😋🍻3 -
Product owner/Scrum master: "We don't have any time to review pull requests. We need the development time for features"6
-
-Be a university student
-Work with SCR(OT)UM for the first time
-Divide tasks into 3 day sprints
-Watch the SCRUM master go nuts and the project fail
Never again3 -
The whole point of having a daily scrum is to let your team know about the progress you've made from last day and what you'd be needing to stick to the sprint plan.
So ideally everyone has 30-60 seconds to give a gist of their activities. And a small scrum team would be productive because everybody is on the same page.
Our scrum meetings usually wait for all of us to assemble with our coffees and donuts, sit down, joke, and then agonizingly go over everybody's existential crisis as a developer because of the task they've been assigned to has too many dependencies. And this happens every single fucking day! These "scrum" meetings tend to go for 1 hour. FML!5 -
We use scrum in our company.
And with scrum I mean we don't have a scrum master, our senior developer is the project owner, we estimate in hours and the estimate is binding, so you are not allowed to work longer on a task than the estimate.
So yeah.. "scrum"4 -
We got a new manager. He has us doing scrum meetings in the morning. He is slightly amused and annoyed that I refer to this time as:
"Software developer bonding time."2 -
I work remotely and have to attend a 'scrum' call everyday which I fucking hate. It gives me anxiety as I already dont like extensive phone calls.11
-
Bureaucracy is the biggest impediment to progress.
Instead of putting a brick wall in front of you by saying "The PO said that you created a bug", learn how to communicate and have a horizontal hierarchy, for fuck's sake.
Even if all my tests passed, they still throw other bugs in my face and call it my fault. Fantastic. I love Scrum. This is not Scrum, this is abusing and not respecting Scrum.
Stupid rules, stupid people.1 -
Everyone working a non-tech/programming job I talk to finds this daily standup meetings we have utterly laughable and micromanage-y.
Someone at work thought it would be nice to replace Wednesday's standup half hour with a "Wellness Wednesday" session. We had to find something around/on our desks at home that has a lot of meaning to us and show it and tell everyone why it has meaning to us. I literally couldn't find anything here besides my trusty pistol and I was like "it would be inappropriate to flash a firearm on camera in a meeting, blah blah blah." Maybe I should do more awkward shit like this so they stop this madness.
This is getting ridiculous.9 -
The development process that my boss called SCRUM. It was anything but. Management thought they could make us do more work than possible.2
-
So we decided to adopt Scrum where in manager(scrum master) picks the stories for dev, changes them during sprint and also decides the complexity of task. so much for a servant leader!!3
-
When your sprint review is turned into a 5 hour argument about how to effectively do scrum and all you want to do is code.1
-
I'm a developer with scrum master certification but the company wanted me to use their existing google spreadsheet for managing the tasks of 60 developers. I study agile for nothing. Kill me now please. I'm out.5
-
Sorry for the so many jobs I didn't applied because I thought Scrum is a js framework XD omg... Actually... omg.4
-
So you have an organization that flirts with scrum and wants to be agile. You have non-crossfunctional teams who don't know what agile is. You have product owner who doesn't want to do backlog, but instead acts like project manager and asks for statuses and assigns tasks to peple. He wants the teams to find out what needs to be done and fill the backlog themselves - and then raport to him. You have business owers who noone knows who they are. You have project managers, who don't fit the whole scrum hierarchy. These project managers insist calling scrum masters "team leaders". Also these project managers think scrum is silly and don't want anything to do with it. And then you have higher program management that think this whole scum thing is better than sliced bread and everything is going just dandy!
Oh yeah, also highest organization management thinks that we are on the right track. We just need be more agile but less agile and work more efficiently whitout really saying, what the hell are we supposed to do.
Basically every day is like going to the zoo. Without the fun part.6 -
This is my first time experiencing agile development with its daily scrum meets, and I hate it already.2
-
Program manager who handles scrum of scrums asked our scrum master to slow down. Our velocity and quality is making other teams look bad...
The problem is, no one from other team wants to learn anything from us on automation/cicd. They are good even though manual.
Not sure what to do. Biz is happy with us...6 -
Scrum CSM course: it's good to accept that we can't be perfect.
Also CSM course (1): if it's not followed perfectly it's not scrum
Also CSM course (2): scrum won't work in your team unless the whole organization adopts it
CSM course provider after cert: $1k CSM cert isn't enough to practice Scrum responsibly12 -
How bad it feels when it work in a place where Agile and DevOps are mostly abused buzzwords.
Forced doing "scrum" with:
- half of the team providing endless daily reports instead of focusing on the 3 questions
- a scrum master that is barely reachable
- a product owner that would not even make a decision
- a sponsor that pushes us to go faster regardless of current technical debt (it's important to look good to other sponsors!)
- doing all possible scrum ceremonies with no value added
- not even estimating stories
- not even having accurate description in stories. Most of the time not even a description.
- half of the team not understanding agile and DevOps at all
Feels so good (not). Am I the one in that boat?? ⁉️
What's the point of doing scrum if implemented that badly?? 😠6 -
TL/DR;
Worked as outsource where Scrum was misused. Please use it as a guide rather than law.
RANT;
Just remembered working as an outsourced programmer...
The Scrum master got us all... all of us... everyday... most people on Skype too... to update with our plans, issues etc.
So including the time trying to get everyone to sync up on Skype at around 9am, introductions, updates from EVERYONE... back and forth suggestions... I'd be starting near midday.
The task was related to making a tile based menu system that was populated with items from a backend... On paper, I only really needed to talk to the 1 artist and the 1 backend guy to understand the request / responses.
But even the art assets were arbitrary sizes... untileable... at the time they even had to be power of two too... My god, getting them changed was a nightmare...
In the end I was too slow for them.
Gladly.4 -
Funny story:
We were going through Sprint Planning on Monday. We got through all of the tasks that we knew we had to get done, then we started going through the backlog to see what we could pull forward.
The guy running the meeting (who's not actually a Scrum master, but whatever) get's to a task, reads it aloud, and goes, "That doesn't ring any bells. Brian, it's in your name, it says it's from May, do you know what the status of this is?
Brian reads through it for about 20 seconds before saying, "That date says it's from 2017. I don't think we need it anymore."2 -
the amount of micromanagement enforced in our scrum routine is getting ridiculous... but the PM seems to be happy with this14
-
Scrum Master? More like Scum Master.. The nutjob sends a calendar invite for daily stand up for 30 minutes which extends to 50 minutes.. 50 minutes for a team of 6 people ? Fuck off.6
-
My daily scrum, the team I'm in doesn't care and just blows our 10min daily into a 1hour "talk about anything" meeting2
-
You remember my team with scrums that last more than hour? They just decided that it is not enough - we will have another, morning, scrum. I am looking for a new job.5
-
The panic when there are only two competent programmers in the scrum team, and PM says he is moving one to another team.
-
The stand-in for the person who normally runs the daily standup meeting (who is currently on leave) asked me today in front of everyone in standup if I've updated my notes. Fuck. Off.
So, I decided to be cheeky and add a comment to the daily standup notes automation task in our project management software that we should just include all of the recipients of the daily status update email in our standup meeting every morning, this way we don't require a OneNote space to update as well as an email.
If they tell me that's not the purpose of standup, then hopefully someone will realise what they've been doing all along.
Let's see how that goes lmao.2 -
Bless whoever came up with Scrum! Now when the PO requests a change from me, I get to tell him: "please refer to the scrum master and discuss potentially adding your suggestions into the backlog items for the next sprint."1
-
most of the self-described "AI experts" on my Linkedin feed were "scrum masters" not even half a decade ago. something to think about2
-
~ before sprint starts, suring planning phase ~
Me: “There’s no chance this will be done in a sprint”.
Scrum Master: “Great, let’s just mark this as a risk and continue”.
~ two weeks later ~
Me: “oh jeez, I don’t think this task will be done this sprint!”
Screwyou Master: “Why didn’t you raise a flag sooner so we could plan better?”
~ Me proceeding to jumping off that beautiful skyscraper office ~5 -
This is how Scrum works:
Three coworkers are in a Scrum Team. One of them is also the Product Owner and the Scrum Master... The PO decided this Monday that they need to add a new feature for the Tuesday night release, which is estimated at 80 hours. I told the other two in front of a manager that this is not scrum. Nobody gives a shit.2 -
Since there is Scrum i am programmer , tester , software engineer , networking guy and application manager. Thank you Scrum didnt know that before. And i have no idea what i am doing right now ....2
-
So our scrum team just bought a collection of nerf guns. We were able to repel quite some disturbances from outside the team.1
-
Our agile scrum team has finally shattered into two parts.
On the one hand we have front-end guys.
On the other hand we have backend- /dev-ops guys.
The FE guys don't care about the BE guys business.
They don't join pairworking and only noticing things that went bad, when a Backend guy has caused it.
Goodbye fullstack dev-ops team...
I really dislike that arrogant basterds.
Frontend Hobo-Bitches...! -
So the company decided to go agile. I am now a scrum master. And we have the local product owners and all. They made us do daily stand-ups.
I don't know what is a scrum master. Nobody knows what the hell is a stand-up. It seems to be an akward 30 minutes every day, when local product owner asks questions and demands status reports.
I did some googling and it seems that the scrum master is supposed to just support the team and solve problems. In our version the scrum master finds out the system architecture and requirements, fills the backlog, does the system design and reports to the project manager(s). Also reports to the clients about the general project status in an executive meetings. I also do the sprint planning, in which we fit the vague features that we are told into time tables with ready told dates.
Oh yeah, the team is just 2 guys. One of them is me. And the other guy relies completely on me to daily tell what to do, review the work and also answer all the project and company level questions that pop into his mind. He gets angry if he doesn't receive ready-thought solutions to all problems, since "you're the boss and it's your job to tell us what to do".
This is going to be a great year.4 -
We have this bloke in our scrum team who never does shit. He always says that he spent the week studying technologies and what not. How ever looking at the time he has spent 'studying' he should be the scrum master by now...
Who else has a bloke like this in their team?2 -
The feeling when your scrum master or lead ask you run the automated tests against the application though they know the application is down or not working.
-
Fuck me I'm pissed. This sprint, my tech lead has been away and a senior dev has been covering for him. We plan a load of work and distribute stories and we churn threw it quite well. However, my senior dev says let's not deploy until all the works done. I was like, how is it going to be tested? He was like well it will be fine because it's all one test. Bs. We now have 2 days left, tester is getting stressed because they don't know what to test or what's been finished. Scrum master is asking why all of it should be tested at the same time and I'm here like this is fucking dumb. Also the tester decided to start testing with the most complex piece of work, rather than prioritising.
Starting to wonder if I'm just the outsider or whether no one understands that granularity is better.2 -
man, SCRUM is a FUCKING chord, sometimes. Isn’t it supposed to make us productive and not hog time and resources?5
-
The person sitting next to me in scrum is literally eating honey roasted peanuts out of a cereal bowl with a spoon6
-
I like our daily stand-ups, but our team only does it when our scrum master is present, if he takes a day off, no one cares about it
I think it's healthy for scrum teams to have that every day
What do you guys think? Are you also doing scrum? How bug is your team?6 -
[tl;dr at the bottom]
(Project Team Group Chat)
dev: @Desing team, i have a question, there's a required field missing in you design, can i go to your desktop to get an quick answer/explanation about that?
design team:....
dev: hello..?
PM: [writes a huge text to tell me that i can not interrupt them even if its a blocker and that we (dev team) shoul write them down and tell them only once a day in the scrum meeting]
dev: uuumm ok
-next day-
dev: so about that field, why did you...
Client: WHAT? There's a problem with the design!? oh boy, lets re-check every view right now with the whole team!
(it took like 2 hours, the field was missing just because they forgot that feature)
PM: okay, @DesingTeam, answer any questions from developers when they ask you...
tl;dr
we spent almost two hours with the client just because desing team didn't want to answer me a little question -
TFW your boss likes you enough to set up a full-time offer for you. 😗
TFW the offer is $20K below the average salary. 😬 -
My boss was told that dev team cant do TDD because they are agile and following scrum. Did not know what to say.😏2
-
I really hate it when I work on a user story consisting only of a cryptic title: "Implement feature X".
Esp. when I missed planning during a holiday and can only wonder who in their right mind would have given it 3 points.
Why thank you.
Sometimes, just pulling the acceptance criteria out of somebody's nose takes days. It doesn't get better once I realize that not all external dependencies have been properly resolved. It's worse if there are other departments involved, as then you get into politics.
Me: "We are dependent on team X to deliver Y before we should have even planned this ticket. I'm amazed that our team was even able to estimate this ticket as I would have only raised a question mark during estimation meeting. We could have thrown dices during estimation as the number would have been as meaningful and I'd have more time to actually figure out what we should be doing."
Dev lead / PO: "I understand. But let's just do <crazy workaround that will be live until hell freezes over> temporarily."
It's borderline insane how much a chaotic work flow is branded as agile. Let's call it scrum but let's get rid of all the meaningful artefacts that make it scrum.1 -
Started a new job at a big firm (previously came from a startup). Both do "scrum". Still have my mind blown because at the new job, we have people join the standup of which NOBODY in the team knows what their role is on the product...
Does this happen often in big corporates?5 -
currently thinking about asking my boss if I can make a training / qualification for scrum master.
when PM is trying so hard to shove *his* scrum down our throats and at the same time tries to block any scrum-related criticism of team members that question his behavior as SM AND PO, then maybe convincing my boss to become the new SM and shoving ALL the scrum down the PMs throat is the only chance to have a (bit more) bearable working environment in this project.
in my opinion, he has too much power.
whatcha think? any SMs here, and do you like what you are doing?8 -
to everyone who complains about poor methodoly usage:
I had a solo ptoject. I was told to do scrum. I had dailies.. with my PM. we were moving JIRA tickets around. -
Fuck you and your agile and scrum
nothing will fix your laziness and stupidity
I hate wasting time for this bullshit2 -
Agile/Scrum is the worst project management style in software development.
Rather than focusing on delivering a feature or changes on the project, everyday there is always a meeting that you need to attend to, other than the daily huddle. And those meetings are none of your concern or why they needed you there
And my Product Owner and Scrum Master does not know even though how software development cycle works. When you discuss technical details or constraint to them, they either look confused or don’t know what to say and just say “If you need anything, always communicate or approach me” even you already told them the issue.
Or maybe we are doing it wrong. But it is been 5 years when they implement this Agile/Scrum and we are still bad at it.
Just ranting4 -
My scrum master said, 'I would optimize your work hours.' He's monitoring how much time every one spends on browsing non-productive webs like devRant. How can I fight back? :(6
-
just as Erik Meijer said scrum is the most stupid shit in modern development process. I worked in an organization hires ppl as full time scrum master, which is joke. each day the asks what did u finished yesterday and how long it need to finish the task assigned to u. btw the scrum masters know nothing about programming. come on man how can u finish any serious shit in one day and who cares how much shit others finished. each week just attending those freaking meetings without coding. each programmer are assigned at least 5 bosses, and what the fuck is product manager doing, it's not adding indirection can solve anything.2
-
Newbie Agile Team: "Hi Scrum Coach, we studied and implemented the Scrum methodology, but we are late as before and our software is buggy and shitty as ever, how is that?"
Agile Coach: "Scrum Methodology is easy to learn, but difficult to master!"
Newbie Agile Team (chorus): "Oh coach, Fuck yourself daily, with your coffe thermos, standing up and once per week retrospectively. If you'll come at the next review meeting, we will gangbang your ass in front of the stakeholders"5 -
Does anyone else work with that one guy who doesn't know anything and always asking others to do his work, butt in the scrum meeting his daily updates would make management think he was Bjarne Stroustrup reincarnated?5
-
Using a chart at the retro to compare how many story points each developer completed during the sprint.
That’s it.4 -
I really hate that my boss will come 7 minutes into our scrum and he speaks for the next 10 minutes…like what actual hell?2
-
Java Dev: "Does Josh's team own this java service?"
Scrum Master: "They did the dev work but we own it."
Java Dev: -
I wrote a message to the scrum master complaining how unfair is that QA added new acceptance criteria after I finished the story
he sends me back a GIF
and that's all -
I'll be starting a new job soon, and I'm sure there will be a chance to implement some form of process for the dev team to use...
To Scrum or to Kanban?2 -
customer claims they do scrum but they have quarterly planning events (2 full days) where we need to estimate and plan everything for the next 3 months.
Manager: "last quarter I calculated your velicoty so now you get 4 story points per sprint per developer"
Team: "But you started us off at just 5 per sprint that's too small"
Manager: "Ok but if you only did 4 why do you now want 20"
Team: "Because it's arbitrary and we say we want to"
Manager: "1 story point is 1 day"
Team: "story points aren't time"
Manager: "4 story points is 1 sprint"
Team: "but a sprint is 10 days"
Manager: "the junior dev can do 4 story points per sprint and the senior dev can do 4 story points per sprint"
Team: ...8 -
When your project leader wants to work 100% scrum and the steering committee, up front, wants to know exactly what will be delivered, what it will cost and when it will be ready..3
-
A long struggle to change a nazi enforced scrum methodology that cut our efficency, technical standard and dedication to the product by just working on fragmented features that were added and removed by the wim of the PM.
Job offer in hand as senior dev somewhere else, I stayed, got better eventually. My old boss kept complaining on me for years in performance reviews that I did not respect managements decisions.
Two years of badly led scrum regime left our product in a spagetti mess that is still trying to be untangled.
Til this day, if I hear someone mutter "scrum", I feel a strong need to run far far away.6 -
I find Scrum Masters useless. I'd rather have a developer replace them. Am I overseeing their value? Could someone enlighten me?
I also think that if a group comprised of smart people, things spontaneously happen without needing a handrail to walk along.4 -
When you are stuck in between a very interesting Spring 5.0 GA release webcast and a stupid mandatory daily scrum call!
-
Scream, the agile framework for when scrum would require too much change.
https://docs.google.com/document/u/... -
Does anybody else feels like scrum's daily is utterly useless when working day by day on site?
I mean, we talk to each other either way, all day long. Scrum acting like this is the 15 min of whole day we will have the chance to speak...2 -
So my team (read: not the team at all) has decided that we are going to scrum. Someone ease tell me it's not as fucking tedious as it sounds. Sounds like it's just more meetings. Especially on this team which is actually already pretty agile. And the way our "certified scrum master" describes the retrospective sounds like it was designed by the type of shitlord PM that forces everyone to wear ugly t-shirts to the mandatory company barbecue for "team building". Please tell me he's just a terrible salesman.7
-
The Dev was asked an update on his sprint task.
What task? The Dev asked.
"You know changing our git branches from master to main" says the Scrum master.7 -
Alright, let's talk about Scrum Masters. Honestly, I just can't wrap my head around why they're even a thing. It's like someone decided to invent a job title for a role that's already covered by other folks on the team.
I mean, think about it. Who's usually sorting out the team's issues, making sure everyone's on the same page, and keeping the project on track? That's right, it's the project manager or the lead dev. They're already in the trenches, dealing with the nitty-gritty, so why do we need this extra layer?
And don't even get me started on this "servant-leader" nonsense. It's like they're trying to be the team's buddy, but they've got no real power to make things happen. It's like being a king without a crown. Who's going to respect that?
Plus, having a Scrum Master often just leads to more red tape. Instead of getting stuff done, we're stuck in endless meetings, talking about process this and methodology that. It's like we're more focused on how we work instead of actually working.
The best teams I've seen don't need a Scrum Master to babysit them. They need a real leader, someone who's not afraid to make the tough calls and who can give them the tools they need to kick ass and take names.
So, in a nutshell, I think Scrum Masters are about as useful as a chocolate teapot. It's high time we ditched this outdated role and got back to doing what we do best: building awesome stuff.8 -
So I was attending a Scrum Master training recently. During the introduction, the coach is making sure everyone understands why are they even on this training and stresses out that for a company to be able to actually become agile and survive the transition, people of different levels and roles/responsibilities should get familiar with Scrum, not only IT/developers.
Coach: I can see we have developers, testers and people from operations in the room, good. Too bad there's noone from the actual business. Anyway, who decided that you should come to a Scrum training and become certified?
Group: Well, the business..
#ironic1 -
Oh my fucking god, we're doing SCRUM, why does every task get stuck in review limbo and take a sprint and a half minimum because of it.
-
When you work for a multinational organization that's adopting scrum. We don't swarm, our PO isn't even in the same building, and one of your teammates hates git (loves TFS).
Fake it till you make it I guess?3 -
Having a meeting to decide, when to have other meetings...
Scrum, scrum of scrums, workstream, planning, pm ,design review, architecture review, Sprint review on and on....on and on on...why can't i simply code:(4 -
Does anyone else have one person who makes them not want to go to work everyday. That person for me is my SCRUM master.
-
Facepalm Monday...
My collegue denies to provide breaking changes in our login API in a separate version to the other teams depending on it.
What is the reason for his stubborn rejection?
It's scrum. We haven't planned the effort for realising a versioning concept for our API.
Let's build it in the next sprint as a part of live deployment strategy.
The point he miss is that the ProductOwner wants his API change deployed during the next sprint.
Additionally, it is best practice, having a compatible, deployable product after each sprint, without any risks.
Furthermore, another best practice to provide your API is one URI without a version part holding the current development of the API. And URIs with a version part in it to keep a specific request/response structure and behavior.
What really grind my gears are sayings like 'if the other teams had well programmed their software, modifying our API won't have any effect on them'
C'mon dude. That's far from reality, as anybody knows.
I can't accept, we provide unprofessional API builds, as he is going to do.
So, i have to spend my time and energy to change his mind, together with other software-architects, planning the big thing API-Gateway *sigh*2 -
Just a reminder guys especially who do agile(scrum). TEAMS SHOULD BE HIGHLY ALIGNED BUT LOOSELY COUPLED!5
-
8 months into a complex Agile project, managing multiple Scrum teams -
I still feel it would go much faster if I just do it myself.1 -
My coworker has been freaking out that our company doesn't do Agile or Scrum right and it will negatively impact his career. He claims that some elite company will want him to prove he worked in well oiled Agile machine. He also claims his last company had it down to a T yet he voluntarily left so they couldn't have been that damn spectacular.
I'm on my 7th company and no one does this shit "right", everyone makes it up. Also it's impossible to prove that you worked in a perfect environment to a different employer, if they even care at all. If someone asks, just tell them what they want to hear because no one actually works in this mythical world of Agile perfection.1 -
Today we received a new scrum master. Seems nice enough.
Now he wants to remove the fucking swimlanes from OUR jira board and change them into separate sub tasks.
Wtf.4 -
Let’s start the week great with a scrum master complaining about a functionality that isn’t working, and a coworker that’s pointing in my direction.
Go point your finger elsewhere (***)3 -
Long one
So our newest team-mate has made a channel dedicated to make fun of or scrum master, then I send him a pm saying to cut out the childs play, and we need to act professional.
Then he tells me that our scrum master is okay with it, and really looks like he is!
SM said this making jokes about him brings the whole team together and makes us a better team!!
WTF...
Really WTF ... am I the bad guy for caring about my team??3 -
dev1: where are all scrum masters?
dev2: WFH
dev1: can I do that?
dev2: yeah, but you need their approval first3 -
I'm absolutely fuming why on earth would someone try to apply exactly all rules of a theoretical concept. I hate those so called "scrum masters". We can't apply all rules of agile we're not machines. There's real life and theory.1
-
Screw Scrum, screw it very much. Is it a task or a story? Oh let's make it a story to track points. What are points, really? *20 minute grilling always follows* Well they're kind of a roundabout way of talking about time without talking about time, mkay? But last time 2 points took you a day, what gives now? What do you mean points are for internal use, but how will management plan ahead for next quarter? Ok, let's mix in all those new people, and propotionately bump the expectation for the sprint, mkay? Yeah, they did 34 points per sprint over there, we'll just add those in. Oh, and by the way, after the 4-day estimation session we had where everyone was seizuring, I scheduled us at 645 points for the coming quarter, mkay? Don't worry, I added 15% for the "unexpected dtuff" so you're safe. Fuck you scrum, scrum-fall, whatever you are. Lost a dev lead role once for being honest about it after a year with a team that loved me, and projects completed more or less on time. Been reconsidered for a dev lead role for being honest about it in another place. Somebody else peddle this kool-aid, this one prefers a walk-on role in the wall to a lead role in the cage.5
-
Our team moved to scrum a while back. But everybody still does story point estimation by mentally assigning 1 story point for each day of work it would require. :/
On top of that, management compares the performance of two *different* scrum teams based on the story points they finish in a sprint. :// -
Help. We're starting to feel the effects of unnecessary micromanagement.
We're a small startup. The kind with less than 10 devs spread across different domains. We've been fine with a Kanban approach as the velocity/flow of deliverables don't necessarily warrant a Scrum approach yet.
Our boss has been wanting to adopt Scrum-style sprints, even shoved and assumed that were doing these sprints and demanding Scrum-style reports (and meetings!!!) when they are, in reality,
1) unnecessary
2) a waste of time
Absolutely none of the team members want this. But our boss insists on having it. We like our boss, but lately things are getting out of control
What can we do to mitigate and prevent this?3 -
my boss doesn't believe in AGILE-SCRUM, hence android and back end is always out of sync and I always end up having to rewrite the code in order make it compatible with the back end, even though i have to post a new binary to the app store and play store not to mention get the users to actually update the damn app. How do I get my boss to adapt SCRUM?3
-
So i have some SQL skills. and I ended up some shitty business reports .
My boss will to implement something she read on internet (scrum).
I recommended her to manage her expectations. IMHO After implementing scrum, no shit is gonna change and obviously I was ignored and treated as a negative thinking being
Do you guys think this could work? Since we're a 4 people team and each one of us have different and non related activities10 -
The company i work for is getting into scrum. Hired consultants, product owners and scrum masters. First action was 'lets spend 2 days in meetings estimating the rest of the project'.
Agile as fuck3 -
Do you know that lady who waits in line at the grocery store for ages and when it's finally her turn she suddenly realizes that she might need her wallet somewhere from the bottom of her bag?
That's our current business analyst managing external dependencies like a boss... :D -
Is there a team that works truly productive and happy via an agile (scrum) workflow?
Or does it always distill down to an excuse for a chaotic workflow?
My experience and cynic nature has let me to assume the latter.
(That being said, I never had a dedicated scrum master to work with. So that may be the first of many problems.)4 -
Every unholy, directly sent from hell, refinement-planning i ever had since dealing with scrum.
Refinement: Good
Plannings: Fine
But the juxtaposition of both kind of meetings...
... destroys nerves
... desintegrate teams
... destroys lifes
*shivers* -
I'm at that point where I want to lash out at our team for not finishing a sprint. I've been doing the scrum master/dev role for months now and each sprint is incomplete since we have started the agile way.
Most of my team members are seasoned senior devs and my team's downfall are caused by not acting as a team. I'm the youngest in the team and have been acting as a babysitter for them.3 -
Am I the only one who feels like morning scrum meetings are a complete waste of time? At least in the way that my team does them. It's 30 minutes of "I did this thing yesterday, and I will continue to do that same thing today." All of this information can be sent in an email, but we insist on meeting every morning to say the same exact things.
For the past 3 weeks, the majority of the team has said the same exact things during scrum: "I continued to work on this big feature yesterday. Thank you." Like how does a detailed retelling of what this person did yesterday pertain to the rest of the team? It's just meeting for the sake of meeting, and talking for the sake of talking.
If you have this little technical issue that only pertains to work that this single person is doing, then meet with that person separately and discuss it. There's no reason to make everybody else sit and listen to information that will never be useful to them.
And most of the time, this scrum stems into spontaneous unplanned longer meetings afterwards. So suddenly this "quick" 30 minute scrum turns in 2-hours of meetings and a morning wasted on information that could've easily been discussed over email instead5 -
As a developer I never understood the intended benefit of standups. Issues + a scrum/kanban board like trello or GitHub project + a chat for quick questions or to schedule an ad-hoc pair programming session should be enough to make everyone know everything they need to know about the project status at any time.
Obliging developers to talk in a group session to reiterate in a more verbose way what they already wrote down when working on it, will make a lot of people uncomfortable. Talking too much or not complying to the talking rules is an expected side effect besides anxiety and reduced productivity.
If you want a talk show, hire talk masters.
If you want software development, hire software developers.
Don't confuse one with the other!10 -
I was in a meeting the other day which started with a introducing of the members and a basic explanation about scrum.
The meeting ended with the note form the client that the project was absolutely not allowed to cost more then X.
After the meeting a coworker asked who explained scrum to the client. And it was explained twice by two different people. -
At the end of the sprint half of the stories didn't get done due to lack of coordination to put 4 people in the same room and get them to agree on the solution.
During Retro my Scrum Master says: Are these stories not done because we haven't estimated them during sprint planning? 😂 -
When your SCRUM Master cancels the sprint retro because he knows all hell is about to break loose.2
-
What is the best way to work on a project with a team?, I mean, how to use git, runbots, scrum, kanbans, modeling, and the most important the deadline... D:6
-
why so little books about enterprise paradigm on developer (best practice/app lifecycle/scrum, etc) when so many resources about coding4
-
So I was reading Scrum for my exam all I can see was Meeting.
Product backlog meeting for 15 mins;
Enters to the office 5 mins meeting;
Sprint review meeting for 10mins;
Daily scrum 2 times meetings;
Sprint planning 3 hours of meeting;
Starting the next Sprint 30mins meetings;
Managing releases 45 min meeting;
Sprint Retrospective 45 mins of meeting;
Wtf? Do they do any work there?4 -
I'm really sick of people saying "WE USE SCRUM" like that was the solution for their shitty code or their "business core"5
-
of late my team has slipped in the rather irritating habit of not scheduling review meetings; instead they just announce during scrum that they'll have a review right after scrum. this just messes up the day. you go to scrum thinking 15-20 minutes, and boom you end up with 3 hours of back to back unscheduled meetings
-
I hate my scrum calls so much. People go into the fucking weeds and the scrum master is so clueless. Doesn't stop them and let people ramble. Jesus christ.
If scrum calls last more than 10 minutes, I think you're doing it wrong.1 -
I figured it all out, where all the bad code comes from, I know it now!
I think good developers need two things, an ego that makes them wanting to be competent and perceived as such and (very important) a problem with authority!
All the bad code is written by people who wanted to be liked by their teachers. The PM and PO are their teachers now and they make everything possible for them. Technical debt and human costs are swept aside when the authorities want a stupid feature now - because they have to like you and you need to be a nice pet to whip! -
I know your code is great and that you learned about scrum a month ago. But I didn't know the scrum training had to say you don't assign yourself tasks, mark them as done and be surprised when other team members haven't done them, two minutes to five the day before a national holiday (yesterday).
-
When i heard people talking much about scrum & agile things, but he actually never implement yet even worst he didn't really know about scrum it self, just STFO... I'm tired of all those BS 😪1
-
The previous company was working for, or scrum team was so in sync, complementary and top gun that we could finish each other phrases. Dream team.
-
My experience with SCRUM:
Everytime some say:
Lets try scrum.. couple weeks later dropping it.
Just use Jira instead, and meetings once a week.
I Never have seem (Official) Scrum working in a team for a long period.3 -
Can someone explain Scrum to me, like everything, what it is, why it's used, why it's effective, cases where it isn't effective, what the roles are etc, I've tried to understand it online but to no avail (need a childish explanation I guess)14
-
!rant
Doing the Professional Scrum Developer Cert today. I feel terrified by the thought I might be throwing 200$ out of the window.
┌( ಠ_ಠ)┘ 彡[$̲̅(̲̅200)̲̅$̲̅] ロ
Any tips highly appreciated. -
The scrum master cries out for the team’s burndown chart as he move more unplanned work into the current Sprint.1
-
Kind of had my first SCRUM-meeting couple hours ago. I'm a student and have a internship at a company. It felt so dull since me and my two team-members stood there and listened to three others talking about their project that we have nothing to do with. Then we got to say what we made yesterday and so on. Hopefully this is all in educational purpose?1
-
Does Professional Scrum Master certification add any value to a devs profile? I am asking because I failed in the first attempt. 😟4
-
I like scrum. I really love working that way. And imo the daily scrum meeting is pretty useful.
But now we have two of them every day. I don't know how to feel about it :/ the one mornings is good and all but the one in the noon just kills my focus1 -
'we don't develop with quality just for the sake of it, just push it to finish the sprint'
Another gem from my scrum master -
I'm a scrum sprinter using my agile-ity to dodge rock-rigid waterfalls.
My take at another lame joke.
But I still have my legs and can walk... -
Scrum masters are a joke. I think we should take half of their salary and tack it on to the tech lead and let him run the show.6
-
If you have not achieved the sprint and a meeting is scheduled why you have not achieved the sprint ... in the next sprint ...
-
Returning to tech after 3 years working with agile, training and coaching Scrum, Kaban and XP practices. Applying for team leadership positions. Advice?1
-
I’m in the middle of a 2:30h SCRUM meeting and the only thing I have to say is that Bill Cosby drinks would be less soporific.
Honestly, why managers can’t just hand out the tasks instead of forcing us to look at them discussing them?2 -
Today, I found a bad bug. I fixed it and tried to understand what happened there. Story description was ok, dev was done on time, review performed (1/3 of the time needed to developed), testers were happy: story was DONE.
I feel uneasy as all protocols had been respected, and still, the code was bad and features were broken :( -
It's refreshing yet odd when you go from a team with loads of meetings (mostly stand-ups and of that Scrum stuff) to one with only 2 weekly meetings.2
-
How to deal with micromanagment?
I just lose it when the team leader checks on issues on a hourly base, And dont get me started on the scrum master who checks the sprint status twice a day.
I can't quit this work but I'm losing mind here.
H-O-W T-H-E F-U-C-K do i deal with this idiotism??5 -
Group project at uni, we're learning how to do scrum sprints. So here's a small story about all the ways it can go wrong.
We assign scrum master and product owner roles, what do those do? "We want to do design tho" they say two weeks later.
I end up doing the organization part and structuring the backlog.
"Alright, you guys will be the frontend team, your tasks are X and Y"
No response
One day before the review I ask again
"So, what's the status" (well knowing that they didn't do shit so far)
They start scrambling around, and manage to do like 30% of their tasks at best, I end up doing most of the work for them.
Next week, new sprint, our tutors somehow don't notice that literally 95% of the code has been written by me so far.
"Alright team, hopefully you will do better this time, so and so will be your subteam leader since he knows this stuff"
No response
Some guys start working on independent things without collaborating with each other, sometimes replicating stuff I already did (but obviously worse).
So that's the situation so far, I really would rather kill myself than keep working with these guys, jeeesus1 -
Explaining to my Scrum Master EVERY morning from scratch the technical details of the story so that he can give his blessing to why the story is still In Progress column!
-
Scrum standups and standdowns at my university be like: "oh let's discuss everything that comes to our mind and talk about it for an hour" - Professors 2016
(Only ranted this because I had to take a huge dump and had to hold it for a hour ;_;) -
Fellow devs, I want to hear your opinions on Scrum and daily stand up meetings. Do you think they're necessary?
God, I really hate that I'm required to participate in a meeting EVERY FUCKING DAY.6 -
So I've been asked if I want to take the role of scrum master along with my job as developer.. I must say that I am quite interested in taking on that role and it's responsibilities, but I'm somewhat scared by the things I read on the internet (especially when combining it as dev on that same team).
Let's hope I don't become the bad guy in this story after some time by being an a-hole of a scrum master lol4 -
Upon every mention of the term SCRUM my mind is instantly pulled off topic onto rugby... damn you homonyms..
-
The first time you receive a recurring invitation from the client for a scrum.
"This just became a job!' -
It’s me or Scrum trivialize developer’s skill development? My company replaced almost all the training with Googling and “peer to peer training” in which some junior with no teaching experience prepares a presentation/lesson on some technology and then shows it to others.
Following this logic with all the true crime which I’ve watched I should be a detective.7 -
Whenever we have to do Sprint Retros i feel like i am trapped in self-help group.
Recently, we had to describe our work/team like we would do amazon reviews. That is, we had to write "reviews" about our last sprint.
I sincerely would like to know why we can't discuss problems like grown adults, if there are any. Why do we have to pretend we are in a space rocket, on a sailing boat, in a formula one race car or reviewing amazon articles to articulate our needs?
I feel like developers are treated like stupid, little kids, and the majority of the developers don't have a problem with it.4 -
We all know that one guy at work that explains and overshare stuff using a lot of jargons for the sake of using jargons at the daily scrum. Then it turns out, he's ranting about something so trivial, basically wasted a lot of time. And don't get started on meetings. Oh god. Please send help.1
-
Scrum con religion is after me, I either convert or burn at the stake with scrum masters holding hands and dancing around while chanting the scram commandments.
Scrum will kill every decent developer on the planet and replace them with frauds...
Scrum's stupidity is toxic it's like being exposed to radiation - it makes you mutate into a brainless freak! -
That smug moment when you've just come back off holiday and reel off all the awesome shit you got up to during the scrum stand up meeting 😏
-
What is the point of doing retros and giving feedback, if the fucking scrum master is not going to enforce it?
I hope we can rid of this stupid scrum master position. Don't get me wrong we need managers, but we don't need glorified task readers.2 -
Should you get tasks from the backlog when everything is done in actual Sprint? Or it is a good time to keep learning while waiting for next Sprint?3
-
I hate my Scrum Master. Normally he doesn't even checks pull requests, and when you need his help, 80% of the time he's missing. Now that our boss is the new Product Owner of the application, the SM is bugging us A LOT
So fuck him, go away to do whatever the fuck you did before. Stop pretending you "work" -
Has anybody experience with Scrum in small web development agencies? Especially estimating stories with story points instead of hours/days?
We have a new junior project manager, without any practical experience working agile, who wants to establish scrum because what he read about it sounded so good... I already worked agile with kanban before and I loved it, but I only have little experience with scrum.
I think scrum, or agile in general, won't work with the clients we have. Most of the time, our clients have a fixed deadline, a fixed budget (either money or time) and they know their requirements, so there is no much room for beeing agile.
Regarding story points, I just adding an unneccessary layer of abstraction, because the customer wants to know how long a specific feature takes. Sure, story points are just another, more dynamic unit for time, but then why nut estimate in static time unit in the first place? Another fear I have, is that some devs may be more ignorant regarding deadlines and expectations on customers side. "yeah I'm working for 10 days on this story, but it's 8 points!" instead of informing the project manager "Currently I spend 2 days on this feature, we estimated 3 days, but it seems I need 3 days more".
Maybe I shouldn't be worried, but it would be great if you could share your experience and learnings. Thanks in advance!14 -
scrum my ass! the whole company(especially the marketing) must be aware and agree with this methodology and not only the devs.5
-
Scrum-meetings-and-process-planning meeting. Not a joke!!
It was actually called like this and took 2 days. We planned how we are going to try scrum... In the next retrospective, we were back to the way we were doing it before. -
We are in a course for the scrum certifiaction. Most of my partners are more concerned about they can't take the decission about using scrum or not. Is so sad because os a really small organization.
-
How do you deal with a toxic workplace environment. More specifically a senior that don't want to take responsibility and a SM that takes on more a role of a project manager than a scrum master?
Any advice would be great
For context I am a junior but work for nearly 2 years on this project1 -
POs and scrum masters - looking for alpha testers for a side project I'm developing.
Http://blystr.com
🤘🤘🤘🤘2 -
Tl;dr any tips for new scrum team ? How to start with story points with people that dont know eachother?
More:
Its for our team project at uni ( 8 people 1 year). Yesterday we had our first meeting and the hardest part was asigning story points. Or asigning some benchmark value for story point.
Looking for some practicall tips since uni gives us all the theory we need. ( Does not mean I know all the theory :D )6 -
Real programmers use macs in a coffee shop. Perfect for collab and scrum.
Desktop turtles get over it. You're no longer viable.4 -
!rant
Use BitBucket Cards to manage your issues as a Scrum Board. It makes your life way easier!
http://www.bitbucketcards.com/ -
I'd like to learn SCRUM/AGILE/JIRA or whatever management thingie is available out there that helps to manage projects in a team. anybody can share any link/blog/video? thanks6