Here is recording 2nd session "Salesforce User Stories in Action" kzfaq.info/get/bejne/j6d3ocuCxL69oIU.html

00:02 Introduction to the session on when Salesforce met Agile. 02:07 Agile scrum in Salesforce explained 06:16 Agile in Salesforce requires a mindset shift towards welcoming diverse perspectives and learning from past mistakes. 08:13 Agile is all about adapting to change. 11:58 Happiness and collaboration are crucial for success 13:49 Agile implementation enables incremental and safer delivery with high quality 17:37 Agile allows for iterative development and flexibility in incorporating changes. 19:20 Priority-driven Agile approach in Salesforce implementation 22:50 Agile methodologies focus on eliminating waste and achieving continuous progress. 24:34 Key pillars of Scrum are transparency, inspection, and adaptation 28:28 Understanding epics, features, and user stories in Agile Salesforce implementation. 30:12 Creating user stories for product backlog 33:30 Roles in a scrum squad 35:23 Developers in Scrum are self-managing and work on cross-functional teams. 38:53 Sprint addresses sprint goals, product backlog, and work planning 40:32 Daily scrum promotes self-managing teams and improves communication. 44:04 Agile team focuses on retrospective and immediate improvements 45:49 Definition of Done criteria in Agile Salesforce implementation 49:11 User story estimation process and sprint planning in Agile Salesforce implementation 50:53 Consider capacity for sprint planning 54:31 Breaking down user stories into logical tasks is crucial for efficient implementation. 56:12 Monitor velocity and capacity to set realistic sprint goals 59:32 Demonstrate user stories early for better feedback and customer satisfaction. 1:01:07 Handling feedback for user story changes 1:04:18 Improvement in communication about impediments 1:05:59 Salesforce implemented Agile workflow to boost growth and innovation. 1:09:39 Optimizing customer service through agile salesforce implementation 1:11:25 Start with capacity for first sprint in Agile implementation 1:14:53 Product owners need to be available for clarifications 1:16:33 Demonstrating user stories and obtaining feedback during sprint review sessions 1:19:59 Importance of having knowledgeable product owners in agile Salesforce implementation

I feel these two sessions are underrated. Great presentation

Great session !!!! Thanks Sudha and Apexhours team

Very informative. Thank you for sharing.

Great session, and very practical, thank you

47:36 story snapShot 57:28 Sprint goal (Do not overPace the Velocity)

Thanks. Very informative

Thank you, this was helpful

What's the role of Business Analyst in Salesforce Agile project? And how is product owner different from business analyst?

Sir, I really need your advice, I am from elect eng background 4.5 yrs and current salary 20k, I recently got a Salesforce Dev job with 12k. Should I leave my current job and join Salesforce Dev job? Kindly help me.

Solution architect

solution architect please

when salesforce met agile what does you mean by Agile? cpmmitment , forcus ,respect ,openNess , Courage Mindset=>culture to work away from traditional way; =>cross function team with differnt capability or skillset (developer,tester,architect) =>lerning from past mistakes =>Accept mistake/change and adapt quickly..less setBacks =>our teams should be transperent => comuunicate and share and become cumulatively powerful => sustainable work Pace =>Happy teams in or out of work compassionate and happy colleagues => happy customers high business value to customer safe delivery with lesser problems in production waterFall vs Agile?? waterFall fixed.. no sudden changes....Watefall The work is predictable and the outcome is known =>very limited room for inovation and feedback => Agile=> start asap..with minimum viable product(MVP); most important and fundamental things will be first accomodate new ideas and learning time and again... scrum==> Empericism (experiance) and Lean thinking (what is impoprtant..weightage) ==> transperency and communication => collective responsibility => Adaptation => inspect and Adapt => increase proficiency scrum Squad 1.Product owner.. responsible for produsct an prioritisation=> epic(Lrger level) , features and user stories(granular level) =>ensure team understand Product BackLog Items =>maximum value of product(ROI => returt on investment => Efficienct) Scrum Master ...serves srum team and the larger Organisation ...ensure scrum is adopted well ...Scrum Coach / Mentor ... remove Impediment Developer cross_functional (developer,tester All).. defintion==> What you have completed(what part of product is done) scrum frameWork product backlog is constantly evolving Based on inputs fron executives team and stakeholders customers and users.. Sprint are heartbeat of scrum... ideas are turned into value; it is timebox iteration of countinuous developement cycle..... Incremnt or multple increments are created.... increments are done product or potentially shippabel items.. ==we try to achieve sprint goal and make achivement p== wht the sprint? what is done in sprint? what is work in sprint? sprint Goal=> 1.daily standup ...inspect problem and adress in 24 hours..it is not a status meeting... it is to improve self management goals... improves communication and transperency ...rohan you callOut when you see any impediments by yourself...do not wait for daily scrum...reach out to scrum master... 2. Sprint review inspect outcom of sprint and lookout for future adaptation... scrum teams presnt there outcom to key stakeholders and the progress towords the prduct goal...(this is not sprint Demo)... 3. Finished work... 4.Sprint retrospective.. what went well an unwell an what can be improved..Action plan for future improvement defination of DONE.. you are truly done with a story in a sprint/feature in a release when you meet certail crieteria.... (Acceptance crieteria is different than DONE) Acceptance is a part of your user story..... testable statement for a story to complete... DONE...MY sprint is DONE WHEN 1.Acceptance crieteria met(one of the condition for DONE) 2.peer reviewed 3. Apex test coverage >=85%; 4. Stories tested and passed Integration are fully tested and passed 5.All defects fixed , retested and Closed 6.user stories to po complete and Approved Dummy story 1. produsct backLog by owner see the stories at 47:36 story snapShot 2. velocity (earlier sprint) Velocity is a measure of the amount of work a Team can tackle during a single Sprint and is the key metric in Scrum. Velocity is calculated at the end of the Sprint by totaling the Points for all fully completed User Stories. Avg story point on an avg you have completed pr sprint.. 3.Capacity (onGoing sprint) In scrum, capacity is the amount of product backlog items that a team can satisfy during a time box without going to heroic efforts. Capacity is measured by the sustainable pace that the team can achieve and that is based more on throughput of product backlog items addressed instead of number of hours you have to work. plan B, vacation days,...How many Hours of time we have per day..an also per sprint.. 6.5 hours per person per day productive hours Task are picked by ourself; whta fits our skillSet... if my velocity is 20 USP(user stori points)... I sould not pick tasks which will add more than 20 USP per Sprint 57:28 Sprint goal (Do not overPace the Velocity) dont be a yes man to the customenr...sy no if when it needs to be...it is not necessary that you should complete the task at the cost of problem inthe future...