Couldn't agree more. This really expands on your earlier insights about cloud being foundational. I wonder how this intelligence-first approach will reshape team structurs in developement?
That is a great question. Instead of working in SILO's team's should begin to structure themselves accordingly. Don’t split teams by job title. Split them by the goal they own.
One thought is to integrate technical, functional, and developer teams into pods that focus on outcomes. Perhaps a mix of team members: a process lead, a PeopleSoft functional expert, a PeopleSoft developer, and an automation/AI helper.
Faster feedback (see problem → fix it → stop it from happening again).
Couldn't agree more. This really expands on your earlier insights about cloud being foundational. I wonder how this intelligence-first approach will reshape team structurs in developement?
That is a great question. Instead of working in SILO's team's should begin to structure themselves accordingly. Don’t split teams by job title. Split them by the goal they own.
One thought is to integrate technical, functional, and developer teams into pods that focus on outcomes. Perhaps a mix of team members: a process lead, a PeopleSoft functional expert, a PeopleSoft developer, and an automation/AI helper.
Faster feedback (see problem → fix it → stop it from happening again).
Clear ownership (one team, one scoreboard).
Less “throw it over the wall” drama.
YEP. The more we can use AI for the templates, time saved.
BUT !! It doesn't replace HI .. Validate everything, document everything, upload that document to 2/3 AI sites, and repeat till happy.
Ian, I can't agree more that AI cannot replace HI. Thanks for your comments