Agile my ass. Stand ups should not take 40 min.

I once had a manager who would, at every stand up, ask everyone if there was a better way to solve their problem. She did this even if the team had already decided on a solution or even if there was no problem at all. She wouldn't let us continue the stand up until we had proposed a new 'solution' that was close to her 'suggestions'.

Some of my favorite suggestions were: "Are you doing everything you can to not make it too 'spiffy' ?". If you said yes the follow up was always: "can you tell me how?"

Then when you said you hit a bit of a bump yesterday due to something unexpected she always demanded that you pair programmed today. Now I don't have anything against pair programming, I even think it's useful from time to time, but being forced to sit next to someone or have someone sit next to me every time someone encountered something unexpected annoyed the shit out of me. Needless to say no one had any problems to speak of during stand ups after a while.

Whenever I was sparring with one of my colleagues she would always join in and start proposing 'solutions' about technical problems she didn't even understand. Again, she wouldn't back down until we had accepted her 'solution'. We would then go to a different room and hope she wouldn't find us there.

This went on for months, until several people had disagreed with her so much that it ended in shouting matches.

It still makes me angry when I think of one person crippling a team that much. I took my issues to her, to HR and finally to the CEO directly, but no one did anything about it.

Finally one of my colleagues decided to quit. After he handed in his two weeks notice our manager came to me and asked if she could talk to me in private.

She told me that she didn't understand why our colleague quit and she thought everything was going great. This was after just about everyone had told her that they hated how she acted and that if she wouldn't stop they'd quit. I had told her that myself twice.

She then proceeded to tell me that I was the most valuable employee and that the company couldn't go on without me. As a gesture of their appreciation for my invaluable effort, she was so generous to offer a salary increase of 50 euro, before taxes.

I laughed, said no and handed in my two week notice the next morning.

I vowed never to work with fucktards again, and I haven't since.

!rant.
I've worked for about two months at my (first) job. Its amazing.
We create audio/video software for the products we make.

There are 9 programmers besides me, I'm the only junior. And I'm still learning my way around the code, but they still value my input.

We only do stand ups for 5-10 min, like it should.

One if my colleagues helps me often when I have questions, so I've nicknamed him ducky.

My pm is awesome, he's great at coding and a great manager.

When we work overtime, the department pays for delivery food and drinks.

And we've already gone on 2 trips with the department, mountain biking and a BBQ.

I love my job and I hope that I'll soon be good enough to ask less questions.

Let's see here, we have:
🤡 Creepy Cackle Guy: watches videos all day and cackles like a hyena, plus constantly farts, and complains a lot. He gets everyone gassed up, no pun intended.

😤Bitchy PM: argues with you about every little thing, lies to pad her metrics while screwing the dev's metrics over. Also lies about what clients say to force launch or what she feels client should do. Rude to clients & co-workers. Runs and tattles to higher ups when people call her out on her shit. Nobody can stand her, she get's the entire office upset.

🙉Darth Vader: I don't think this one needs explaining. He breathes SO freaking loud you can hear it across the room. He also won't talk to anybody. Ever.

🤐The Non-Stop Flapper: nice person, but chats you non stop about their mundane life events, even when your status is set to busy or they know you're swamped. Asks irrelevant questions all day, every day. Heart of gold but needs to reel in the chatting.

🤬 Mr.Rage: whines about EVERYTHING. I mean everything. Has also thrown his food on me once over a joke about pizza. Wants to move up to programming but cant program.
---
So between them all, I scream on the inside daily. 🙊😫😢

Admin work, because its all manual:

- Each new project has to fill out an Excel tab in a workbook, with a list of all the major tasks and who is responsible. This then needs to be used to create a Gantt chart, manually, in the same tab, showing in what month a task starts and ends.

- Every month we have to manually enter status updates into a powerpoint slide on a shared deck. Which has a collision at least once per month.

- Once a quarter we need to do something similar as the powerpoint slides, but into a word doc instead.

- Once a week we need to track our time on projects in a tool that can't be integrated with (no API or anything). Meaning we can't link up a ticket tracking system to it, so again, all manual.

- Once every 6 months a new round of research funding opens up and we write proposals. The status for which are tracked in another Excel spreadsheet, manually, once a week until the deadline.

- The instructions for what to do with the proposals are so vague and badly documented that there is an unwritten rule, that for the first time you will have to ask a bunch of questions to the project manager. This is accepted by everyone and its just the done thing.

- Everything is stored in a dropbox style system, which has become so cluttered I can only find resources by saving the links sent out previously.

- Some of these updates / reports also get a 1 hour meeting for everyone to stand up and read out what they've entered.

- From time to time random things will need to be reported on to the higher ups (how many publications, research papers, patents, times and dates etc.). Again rather than a tool, a new Excel spreadsheet is whipped up and emailed to everyone on the team. Whoever sent it out, then has to merge the 20+ copies into 1 doc.

- Some of the staff (mostly the devs), use a ticket tracking system to keep track of everything. Management refuse to use it to track the things they need. Instead we have to copy paste from it into the word docs, powerpoint, excel etc.

- By far the most annoying. Management force all the above as they need the info for finance, accounting, legal etc etc. So we have to do it, but whenever there is a question from legal, management send the question to us. So despite having documented every facet of everything imaginable, it all gets ignored in favour of endless emails.

I once tried to to put an end to all of this madness by proposing the use of a ticket tracking system, and then building reporting tools on top of it.

... I was told that it "wasn't appropriate". Still don't know what that means.

Daily stand ups can be like this...

Help my team get a new token for the stand ups... We are thinking about something more orange...

An old company contacted me, seemed remorseful and said I probably didn't want to work there again but kept pushing. Eventually he said a high salary and I figured ok they had easy projects and the overpaying would beat the underpaying they did while I was there, right?

The new lead dev at the place took a month to give me work, tried to pressure me by saying she was going to tell management they are behind because of me, and then progressively stopped assigning tickets to me and assign-then-reassign them from me according to my schedule/predictions I revealed during the daily stand-ups. Why hire me at all. Then they said they changed their business direction at 3 months and let me go. What a waste of everyone's time.

Someone needs to turn verbose mode off on my boss.

When your morning stand ups include non-tech personnel and you need to get back to the code

is it just me or daily stand ups feels like a bunch of virgins sharing thier first time feelings and details ...

Story Time.

TL;DR - Because of Corporate PTSD, I replace the word "everyone/folks/guys" with "Team" when I'm addressing my colleagues, whether it be an e-mail or verbally (F2F/Zoom/GMeet).

In 2019, An office job I worked at, a new Vice President joined the company (the same one who told me he saw me in his dream).

We were required, on a daily basis, to form a circle and one-by-one everyone would out-loud say their yesterday's and current day's tasks updates.

So before the VP joined, everyone was free to initiate their turn however they wanted. Phrases like "Hey Everyone", "Good morning all" or "Hi All" was all around acceptable.

But the moment he started joining the stand-ups, he felt the need to change this phrase to a standard "Good morning Team". No other variations of this. Only and ONLY these three words.

Why you ask? Because saying Good morning is good manners and using the word "Team" strengthens the bond between co-workers and increases collaboration and creativity.

Some colleagues were bound to forget this and they did, which resulted in the VP blasting at everyone for doing so. He would show genuine rage over this, almost as if the company would go out of business because of us, not complying to do so.

Now imagine, you get up at 8 AM, get ready, commute, and get ready to speak for the standup and you get yelled at in front of everyone, FIRST THING before you start working.

Needless to say, it would kill everyone's spirit for getting their day started but nobody could speak up against him because obviously, he was the VP of the company then.

And oh yes, our CEO fired him 5 months after that because he (the VP) got slammed with a pedophilia-related lawsuit, by the parents of a 5-year old.

My stress ball has become the 'talking stick' at our daily stand ups.

I’ve been at this job 4 months and I feel like I’ve been here long enough to make an accurate opinion of it. From day one I have not felt welcomed. There is no communication within the team.. none of my questions are ever answered.. and when I do ask questions I get snarky answers. I don’t expect my hand to be held, but as someone who is new, I’d like you to give me guidance. Especially since the code is mostly legacy and no one else on the team seems to know anything about anything.

Oh and there are not daily stand ups, project managers, or direction in the tickets themselves.

I guess I should have expected this on the first day when I asked for a SIP or documentation on how to get my environment setup I was practically laughed out of the office and then had the nerve to ask me why it took me the entire day to get 5 environments up and running.. not giving me the custom mappings or the global UDFs.

Today was my last straw.. when I asked a question in three different forms of communication on multiple different channels and was never given an answer.. and then was asked why I did something the way I did instead of doing it the way they wanted me to.

I think the saddest thing is that I felt tricked into this. I was told this position was going to be one way but ended up being something else. I was excited to share my knowledge and best practices to the team. Instead, I’m an outcast and get only be negativity and excuses when I politely bring up suggestions.

I no longer have the will to code here.

Man, my product owner is so fucking annoying. I am 50/50 between two projects when really it feels like I'm 100/100 - and the PO of one of the projects always requests that I join daily stand ups and give updates.

CUNT.

I don't always have updates because I'm working with another team. Why are you trying to micromanage me you fuck face. Also, you know when you get those PO's that are totally useless and don't actually bring any real value to the project except in the capacity of being a slimey charismatic weasel? Yah, that's this person.

So I walk up to my desk, join the zoom meeting for daily stand ups, and then join the other meeting scheduled by the CEO. And I watched a presentation built around how I'll be fired in the next few minutes. My colleagues and I got laid off in the snap of a finger.
Sad much

Hello DevRant community! It’s been a while, almost 5 years to be exact. The last time I posted here, I was a newbie, grappling with the challenges of a new job in a completely new country. Oh, how time flies!

Fast forward to today, and it’s been quite the journey. The codebase that once seemed like an indecipherable maze is now my playground. The bugs that used to keep me up at night are now my morning coffee puzzles. And the team, oh the team! We’ve moved from awkward nods to inside jokes and shared victories.

But let’s talk about the real hero here - the coffee machine. The unsung hero that has fueled late-night coding sessions and early morning stand-ups. It’s seen more heated debates than the PR comments section. If only it could talk, it would probably write its own rant about the indecisiveness of developers choosing between cappuccino and latte.

And then there are the unforgettable ‘learning opportunities’ - moments like accidentally shutting down the production server or dropping the customer database. Yes, they were panic-inducing crises of apocalyptic proportions at that time, but in hindsight, they were valuable lessons. Lessons about the importance of thorough testing, proper version control, reliable backup systems, and most importantly, owning up to our mistakes.

So here’s to the victories and failures, the bugs and fixes, the refactorings and 'wontfix’s. Here’s to the incredible journey of growth and learning. And most importantly, here’s to this amazing community that’s always been there with advice, sympathy, humor, and support.

Can’t wait to see what the next 5 years bring! 🥂

"Oh, we do our daily stand-ups on Friday's at 3PM for half an hour or so"

:/

Before 2012, I always worked in cubicles and had weekly status meetings. In 2012 I moved to a big city and learnt there was something worse than cubes: the open work plan. Marketed as a way to increase coloration, the open work space is really just the result of real estate prices being expensive in cities and how desks are cheaper than 3-cube walls.

Up until 2013, we'd usually just have the weekly status meeting. Here are your tasks for the week. I'd do them at my own pace. Some days fast, some days slow, but they'd all get done by the end of the week and I'd proudly go down my list of stuff I had done.

Since then, it's all been "agile" and "stand-ups" every. fucking. day. The work is endless. A Product Owner once told me that stand ups weren't suppose to be status meetings; that you were only suppose to say if you're blocked or need help. But in every place I've worked at, they're daily status reports. You have to preform every day.

I really hate IT today more than ever. I miss the cube. I miss the weekly status reports. Today things are so high stress and higher paced and the work is endless. You can't even really pace yourself anymore.

If you have daily stand ups, don't let participants choose who speaks - we seem to spend 5 minutes of the 15 with people saying "no you go first".

I think I just gave my teammates/boss another mind-blowing idea...
Daily stand-ups are usually done standing up... Which means away from computers... And therefore JIRAs should not be mentioned, at least not by ID...

WHO THE FUCK CAN REMEMBER THEIR ISSUE IDS ALONG WITH EVERYONE ELSE'S...

This is long rant/story:

My manager conducts sync-up meetings regularly. The idea is to sync up all developers on current state of work. He does’t conduct stand-ups. He doesn't have time for it. He rather discusses on individual basis if we are blocked. The rule of the sync-up meeting is NOT to discuss any blockers or problems but simply explain each other what we are doing and how we plan next.

Sometime ago, the manager brought up and explained a new way of working in the sync-up meeting. At this point, a new developer in the team was absent due to sickness.

Today, there was a sync-up meeting and the manager started to question the new member about the newly introduced way of working. He was unaware of it and the manager never communicated this important information via email or any mode of communication available.

So, the conversation goes on as follows:

"Manager": — "Why didn’t you complete your task as per the new way of working?"
"Employee": — "Well, I've no idea. Am I supposed to do? I’ve been working as usual like any other"

"Manager": — "We have a new process and you have failed to follow it, so we’re late in delivering your work"
"Employee": — "I’ve already finished my work on time. I've raised a pull-request this morning"

"Manager": — "It doesn’t matter, it is not merged to main branch and so we can’t include your work in the release"
"Employee": — "I’ve no idea about the new process"

"Manager": — "Haven’t you asked around about what happened from previous meeting"
"Employee": — "Yes, I have. I was told which tasks were handled, but nothing about a new process"

"Manager": — "Aren’t you interested to learn it?"
"Employee": — "Why won’t I be interested? I was on a sick leave and I have no clue what happened here"

"Manager": — "What’s happened is past now, let’s not focus on it"
"Employee": — <Dumbfounded>
The Employee felt ashamed in front of everyone. He did his job but it didn’t pay off.

…. After an hour … the Employee had a talk with the Manager

"Employee": — "You shouldn’t have pointed me out in front of everyone. It made me feel real bad. You should have emailed this information if its important for the team."
"Manager": — "I have no idea what you’re talking about. When did I say so? I think you’ve a bright future in the team. You should be focusing on doing better things."

Employee goes back to work. A minute later, the Manager sends a PowerPoint screenshot of the process in the group chat.

**The Process**
It's about delivering release packages based on priorities defined by client. Each release package is a set of work items or requirements. Individual developers are assigned to work items. They are expected to deliver on planned delivery timelines in order to consider a work item into a release package.

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.

I don't like many sudden unplanned meetings appearing during your estimated development hours. It consumes some development time and destroys your momentum.

We follow the 2 weeks sprint that contains sprint ceremonies like sprint planning, demo, retro, daily stand ups and backlog grooming meetings. My capacity should be less then 80 hours since there are sprint ceremonies and unplanned meetings that happen during development hours. Unfortunately, my capacity is still set to 80 hours and meetings hours are not deducted. This puts me to a disadvantage as I need to do unpaid OT/weekend work just to make up for the lost time consumed by meetings.

Those 1 hour/30 minutes meeting piles up thus consuming development work hours. So a simple example is that you have 32 hours estimated to finish a big user story but sudden unplanned meetings and sprint ceremony meetings will consume some of that 32 hours. I will bring this up in our next retrospective meeting.

Got a new team and teammember who has been here for years seemed not so happy having me now as lead. No problem, i even can understand him a bit. Still, if you have a f***** problem there are better times to address them then every f***** time at stand-ups. -.-

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?

Every thought of using developer-related stuff in your home? When I get married I plan to have a private family slack workspace and Trello board and everyone gives stand-ups.

never before have I been happy to be asked to work overtime, but for once, fuck yeah...

Bit of back story, I am tech lead on a massive project that has been run like a complete shit show, the PM who also happens to be the brains behind the project seems to think we are miracle workers and for the first 9/10 months of the project would make significant, like delete a weeks worth of code and start over changes, 3-5 times per week. There are features for the v1 release that have been built in excess of 5 times. I have been saying since October that even without all his constant changes, we will NOT make the deadline, and naturally as is part of my job I argued against every unnecessary feature he tried to implement, eventually he pulled me into a meeting to tell me how much he values my opinion, I need to stop arguing with him and he does not want to work with yes men (I have a rant about that convo already).

I believe our CEO finally started smelling a rat as he insisted on joining our daily stand-ups, during which said PM scripted some lovely stories to disguise the fuckup we are in, and since has assigned another PM to take over and do proper project management and risk analysis.

That is where the email comes in, a lot of the work assigned to me will miss the deadline by a month, honestly I am impressed that it is by so little and so few people will not be missing it, but anyway, he probably spun a few stories there too.

So I spent part of the work compiling the most perfect surgical response as not not actively throw him under the bu, but create a quite a few questions that they hopefully as, as himself and the CEO where cc'd into the mail.

And the jist is, the deadline itself was still impossible and 8 of the 10 tasks assigned to be have ZERO back-end whatsoever, and those tasks are about 80/90% integration to said non-existent back-end, some of those services and data structures have not even been planned yet and we are a week past the deadline and 3 weeks from the just as useless extension.

Moved from A 10-day sprint to a 10-hour sprint.

Thank god we don't have hourly stand-ups.

lol @ doing stand-ups for the sake of stand-ups. I used to work for a company that vigorously applied them. Bro, I don't care about your development progress. You're wasting my time with your bla bla. Bunch of people just standing there rattling out their daily progress.. but no one really caring. Not useful.

lol..

Daily stand-ups might seem like a joke when done remotely, but I believe they help unite the team, and they play a key role for project managers, even if they're brief. The bigger issue might be just some of the dev's attitude towards it, and the lack of communication through out the project development.

When you come back from work after filling up jira, talking with colleagues during too long stand ups and writing documentation it's time to finally sit down and write some pure code.

I hate unnecessary meetings. It is a waste of my productive time. Also I hate daily stand ups that becomes a regular meeting with question and answer portion lol

It is like they are lazy creating a separate meeting for specific concerns and just brings it up in the daily stand ups lol nice way of doing agile things lol

> client has no infrastructure of the project
> dev like me still work on it
> I constantly request for mock-ups and infrastructure
> client never responds back, instead he raises issues ahead of sprint
> I snap back at him
> Client wants call now
> What the fuck

To be honest, I'm gonna take a stand here...fuck this shit man, no clear way of working

Damn those 30+ mins long stand ups. A standup shouldn't last more than 10 mins. Discuss your detailed analysis of the project outside of the standup. 😤

I'm so, so tired of stand-ups. We have JIRA, and basically all we do is read the board—ticket number, ETA, blockers. We've done some Slack stand-ups, but my managers insist we all be in the room to communicate the same shit we communicate very effectively on Slack.

Colleagues of mine merge try/except:pass without my consent also I strongly argue over the fact that exceptions in python should never be passed silently. I feel my poor technical knowledge to be denied or ignored and it feels painful.

I don't even have the gutts to speak about it loudly - during stand ups - because I am afraid to get on my nerve that ppl don't listen to me plus quickly merge such awfuls snippets without listening to me.

I feel like I am struggling. What should I do?

I am so fucking sick of daily stand ups. What a fucking waste of my time, even if it’s only 15 minutes, it fucks up my workflow and is just generally fucking annoying

PM, we are going to go to an agile methodology for working. (despite PM having never done agile, and most of the team having never done agile) But we will have 4 week sprints, as 2 week sprints are too short. We are going to have daily stand ups, oh but we'll only have then once a week... And we will keep the 3 hour mid week meeting. Oh and we'll keep our existing JIRA, but you also need to use *new* JIRA as well, but that's going to the customer so don't post bugs on it.... (all with a ln important delivery in a few months) The suggestion of getting an adviser (either internal or external) who has experience with agile to help us transition smoothly and provide best practice got shot down. feels like the blind leading the blind...

I’m currently working 2 jobs with over 60 hour work weeks in addition to my own SaaS company.

One job is full-time 40 hours, where I am a mid level developer and I just do the waterfall of tickets that is assigned to me. This place is unorganized and has almost no communication within the team.

The second job I am the Senior Dev and project lead. It’s a contract position that I put 20+ hours in on the evenings and weekends. Agile methodology, with a modern tech stack and I promote excellent communication as well as documenting everything.

I’m in a unique position because I’m able to see these differences and compare them side by side. My full-time job doesn’t really know about the second job. I get my work done, and that’s all that matters. This place is a mess. The project lead (CTO) is a helicopter boss that sticks his nose up at any type of formal documentation and practices. No tests are written.. no SIPs or deployment docs.. no stand ups or anything. I must also mention this team has 5 developers and a QA.. my team is only 2 developers and a QA. We get through tickets much faster.. it helps when I go over every single ticket that is created and add requirements and images..

I guess my point is... I’m about to be a full-time contractor because I can’t take this unprofessionalism anymore.

Just because these formalities technical take longer. It does decrease actual time spent developing a project. Spending a couple of hours on tests and requirements can save you days of back and forth in the future. Not to mention... document.. everything.

"Dear TitanLannister : You are in the final year. A lot of shit is happening around u. its now time to make a career and take tough decisions. What would you do?"

CHOICE 1: COMPETITIVE
>>>>background : "a lot of super companies like wallmart, fb, amazon, ms, google,.. etc simply takes a straight coding test for fresher placement. They ask tough bad ass level questions, but with right guidance, a hell ton of dedicated hours of coding, and making it to the top of various coding tests could make you a potential candidate"
>>>>+ve points :
- "You got the teachers and professionals with great experience to guide you"
- "a dream job come true.you can go there and join teams that interests you"
- "it was your first exposure to computer world. maybe you would like doing it again, after 4 years"
>>>> -ve points:
- "You have always been an average 70 percentile guy. The task requires 2000-3000 hours of coding an year. it will be hard and you always grow bored out of this pretty quickly"
- "Even If you did that , you stand a lesser chance because your maths is shitty.There are millions running in this race with brains faster than your IDE"
- "your college will riot with you because they expect 75% attendance"
- "You are virtually out of college placements, in which , even though shitty companies come and offer even shittier 4LPA packages($6000 per annum), would take a tough logical/aptitude based test for which you won't be able to prepare"

CHOICE 2: PROFESSIONAL WORK
>>>>background: "you always wanted to create something , and therefore you started taking android based courses. you have been doing android for over 2 years and today you know a lot of things in android. you might be good in other professional lines like web dev, data analytics, ml,ai, etc too if you give time to that"
>>>>+ve points :
- "you will love doing this, you always did"
- "With the support of a good team, you will always be able to complete tasks and build new things quickly"
- "Start ups might offer you the placement, they always need students with some good exposure"
>>>>-ve points :
- "Every established company which provides interesting dev work takes their first round as coding, and do not considers your extra curricular dev work. So you are placing your all hopes in 1 good start up with super offerings that would somehow be amazed by your average profile and offer you a position"
- "start ups are well, startups and may not offer a job security as strong as est. companies"
- "You are probably not as awesome dev as you think you are. for 2 years, you have only learned the concepts , and not launched more than 1 shitty app and a few open source work"

CHOICE 3: NON CODING
>>>>background: "companies coming in college placements have 1-2 rounds of aptitude,logical reasoning , analysis based questions and other non tech tests. There are also online tests available like elitmus,AMCAT, etc which, when cleared with good marks help receive placements from decent established companies like TCS, infosys, accenture,etc"
>>>>+ve points :
- "you will eventually get placed from college, or online tests"
- "there will be a job security, as most of these companies bonds the person for 2-3 years"
>>>> -ve points:
- "You really don't like this. These companies are low profile consultant/services based companies which would put you in any area: from testing to sales, and job offers are again $5000-6000 per annum at max"
- "Since it includes college, the other factors like your average cgpa and 1 backlog will play an opposing role"
- "Again, you are a 70 percentile avg guy. who knows you might not able to crack even these simple tests"

Ugh... I am fucking confused. Please be me, and help.The things that i wrote about myself are true, but the things that i assumed about super companies, start ups or low profile companies might not be correct, these points comes from my limited knowledge ,terrified and confused brain, after all.
:(

Was gonna talk to my PM today about stand ups going long, but then standup lasted right through our scheduled meeting. Feels cyclical.

DevRant makes our bloated stand-ups way more bearable hehe

Stand ups , why , I could easily just ask the guy next to me what changed in the last 7 of sleep In which I didn't see him, but nooo mister CEO must have it his way

Stand-ups where I find myself waiting for my colleagues to go on the Zoom call.

Let me share my sprint with you.

So, we lost a developer this at the start of the sprint because the organisation we work for is total cancer.

Project manager frequently says to us that it's better to under commit than over commit.

Come sprint planning, we commit to exactly what we know we can achieve.

Of course, the PM whinges and says we need to put more in the sprint. So, we say sure, but we can't guarantee we will deliver everything on time.

Fast forward 2 weeks, we complete 90% of what we committed to.

PM is whinging at stand ups, asking us why some user stories are still in 'ready for test'.

We try to explain to the PM that 2 weeks ago we made ourselves very clear that this point 2 weeks later would most likely happen.

PM stops whining.

Tester starts whinging about only having a couple of days to test. Blames developers for not adhering to acceptance criteria.

>User stories aren't actually user stories, they're user essays.

How do you deal with this?

How long are your daily stand-ups with ur team (what size is ut team?)

And when do you have them? First thing in the morning or later in the day?