#SalesforceBA exam module: Requirements 17% (10 Questions)
#Agile is not perfect.
Especially in the world of software implementation like #Salesforce.
It’s far better suited in a product development environment, such as an AppExchange partner because of the way the agile framework has been designed.
When we implement Salesforce especially when a partner has been engaged, there are many factors to take into consideration:
– coordination of effort
– upfront discovery and planning
– collaboration of partners and stakeholders
– many moving parts of data migration, integration and BAU release testing/management
Everything is moving, and there needs to be some certainty pinned down, otherwise costs will spiral if you try to run it in a true Agile manner.
In a #ProductManagement environment, when you have your own scrum team – autonomous and independent, with the users, BAs, designers, and developers “co-located”* – being Agile allows you to create amazing software.
Otherwise, in #ProjectManagement, there needs to be a different way of doing things.
User stories is an Agile way of documenting user needs.
Requirements articulated within Business Requirements Documentation is quite different, and comes more from the ‘Waterfall’ world.
And so – with these definition and background provided, I’ve outlined what the differences are (in broad terms).
Of course, the table below is an over simplificaiton of two ways of working that isn’t even homogenous within the proponents of either camp.
No projects are run the same way.
Even within the same Consulting Partner; the #methodologies used may be different based on the
– technology at play
– problem to be solved
– maturity and culture of client organisation
– risk appetite and tech approach to projects from the project team
– the Project leadership and individual experience
– etc etc etc
I could go on forever ♾
However – for the purposes of the exam, let’s just start with some broad differences between User Stories and Requirements.
What have I left out?
—
This afternoon, I am going to get into Requirements part 2 of the #SaleforceBA:
Verify & Prioritise existing requirements and identify new requirements to developo the future state
Join us for highly interactive no-charge workshop sessions. Sign up details below!
*this needs to be re-defined in the remote world
