What methodology should we use to deliver #Salesforce?
Agile. Scrum. Waterfall. Hybrid. W-agile. SAFe. RAD. Prototyping. UPM. RUP. Extreme. Lean. 😵
With so many to choose from; it’s no wonder people get confused.
Underneath all, the basic foundations still apply – especially for consultancy-led projects.
𝗦oftware 𝗗evelopment 𝗟ife 𝗖ycle
𝗣𝗹𝗮𝗻 the approach
𝗨𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱 the requirements
𝗗𝗲𝘀𝗶𝗴𝗻 the solution
𝗕𝘂𝗶𝗹𝗱 the system
𝗧𝗲𝘀𝘁
𝗗𝗲𝗽𝗹𝗼𝘆
𝗦𝘂𝗽𝗽𝗼𝗿𝘁
This can be a life cycle for a single user story, a feature, an epic, a project, or even a programme of work.
It is a defined and discrete step change from
𝗦𝘁𝗮𝘁𝗲 𝗔 (where we are now)
to
𝗦𝘁𝗮𝘁𝗲 𝗕 (where we want to be)
DevOps and CI/CD, as well as the Kanban way of working lends itself better for environments with
– Continuous change
– Constant improvement
– Steady and ongoing delivery of enhancements and bug squishing
Consulting projects that help organisations move from State A to State B may implement a DevOps environment after go-live, but there is usually a pre-defined methodology for the initial step change.
You might hear of #SalesforcePartners and software vendors will have their very own, special patented delivery model. 😐
They are really all the same though.
Regardless of how its dressed up, the fundamentals doesn’t change:
🍩 Using 𝗘𝗺𝗼𝘁𝗶𝗼𝗻𝗮𝗹 𝗜𝗻𝘁𝗲𝗹𝗹𝗶𝗴𝗲𝗻𝗰𝗲 like 𝗔𝗰𝘁𝗶𝘃𝗲 𝗟𝗶𝘀𝘁𝗲𝗻𝗶𝗻𝗴 and 𝗔𝗿𝘁𝗳𝘂𝗹 𝗤𝘂𝗲𝘀𝘁𝗶𝗼𝗻𝗶𝗻𝗴 to understand the underlying pain and how they got there 👂🏻
🍩 Using 𝗖𝗿𝗶𝘁𝗶𝗰𝗮𝗹 𝗧𝗵𝗶𝗻𝗸𝗶𝗻𝗴 and 𝗦𝘆𝘀𝘁𝗲𝗺𝘀 𝗧𝗵𝗶𝗻𝗸𝗶𝗻𝗴 to understand the big picture, the impact of micro decisions on long term goals 🔭
🍩 Using experience and skill to design and build a solution that delivers value to the business 📈
I cover these topics (and more) on my Consulting Deliver Masterclasses – next one starts on 𝗦𝗮𝘁𝘂𝗿𝗱𝗮𝘆, 𝟰 𝗠𝗮𝗿𝗰𝗵.
Want to win a chance to attend for free?
Details in comment 👇🏻
We already have 16 entries for the competition and it isn’t too late to register!
Also if I didn’t mention – Free daily virtual donuts!! 🍩😋
See you there?
#OnThePeiroll
