JIRA doubt...

[dasari4kntr]

mee company lo...how is jira work flow..?

whose responsibility to creates epics/stories...and who responsibility to close it..?

 

memu follow ayye dantlo chinna flaw vundi...just trying to know best strategies...

memu follow ayyedi...product team create epics and ane we eng team create stories under that epic (mostly technical jiras)...at the end closing jiras is product teams responsibility...so they wont understand the technical jiras..its not kind of clean process..

[Spartan]

Grooming meetings both PO or TPM. + Engg team.

create Epics and Stories...

 

[Pandubabu]

6 minutes ago, dasari4kntr said:

mee company lo...how is jira work flow..?

whose responsibility to creates epics/stories...and who responsibility to close it..?

 

memu follow ayye dantlo chinna flaw vundi...just trying to know best strategies...

memu follow ayyedi...product team create epics and ane we eng team create stories under that epic (mostly technical jiras)...at the end closing jiras is product teams responsibility...so they wont understand the technical jiras..its not kind of clean process..

technical debt epics and stories technical team,

business stories , business analyst and project lead create, Dev and QA will provide more details during refinements

[hunkyfunky2]

Technical stories - closed by who ever it is assigned to or who opened it ...after it's accepted .

These are 3 different people or same person... No fixed rule.

 

[dasari4kntr]

27 minutes ago, Spartan said:

Grooming meetings both PO or TPM. + Engg team.

create Epics and Stories...

 

 

21 minutes ago, Pandubabu said:

technical debt epics and stories technical team,

business stories , business analyst and project lead create, Dev and QA will provide more details during refinements

 

3 minutes ago, hunkyfunky2 said:

Technical stories - closed by who ever it is assigned to or who opened it ...after it's accepted .

These are 3 different people or same person... No fixed rule.

 

for us we are not allowed to close jiras…product team is not closing most of the jirs…because they don’t understand…so it ending up as spill over items during sprint switching…(even though they are done..)

[tollywood_hater]

31 minutes ago, dasari4kntr said:

mee company lo...how is jira work flow..?

whose responsibility to creates epics/stories...and who responsibility to close it..?

 

memu follow ayye dantlo chinna flaw vundi...just trying to know best strategies...

memu follow ayyedi...product team create epics and ane we eng team create stories under that epic (mostly technical jiras)...at the end closing jiras is product teams responsibility...so they wont understand the technical jiras..its not kind of clean process..

for tech stories add review step , leads can add review comments and product team close stories in review status with appropriate lead/eng yeam comments 

[kakatiya]

Product owner creates a meeting invite for " story creation + story refinement in backlog" we follow a excel template on SharePoint for each type of story and make changes to template if required..

Each individual will contribute in those meetings if they think their story is missing in backlog

Then scrum master reviews it with acceptance criteria and moves to backlog..

During sprint planning , we move from.backlog to current sprint 

[kakatiya]

Note that epics, features,  containers are used interchangeably 

I am safe agile certified..I dont know why I took it..it was just client requirmenet..they paid me 800$ to get certified

[dasari4kntr]

16 minutes ago, tollywood_hater said:

for tech stories add review step , leads can add review comments and product team close stories in review status with appropriate lead/eng yeam comments 

this is our detailed process...

 

product team, UX team, engineering team..

product team sets the goal for the sprint...and create epics...UX teams provide figma screens..

based on the UX designs me (lead) create jiras...which are some functional level...some are bit technical..

once team member finish the jira and raise the pull..they put it in review status...

once reviw is done...we do dev release...move the jira to testing status...

if the jira is in testing status...product team has to test and close it...

but here...some of the jiras are not getting closed...becuase product team dont fully understand...they approach me...i will explain sometimes...so they close...if i am not available..they leave as it is..

i think we need to find a best process...for 2024..

 

[AndhraPickles]

Jilakara minus laka = jira ani maa Lead cheppindu...ade follow avuthunnam...

[tollywood_hater]

8 minutes ago, dasari4kntr said:

this is our detailed process...

 

product team, UX team, engineering team..

product team sets the goal for the sprint...and create epics...UX teams provide figma screens..

based on the UX designs me (lead) create jiras...which are some functional level...some are bit technical..

once team member finish the jira and raise the pull..they put it in review status...

once reviw is done...we do dev release...move the jira to testing status...

if the jira is in testing status...product team has to test and close it...

but here...some of the jiras are not getting closed...becuase product team dont fully understand...they approach me...i will explain sometimes...so they close...if i am not available..they leave as it is..

i think we need to find a best process...for 2024..

 

add one more step , if it is tech story ,product can move to "Tech/Lead Review" from Testing status if it is functional they can directly close it. 

 

your team will review "Tech/Lead Review"  stories and close them ....

[dasari4kntr]

1 minute ago, tollywood_hater said:

add one more step , if it is tech story ,product can move to "Tech/Lead Review" from Testing status if it is functional they can directly close it. 

 

your team will review "Tech/Lead Review"  stories and close them ....

alantide cheyyali...headh ache entante...ee process change cheyyadaniki...four five meetings vuntayi...

[tollywood_hater]

3 minutes ago, dasari4kntr said:

alantide cheyyali...headh ache entante...ee process change cheyyadaniki...four five meetings vuntayi...

lol , I am architech so no more scrum meetings , stories head ache bro

[Aquawomen]

me lead create chesatadu neeeku assign chestadu

next day JIRA open chesi dev to progress lo pettu

1 week progress lo petti working ani chepu

1 week taravatha done ki change chesi next day bug issue pettu follow same steps for one story

[enigmatic]

1 hour ago, tollywood_hater said:

I am architech so no more scrum meetings , stories head ache bro

ante emi chestaru