I’m Frank, a former C# .Net software developer and business analyst who specialises in software requirements for agile development teams.
Remote, outsourced and offshore development is difficult to do well, and my time in software development teams, firstly as a hands-on developer and then as a business analyst, clearly showed me this.
Iโve shared my own personal experiences in many articles, the following ones being the most popular.
Large enterprise organisations are unable to achieve much of what conventional agile coaching espouses.
Some organisations donโt want agile
The manager too busy for agile
Imagine being an offshore developer
Agile development teams working in less-than-fully agile settings behave in some rather unhelpful ways.
Gnarly behaviours of Scrum teams
Patterns of enterprise agile dysfunction
Offshore developers that want every detail
Software requirements is a powerful enabler for teams struggling to thrive under an agile framework or approach.
Why you need software requirements
When software requirements would help
How to gather better software requirements
How to write better software requirements
Developers want to work in a way that maximises their effectiveness; avoiding blockers and frequent, unwanted interruptions/context-switching.
Blocked tickets during development
Developers decide the implementation
Developers donโt start with a blank sheet of paper
Developers donโt want constant conversations
Tailoring the agile framework to accomodate organisational limitations is a pragmatic and highly effective approach.
Becoming less agile to be agile
Moving beyond sprint planning
One of the best agile experiences
|
Frank Ray Consulting. Software requirements for agile development teams, particularly remote, outsourced and offshore development teams working in financial services. |