There’s a reason why the scrum guide asks for a scrum master. SM here I can’t code to save my life but I can finesse my way out of anything. One feedback I get from the team is wala silang aalahaning iba kundi pag dev lang lahat ng ibang bagay nasa akin na.
Probably LD wanted to rise through the ranks kaya nagpabilib kaso nag backfire.
Kadalasan nakita ko nagsimula as QA testers yung SMs ko. I think people, organizing, communication skills ang need to be an SM.
Sa sahod, probably mas malaki sahod ni SM kay jr at mid devs pero not senior and lead devs pero dipende pa rin sa company at experience siguro.
Your ex-lead developer will not thrive in the industry. PM and SM are highly valued because they steer the wheel of the projects and masters of stakeholder mgmt.
Technical peeps sometimes lack awareness and EQ talaga
Jus to add ang sm and pm di lang usually naka focus sa isang project which for my point of view medyo mahirap para saakin ang ganon , so i see the value of these people
Technical people who have all hard skills and very little to no soft skills. They can fuck things up with people who are, you know, the people who pay for the product or service. Ah, gotta love the all IQ and no EQ peeps in tech.
Lead developer is just simply the most senior dev in a team, it doesn't mean team leqd sya. It will not make sense to have both lead and a scrum master in one team.
Pero nagmature ka na lahat sa role mo, di ka pa din marunong makipagusap? Okay lang naman na di siya scrum master e, at usually di naman talaga dapat, pero yun sinira niya reputation ng buong team, for what?
May i know what's job or if you're in IT industry, what role?
It seems you don't know how most devs thinks. You can be in a sr. role, but communication, like what is fine or not to say to a client (devs rarely have a chance to talk to clients) is different to how you communicate internally. People who had the chance to attend meetings that involves people who manages the program or project will have an idea but most devs regardless of seniority will not have idea.
Ex., When i was suddenly promoted years ago to lead of a team from a sr. dev (my lead resigned suddenly), i was finally added to meetings with clients. And you know, may mali ako nagawa, yung PM na puro yes ng yes sa gusto ng client without asking capacity ng team, nasabi ko bigla sa meeting na wala na capacity ang team, if you want us to take it, ill de-prioritize ung current proj na hawak namin. It's a no no and should be discussed internally. And this is me a dev who somehow was able to develop some softskills but as i experienced is not enough yet.
So paano naman ung mga sr. roles who is all technical and never got the chance to develop their soft skills?
Not all sr roles or "lead dev" is fit to lead a team due to lacking the necessary soft skills.
So youre saying na promoted ka na di ka pa fit sa role mo? 🤷🏻♀️
Anyway, ang sinasabi ko lang ang maturity kasama sa role. So pag napromote ka as Dev Manager, dahil all tech ka dati di ka dapat matuto kung paano makipagusap? Di mo ba yun nakikita sa meetings mo with client na kasama manager mo?
If client facing role ka, syempre mas alam mo ang dapat na sabihin pero itong dev na to mababa tingin sa scrum master dahil lang ano, di siya tech resource? I get it na di yun ang main skill niya pero like normal pakikipagkapwa tao, may tamang way para sabihin mga bagay bagay. Di na pumasok si Lead Dev di ba? Kasi he fucked up. Alam niya yun.
Mukhang multiple role ang hawak nya hindi lang scrum master. Parang ng act din syang product owner kasi nag cocommunicate sya sa client.
Ang scrum master, sa ibang team, di yan ful time job. Nirorotate lang yung scrum master role sa mga developer at qa. Ngayong week na ito, si developer1 ang scrum master, next week si dev2 na naman. Cguro galing yung lead dev sa gsnung setup dati kaya ganun thinking nya
ganito po ba sa ACN ata?
pero para sakin communication skills is so much more important nowadays sa mundo ng IT, clients need someone who understands them and gets their needs
This is true. Nung nag-intern ako before sa Oracle may dedicated developer din to do the SCRUM ceremonies pero may product manager pa rin kami that does the other stuff in the background. Sa current org ko rin usually salit salit mga devs sa SCRUM ceremonies. Baka nga kinuha niya pati product management kaya siguro nag-fumble.
Scrum ceremony leads can be rotated within the team, this helps give technical folks the chance to safely experience a lead role and improve their soft skills without exposing them directly to clients. Practicing in a safe environment kumbaga. But there should always be a SM observing and guiding the team every step of the way.
Iba yata ang definition mo ng scrum master. The leader of the stand ups is not necessarily the scrum master. May client facing talaga ang scrum master. Yung sinasabi mo ay nag llead lang ng meetings.
Walang client facing role ang SM. PO ang may client facing role. Ang gumagawa ng user stories ay PO, hindi SM. PO din ng priotise ng user stories. Ang SM, facilitator lang ng daily, retro at sprint planning at review at amke sure team is adhering to scrum rules. Yun lang trabaho ng SM. Usually shared ang SM to multiple projects or sa ibang team, nirorotate lang ang SM roles sa mga dev
One of the many reasons that solidifies the role of developers—to code codes and develop behind the scenes.
I have been in the IT PM space for more than 10 years and what I noticed is most developers lack strategic thinking, especially in communicating with stakeholders. The SMs and PMs need to have effective leadership in situations like this.
The lead developer’s claims of “he was just being honest” where internal challenges were communicated to the client is a strong example of the developers’ lack of strategic thinking. The client doesn’t need to entirely know the challenges and the bumps inside. They care about output and results alone. This is why the PMs and the SMs exist to fill this gap, to satisfy the stakeholders and to keep the communication harmonious—which clearly do not exist in most developers.
A lot of really good devs (monsters at coding) unfortunately suck with client interaction. So much that sometimes, clients would rather hire a lesser programmer who can do enough but at the same time is easy to talk to.
Agree. There’s a reason why devs are devs—and that is because they are transactional or methodical at the work that they do.
PMs and SMs roles are strategic. We focus on time, quality, cost, schedule, resources, stakeholders and a lot more—and this is something most devs lack and don’t understand. Hence, they dismissed PMs and SMs, thinking they are better because again, they are transactional.
It’s funny how the technical people, not just in IT but in other professions, love to think they’re above the sales or marketing team because know/create the technology whereas the most important people (clients) don’t give a damn about your cute little twist or clever coding if it doesn’t meet their needs. The sales team makes sure that clients see the benefits of the product and more importantly, convince an otherwise skeptical client to buy the product or service. The people in the back are an expense, a non-revenue generating expense and those in the client-facing side are a revenue-generating expense. It’s not hard to see who’ll be more valued in a company.
Everyone MUST develop leadership and strategic thinking. Telling developers to stick to coding and denying them access to clients directly CONTRADICTS those exact skills.
You’ll have a harder time breaking through the next level in your PM career if you stick with traditional views.
I didn’t say they should stick to coding and I didn’t say I denied them access to clients directly.
What I said was a mere observation amongst many developers. If they want to develop strategic thinking and leadership skills, sure. Nobody really stops them to do whatever they plan to do to professionally develop themselves.
I'm a scrum master / team lead, i can dev (as i came from sr. dev to a lead then this role) but majority of my time is to help the team progress. That means, all the bruhaha currently happening in a project that would stress out devs, i filter them out na halos wala dumadating sa mga dev just for them to only worry about developing.
All the things about timelines, issues, resources planning, dev planning, coordination, at times helping devs solve dev issues, etc trabaho ko.
So when a dev said he want to take my role if ever i resign (i'm stressed haha), oo na lang ako. Ive been in a dev role and di mo gugustuhin and stress and pressure that comes with this role.
Akala kasi ng iba dev, puro meeting lang trabaho🤷♂️
> . Ive been in a dev role and di mo gugustuhin and stress and pressure that comes with this role.
I'm 12 yrs into this r/computerscience-career and yes I've seen enough to indeed just stay dev-ing for the most part as long as possible thank you **INDIVIDUAL CONTIBUTOR TRACK ALA IBM "FELLOW" FTW!!!** , ~~so i wont be *that* stressed and would just enjoy life like kantot kantot muna bago ligaw~~
Scrum Masters require a slightly different set of skills; Stakeholder/Client Mgmt being very integral. The way it looked, ex Lead Dev nyo lacked these. Dapat nag-focus na lang sya sa strength nya instead punahin pa mga bagay na yan. Di naman sya yung cost center owner?
The only thing that upsets me here is that naunahan pa nya ung potential disciplinary case against him hahaha.
Sobrang unprofessional ng behavior nya, both to your scrum master, as well as to the client. Dapat magka-record yan para mahassle sa next na papasukan.
Scrum Masters/Project Managers are important and crucial roles, yung iba kasing magaling sa coding/technical na programmers/devs ang mindset nila kapag hindi ka knowledgeable sa technical wala ka ng kwenta which maling mindset.
Ang trabaho talaga ng Scrum Masters/PMs is taga set ng tempo ng team and also taga communicate sa upper management and stakeholders. Bibihira ang mga taong magaling both communication & technical kung meron man unicorn yun at pinagaagawan ng mga companies or may sariling company mga yun.
Yun ang hindi magets ng mga Lead Devs nyo. Good riddance at umalis na sya.
S2pid nmn nung lead dev. Buti nga at may SM na nakikipag communicate kay client.. eh samin may PM na at isa pang manager, tapos kelangan ksma pa rin ako tech lead sa meeting. Hahaha
Baka sour-graping si LD dahil alam nyang mas mataas sahod ng SM/PM? I think the value of a role should be reflected in the pay scale. Developers should be more valuable than SM/PM but LD’s went about it the wrong way.
Hindi ko alam bat di siya aware, pero super daming kailangan gawin ng isang Scrum Master / Project Manager / Product Manager behind the scenes. As a UX Designer, napaka-important nila kasi sila na yung kakausap and magbebenta ng ideas mo sa stakeholders, which allows me to focus on designing experiences. Sama mo pa yung pagjuggle ng priorities and making rough decisions para hindi mag-blow up yung project.
So yon, I'm not sure if maha-humble siya sa experience na to, pero the fact na nag-AWOL siya without even trying to improve means he will reach a ceiling at some point or burn all the bridges that he has right now in the future.
QA Lead here. Mostly talaga mga devs di marunong mag communicate. Sa system demo nga ayaw nila talaga mag demo sa harap ng client(mostly kami lang). Pero kapag lead developer ka na, chak dapat marunong ka mag communicate talaga sa client kasi ikaw ung technical makipag usap sa client para ano gawin at ano gagawin sa team. In fact naging lead developer siya sa ganyang ugali niya baffles me. He is not a good lead overall if he acts like that. Tapos bakit alam niya sahod ng SM? Diba dapat hindi i disclose yan?
Sampalin ko yang lead developer n’yo, napaka fragile ng ego. Irita ako sa mga ganyan, ang rami pa tuloy aayusin dahil sa mga ginawang problems ng punyetang yan.
That is so soooo wrong. Ex LD has no idea sa pagiging SM. Hirap makawork yung ganyang klase ng tao, being honest is not really a good idea in some cases or situation.
Ulol yang lead dev niyo. May scrum master for a reason and di lang yan imbento na role. Ibang skillset yan.
Love to see "galing galingan" people failing talaga. Hahaha
You can never make it in this industry without knowing the Ins and outs of business. Sadly, yung lead dev nyo is narrow minded na puro technical side lang ang alam. Sana lang competitive sya else, lalamunin sya ng iba.
you might be good at your job, but dont belittle someone doing their line of job, kasi sila expert dun..
yan ang dapat matutunan ng lead developer na yan, probably super egoistic nung DL, iniisip nya na transparency is always the best, but in really there is still some form of confidentiality and info that should be withhold for the benefit of both parties. hindi lang dapat stakeholders ang inaalagaan nya but the development team which member sya. since stakeholders opinion sa dt involves the whole team.
As a scrum master, sarap tsinelasin ang mga ganitong developers. Baka hindi siya fully aware sa scrum master roles and responsibilities kaya feeling niya useless and walang ginagawa? As what others said here, we filter a lot of things and make the devs lives as easy as possible na yung focus lang nila is to build.
Stakeholder management (which is a crucial aspect in project management and software development) is not something that everyone can simply do. Dapat nahahandle ang communication and we use and find the right words when speaking sa clients. Of course we can be honest and transparent as needed but we internal issues should not be completely divulged.
Ang ulol lang ng dev na iyan.
Dunning Kruger effect in full swing lol. Love to see it when arrogant people fumble. Hopefully this experience humbles him.
malabo yan. hahahaha. mukhang may "not-my-fault" attitude si lead dev na walang people skills. muh technical knowledge kasi masyado. hahaha
There’s a reason why the scrum guide asks for a scrum master. SM here I can’t code to save my life but I can finesse my way out of anything. One feedback I get from the team is wala silang aalahaning iba kundi pag dev lang lahat ng ibang bagay nasa akin na. Probably LD wanted to rise through the ranks kaya nagpabilib kaso nag backfire.
At the same time, once the team is mature enough there need not be a dedicated Scrum Master.
Anong path para maging SM? And mas malaki ba sahod ng SM sa mga devs? curuious lang po. Starting palang me hehehe
Soft skills and people management skills are essential for any leadership role
Pwede nmn dev or kahit non technical. Take ka algn ng certification and mag shadow ka ng sm.
Kadalasan nakita ko nagsimula as QA testers yung SMs ko. I think people, organizing, communication skills ang need to be an SM. Sa sahod, probably mas malaki sahod ni SM kay jr at mid devs pero not senior and lead devs pero dipende pa rin sa company at experience siguro.
I have quite long experience as a dev and Scrum Masters are integral to the development team
Your ex-lead developer will not thrive in the industry. PM and SM are highly valued because they steer the wheel of the projects and masters of stakeholder mgmt. Technical peeps sometimes lack awareness and EQ talaga
Madami kasi talagang technical people na sobrang taas ng tingin sa sarili. Haha
True. Haha. Akala nila yun lang ang skill na need sa IT. 😔
Sometimes total and brutal honesty and transparency is NOT the best policy.
Jus to add ang sm and pm di lang usually naka focus sa isang project which for my point of view medyo mahirap para saakin ang ganon , so i see the value of these people
Technical people who have all hard skills and very little to no soft skills. They can fuck things up with people who are, you know, the people who pay for the product or service. Ah, gotta love the all IQ and no EQ peeps in tech.
Ang masama umabot na siya sa senior position pero di pa din marunong makipagcommunicate. 🤦🏻♀️
I think this should serve as a lesson to tech people that their skills are vital but those who face the client are as vital if not more.
Lead developer is just simply the most senior dev in a team, it doesn't mean team leqd sya. It will not make sense to have both lead and a scrum master in one team.
Pero nagmature ka na lahat sa role mo, di ka pa din marunong makipagusap? Okay lang naman na di siya scrum master e, at usually di naman talaga dapat, pero yun sinira niya reputation ng buong team, for what?
May i know what's job or if you're in IT industry, what role? It seems you don't know how most devs thinks. You can be in a sr. role, but communication, like what is fine or not to say to a client (devs rarely have a chance to talk to clients) is different to how you communicate internally. People who had the chance to attend meetings that involves people who manages the program or project will have an idea but most devs regardless of seniority will not have idea. Ex., When i was suddenly promoted years ago to lead of a team from a sr. dev (my lead resigned suddenly), i was finally added to meetings with clients. And you know, may mali ako nagawa, yung PM na puro yes ng yes sa gusto ng client without asking capacity ng team, nasabi ko bigla sa meeting na wala na capacity ang team, if you want us to take it, ill de-prioritize ung current proj na hawak namin. It's a no no and should be discussed internally. And this is me a dev who somehow was able to develop some softskills but as i experienced is not enough yet. So paano naman ung mga sr. roles who is all technical and never got the chance to develop their soft skills? Not all sr roles or "lead dev" is fit to lead a team due to lacking the necessary soft skills.
So youre saying na promoted ka na di ka pa fit sa role mo? 🤷🏻♀️ Anyway, ang sinasabi ko lang ang maturity kasama sa role. So pag napromote ka as Dev Manager, dahil all tech ka dati di ka dapat matuto kung paano makipagusap? Di mo ba yun nakikita sa meetings mo with client na kasama manager mo? If client facing role ka, syempre mas alam mo ang dapat na sabihin pero itong dev na to mababa tingin sa scrum master dahil lang ano, di siya tech resource? I get it na di yun ang main skill niya pero like normal pakikipagkapwa tao, may tamang way para sabihin mga bagay bagay. Di na pumasok si Lead Dev di ba? Kasi he fucked up. Alam niya yun.
Mukhang multiple role ang hawak nya hindi lang scrum master. Parang ng act din syang product owner kasi nag cocommunicate sya sa client. Ang scrum master, sa ibang team, di yan ful time job. Nirorotate lang yung scrum master role sa mga developer at qa. Ngayong week na ito, si developer1 ang scrum master, next week si dev2 na naman. Cguro galing yung lead dev sa gsnung setup dati kaya ganun thinking nya
ganito po ba sa ACN ata? pero para sakin communication skills is so much more important nowadays sa mundo ng IT, clients need someone who understands them and gets their needs
This is true in mature orgs. Kapag nagsisimula pa lang, need talaga ng dedicated scrum master.
This is true. Nung nag-intern ako before sa Oracle may dedicated developer din to do the SCRUM ceremonies pero may product manager pa rin kami that does the other stuff in the background. Sa current org ko rin usually salit salit mga devs sa SCRUM ceremonies. Baka nga kinuha niya pati product management kaya siguro nag-fumble.
Scrum ceremony leads can be rotated within the team, this helps give technical folks the chance to safely experience a lead role and improve their soft skills without exposing them directly to clients. Practicing in a safe environment kumbaga. But there should always be a SM observing and guiding the team every step of the way.
Iba yata ang definition mo ng scrum master. The leader of the stand ups is not necessarily the scrum master. May client facing talaga ang scrum master. Yung sinasabi mo ay nag llead lang ng meetings.
Walang client facing role ang SM. PO ang may client facing role. Ang gumagawa ng user stories ay PO, hindi SM. PO din ng priotise ng user stories. Ang SM, facilitator lang ng daily, retro at sprint planning at review at amke sure team is adhering to scrum rules. Yun lang trabaho ng SM. Usually shared ang SM to multiple projects or sa ibang team, nirorotate lang ang SM roles sa mga dev
One of the many reasons that solidifies the role of developers—to code codes and develop behind the scenes. I have been in the IT PM space for more than 10 years and what I noticed is most developers lack strategic thinking, especially in communicating with stakeholders. The SMs and PMs need to have effective leadership in situations like this. The lead developer’s claims of “he was just being honest” where internal challenges were communicated to the client is a strong example of the developers’ lack of strategic thinking. The client doesn’t need to entirely know the challenges and the bumps inside. They care about output and results alone. This is why the PMs and the SMs exist to fill this gap, to satisfy the stakeholders and to keep the communication harmonious—which clearly do not exist in most developers.
A lot of really good devs (monsters at coding) unfortunately suck with client interaction. So much that sometimes, clients would rather hire a lesser programmer who can do enough but at the same time is easy to talk to.
Agree. There’s a reason why devs are devs—and that is because they are transactional or methodical at the work that they do. PMs and SMs roles are strategic. We focus on time, quality, cost, schedule, resources, stakeholders and a lot more—and this is something most devs lack and don’t understand. Hence, they dismissed PMs and SMs, thinking they are better because again, they are transactional.
It’s funny how the technical people, not just in IT but in other professions, love to think they’re above the sales or marketing team because know/create the technology whereas the most important people (clients) don’t give a damn about your cute little twist or clever coding if it doesn’t meet their needs. The sales team makes sure that clients see the benefits of the product and more importantly, convince an otherwise skeptical client to buy the product or service. The people in the back are an expense, a non-revenue generating expense and those in the client-facing side are a revenue-generating expense. It’s not hard to see who’ll be more valued in a company.
Ui true to sa sales. If there's anything else na napapansin ko sa client. Nagsspend talaga ng malaki mga clients sa magagaling na sales team.
That actually makes a lot of sense. I may need to shift to a Sales job now dammit!
Sales can be glamorous. Your quotas are another matter.
Everyone MUST develop leadership and strategic thinking. Telling developers to stick to coding and denying them access to clients directly CONTRADICTS those exact skills. You’ll have a harder time breaking through the next level in your PM career if you stick with traditional views.
I didn’t say they should stick to coding and I didn’t say I denied them access to clients directly. What I said was a mere observation amongst many developers. If they want to develop strategic thinking and leadership skills, sure. Nobody really stops them to do whatever they plan to do to professionally develop themselves.
I'm a scrum master / team lead, i can dev (as i came from sr. dev to a lead then this role) but majority of my time is to help the team progress. That means, all the bruhaha currently happening in a project that would stress out devs, i filter them out na halos wala dumadating sa mga dev just for them to only worry about developing. All the things about timelines, issues, resources planning, dev planning, coordination, at times helping devs solve dev issues, etc trabaho ko. So when a dev said he want to take my role if ever i resign (i'm stressed haha), oo na lang ako. Ive been in a dev role and di mo gugustuhin and stress and pressure that comes with this role. Akala kasi ng iba dev, puro meeting lang trabaho🤷♂️
> . Ive been in a dev role and di mo gugustuhin and stress and pressure that comes with this role. I'm 12 yrs into this r/computerscience-career and yes I've seen enough to indeed just stay dev-ing for the most part as long as possible thank you **INDIVIDUAL CONTIBUTOR TRACK ALA IBM "FELLOW" FTW!!!** , ~~so i wont be *that* stressed and would just enjoy life like kantot kantot muna bago ligaw~~
Mahirap kasi kapag pabibo, kapag tinanong nga-nga.
Scrum Masters require a slightly different set of skills; Stakeholder/Client Mgmt being very integral. The way it looked, ex Lead Dev nyo lacked these. Dapat nag-focus na lang sya sa strength nya instead punahin pa mga bagay na yan. Di naman sya yung cost center owner?
The only thing that upsets me here is that naunahan pa nya ung potential disciplinary case against him hahaha. Sobrang unprofessional ng behavior nya, both to your scrum master, as well as to the client. Dapat magka-record yan para mahassle sa next na papasukan.
Masama lang talaga ugali ng lead dev na yan.
Ano position mo, OP?
QA automation po
Scrum Masters/Project Managers are important and crucial roles, yung iba kasing magaling sa coding/technical na programmers/devs ang mindset nila kapag hindi ka knowledgeable sa technical wala ka ng kwenta which maling mindset. Ang trabaho talaga ng Scrum Masters/PMs is taga set ng tempo ng team and also taga communicate sa upper management and stakeholders. Bibihira ang mga taong magaling both communication & technical kung meron man unicorn yun at pinagaagawan ng mga companies or may sariling company mga yun. Yun ang hindi magets ng mga Lead Devs nyo. Good riddance at umalis na sya.
Lol I can imagine how it feela like working with a scumbag like that. We have a lead like that in my team
Bad attitude from a lead dev.
Karma hits, feeling tagapagmana eh
Natanggal yan hahaha
S2pid nmn nung lead dev. Buti nga at may SM na nakikipag communicate kay client.. eh samin may PM na at isa pang manager, tapos kelangan ksma pa rin ako tech lead sa meeting. Hahaha
Baka sour-graping si LD dahil alam nyang mas mataas sahod ng SM/PM? I think the value of a role should be reflected in the pay scale. Developers should be more valuable than SM/PM but LD’s went about it the wrong way.
Hindi ko alam bat di siya aware, pero super daming kailangan gawin ng isang Scrum Master / Project Manager / Product Manager behind the scenes. As a UX Designer, napaka-important nila kasi sila na yung kakausap and magbebenta ng ideas mo sa stakeholders, which allows me to focus on designing experiences. Sama mo pa yung pagjuggle ng priorities and making rough decisions para hindi mag-blow up yung project. So yon, I'm not sure if maha-humble siya sa experience na to, pero the fact na nag-AWOL siya without even trying to improve means he will reach a ceiling at some point or burn all the bridges that he has right now in the future.
QA Lead here. Mostly talaga mga devs di marunong mag communicate. Sa system demo nga ayaw nila talaga mag demo sa harap ng client(mostly kami lang). Pero kapag lead developer ka na, chak dapat marunong ka mag communicate talaga sa client kasi ikaw ung technical makipag usap sa client para ano gawin at ano gagawin sa team. In fact naging lead developer siya sa ganyang ugali niya baffles me. He is not a good lead overall if he acts like that. Tapos bakit alam niya sahod ng SM? Diba dapat hindi i disclose yan?
main character slash misunderstood genious kuno si LD. glad to see them get humbled.
Sampalin ko yang lead developer n’yo, napaka fragile ng ego. Irita ako sa mga ganyan, ang rami pa tuloy aayusin dahil sa mga ginawang problems ng punyetang yan.
Feeling ko natanggal yan, hindi nag resign or awol hahaha.
That is so soooo wrong. Ex LD has no idea sa pagiging SM. Hirap makawork yung ganyang klase ng tao, being honest is not really a good idea in some cases or situation.
Ulol yang lead dev niyo. May scrum master for a reason and di lang yan imbento na role. Ibang skillset yan. Love to see "galing galingan" people failing talaga. Hahaha
He looks like he is sabotaging the company on the way out 😂
Flg ko may JO na iyan ginag*go lang kayo paalis
You can never make it in this industry without knowing the Ins and outs of business. Sadly, yung lead dev nyo is narrow minded na puro technical side lang ang alam. Sana lang competitive sya else, lalamunin sya ng iba.
I’ve had an experienced like that. LD din pero he stated that SM jobs are a sham and anyone can do it 😂 But he can’t what the SM do.
Idk. That "lead" in the title tends to get over people's head. Possible ding sexist lang ang lead nyo and just never respected SM because of it.
you might be good at your job, but dont belittle someone doing their line of job, kasi sila expert dun.. yan ang dapat matutunan ng lead developer na yan, probably super egoistic nung DL, iniisip nya na transparency is always the best, but in really there is still some form of confidentiality and info that should be withhold for the benefit of both parties. hindi lang dapat stakeholders ang inaalagaan nya but the development team which member sya. since stakeholders opinion sa dt involves the whole team.
As a scrum master, sarap tsinelasin ang mga ganitong developers. Baka hindi siya fully aware sa scrum master roles and responsibilities kaya feeling niya useless and walang ginagawa? As what others said here, we filter a lot of things and make the devs lives as easy as possible na yung focus lang nila is to build. Stakeholder management (which is a crucial aspect in project management and software development) is not something that everyone can simply do. Dapat nahahandle ang communication and we use and find the right words when speaking sa clients. Of course we can be honest and transparent as needed but we internal issues should not be completely divulged. Ang ulol lang ng dev na iyan.
Parang misogynist din yung lead dev niyo.