Our Terms of Use and Privacy Policy have changed. We think you'll like them better this way.

Corporate2Business Owner Cafe

Project Rescue REAL Talk Featuring Agile SDLC Coach @ Jacqueline007

×  

Follow This Show

Stay in the know about new episodes and updates.
Coach Jacqueline007 and David are STEM/STEAM advocates with an emphasis on the T toward every IT (Information Technology). STEAM (Science Technology Engineering Art/Design and Math) is the global language for Innovation. Business AGILITY is the framework used for radical change by innovators, inventors, entrepreneurs, thought leaders, and change agents! If all of this doesn't immediately make sense or engage you, no worries listen to a few episodes and awaken your inner TECHIE and inner NERD! Take Ten to Fifteen Minutes every day to Better Understand the Digital Language that will unlock the mysteries of Science, Technology, Engineer, Math + Agile which is the language of the folks that control the future and will dominate the World We Live In. Don't believe me? #ElonMusk No One Should Be Content with Ignorance. Ignorance is Ignoring the Opportunity to Learn. Information+Action #ExpressoUrself Email us @ technologyexpresso@gmail.com Chat Online with us @ www.techexpressoconsulting.com Call Us @ 855-484-6837 #fullSTEAMahead #CoachOnCall #VirtualAgileHelpdesk #AgileSecretsRevealed #TheAgileDiva #AgileTakeOver

On-Demand Episodes

This episode covers who's wring the user story or who should be wring it.

This episode covers "So That" Statements or Purpose Statements or the Why. The question that should be asked is so what if we don't do this story what will we be lacking.

Using Business Value Points (BVP) for User Stories to help define scope, help prioritize and make planning smoother. BVP can use the same framework as Story Points (i.e. a modified Fibonacci Sequence). For example: BVP 13 - Will... more

Learn the purpose and intent of Acceptance Criteria. Get tips on how to separate and keep your Acceptance Criteria from being: (a) a list of tasks (b) too technical (c) a test script And find out if the Gherkin Method (Given, When, Then)... more

Hear about my journey for the last 30 years and my quest to understand the best way to healthy, sustainable approaches to software development. And how I help empower each of my clients to create a relentless, continuous improvement... more

The team, along with the product owner and scrum master, needs to make sure you are keeping all forms of debt at bay. Technical debt is only one type of debt that you can accumulate as a part of product, service or software delivery but... more

Technical Debt is the accumulation of what is known as enabler and technical stories. It's when you've built the features and not the backend processing, business rules, data and non-functional mechanics that make a story or MVP... more

Understand why your backlog should be Colorful (colored stickies), Circular (Later, Next, Now) , Prioritized, Balanced and Include Administrative Work Items (i.e. training, documentation, refactoring).

A technical story is one where the main stakeholders are the engineering/infrastructure team/leadership. The end-user benefits only indirectly from such a story. Technical stories often are non-functional requirements.... more

This episode explores Acceptance Criteria which are not exactly the same as traditional requirements, but the more you know about traditional requirements the more you can use some of the same techniques for reconciling what's missing.... more
Show Extras

Facebook comments

Available when logged-in to Facebook and if Targeting Cookies are enabled