...
broadened concept beyone software dev
success factors on Agile projects
- size of team
- criticality of solution consequences
- environment volatility
- team skills and turnover
- company culture
software delivery challenges
- productizing innovation
- respond to market pressure
- organization resistance
- product quality
agile challenges
resources
domain knowledge
customer engagement
customer commitment
customer understanding
customer ownership
customer funding
skills
xuc - executable test cases for requirements
data and services integrations for testing
automated devops - CI/CD
tracking progress - actual vs expected sprint burndowns
rework
late definition of xuc
definition of ready poor
definition of done poor
slimplicity focus missing
non-functional requirements not well defined
acceptance criteria are happy path only
requirements ignored current user experiences
developers don't eat their own cooking
developers are not users
who is solution champion? owner? user?
change management process not mature
feature prioritization - moscow rules
release planning
sprint planning poker
sprint environments
epic, stories as BDD with acceptance criteria and "SO" clause on expected impacts ( as X given Y when Z then U so V )
dependencies between epics, stories poorly defined
complex requirements and processes not modeled for clarity prior to development
is solution any good if user doesn't understand it?
project context not defined - prioritization of requirements, acceptance criteria, MVP metrics, plans for resources, contingency plans etc
continuous customer feedback
...