Coming from the top they want us to start being more “Agile”. My PM used to do it for us but now they want the engineers to start doing it ourselves. How do I break down backend tasks specifically into user stories? Any advice/insights/tips would be much appreciated!
TC 320k, YOE 7 (Not at HP)
Want to see the real deal?
More inside scoop? View in App
More inside scoop? View in App
blind
SUPPORT
FOLLOW US
DOWNLOAD THE APP:
FOLLOWING
Industries
Job Groups
- Software Engineering
- Product Management
- Information Technology
- Data Science & Analytics
- Management Consulting
- Hardware Engineering
- Design
- Sales
- Security
- Investment Banking & Sell Side
- Marketing
- Private Equity & Buy Side
- Corporate Finance
- Supply Chain
- Business Development
- Human Resources
- Operations
- Legal
- Admin
- Customer Service
- Communications
Return to Office
Work From Home
COVID-19
Layoffs
Investments & Money
Work Visa
Housing
Referrals
Job Openings
Startups
Office Life
Mental Health
HR Issues
Blockchain & Crypto
Fitness & Nutrition
Travel
Health Care & Insurance
Tax
Hobbies & Entertainment
Working Parents
Food & Dining
IPO
Side Jobs
Show more
SUPPORT
FOLLOW US
DOWNLOAD THE APP:
comments
Go to your developer with a sample and see if he needs more details. Identify the pattern for your team and keep doing it.
As a BWW Fan, I want 15 wings with 2 pints of beer delivered to my man cave on every possible football game day, so that I can immensely enjoy my Sunday afternoon.
It’s more like an epic ;)
This comment was deleted by original commenter.
You should be able to say "as a (blank) I want to (blank)" to capture stakeholders and functionality
The PM/Business should be able to define that.
All the technical work would be children of this in phab, jira whatever