# data[].attributes.body
Do what you preach:

Model vulnerability yourself - When leaders admit mistakes, ask for help, or say "I don't know," it signals that imperfection is acceptable and even valued for learning.

Communication:

Respond to problems with curiosity, not blame - When someone raises an issue, lead with questions like "Help me understand what happened"

Address the "messenger shooting" immediately - If anyone responds negatively to someone raising a concern, intervene quickly and privately. One instance of punishing transparency can undo months of trust-building.

Ask better questions - Instead of "How's everything going?" try "What's one thing that's harder than it should be?" or "What are you worried about that we haven't discussed?"

Structure:

Create regular forums for concerns - Build structured ways for problems to emerge, like retrospectives, one-on-ones, or "failure parties" where teams discuss what's not working without judgment.

# data[].attributes.body
free to attend!

# data[].attributes.attachment_link.readable_text
Regus

8 Marina View, Asia Square Tower 1 S018960 · Singapore

Join us for an exclusive session where Ramesh shares how MyCareersFuture team successfully transitioned from Scrum to Kanban to better align with business goals.

In this meetup, you will learn:

The challenges and opportunities the team faced with Scrum and why Kanban became a better fit.

Key learnings from both Scrum and Kanban that can help teams work smarter.

How the shift enabled the team to streamline efforts and deliver meaningful value to business stakeholders and public.

Refreshment provided.
Security Clearance required at lobby please do come early for registration.

Members are also interested in

See all

# data[].attributes.attachment_link.title
Scrum to Kanban - Real Insights, Fri, Oct 10, 2025, 6:30 PM | Meetup

# data[].attributes.attachment_link.description
Join us for an exclusive session where Ramesh shares how MyCareersFuture team successfully transitioned from Scrum to Kanban to better align with business goals. In this m

# data[].attributes.headline
Could you share about your experience in bringing the scrum cadence back to the team?

# data[].attributes.subject
Could you share about your experience in bringing the scrum cadence back to the team?

# data[].attributes.body
What are your thoughts on having shared team members, such as developers working across multiple squads or those who need to support BAU activities?

Note that management or company is not able to afford dedicated resources.

How does this impact a Scrum team's effectiveness and what are some strategies to mitigate the challenges?

# data[].attributes.headline
How to deal with bug fixing and meeting sprint goals?

# data[].attributes.subject
How to deal with bug fixing and meeting sprint goals?

# data[].attributes.body
As mentioned, time and efforts are needed for bug investigation and fixing, how do we deal with such scenario when we have sprint goals to meet and resources are tight?

# data[].attributes.body
What's the best practice with capturing QA's tasks as part of sprint backlog?

# data[].attributes.headline
Addressing the issue on surface, probably not the root cause or objective intended

# data[].attributes.subject
Addressing the issue on surface, probably not the root cause or objective intended

# data[].attributes.body
If there is a change of direction, requirements or unclear goals. HR/ Management brought in scrum trainer to help team for the new change of directions. Will this be helpful if there is no legit consultant and propose the rightful way from top-down approach? Eg: Business analysis and management decision making require.

# data[].attributes.body
from Fibonacci sequence , u mentioned after 8 , 13 is 20.

Based on golden ratio constant of 1.618 should be 21, can u provide insights why u mentioned it should be 20 from product mgt / scrum standpoint ?

# data[].attributes.body
https://www.atlassian.com/agile/project-management/user-stories

# data[].attributes.body
1. Read through the ticket for comments written by assignee, who may have indicated the reason(s) of blockage.

2. If there are dependencies that cannot be resolved within the sprint, may consider removing the item from current sprint.

3. If things are unclear, assignee and reporter to work together to state the actions/steps needed to unblock the item.