What we covered:
- Agile Frameworks;
- Organization/Technical Governance Boards;
- Release and Instance Strategies.
Content:
- Scrum: Targeted for a small number of teams (1-2) working together on the same scope.
- Scrum of Scrums: Small teams with less than 50 people, targeted for separate agile teams that have dependencies for product release.
- SAFe: Dedicated to larger teams (50+) with multiple value streams to be managed/coordinated.
We chose Scrum of Scrums based on the Case Study requirements, and SAFe for the long-term roadmap.
Regarding the Organizational/Technical Governance Board, instead of focusing solely on Tech Governance, we suggested a comprehensive vision that includes CoEI.
- Governance is about accelerating decisions and outcomes: Effective governance clarifies who makes decisions, how they get made, and what outcomes they should deliver.
- Strategy should drive governance: Start by defining how strategic decisions are made. Technical standards and policies need to be informed by strategy.
- Avoid governance for the sake of governance at all costs. Once you’ve established governance, continually evaluate how and where you can improve and simplify your approach to decision-making.
Every ServiceNow initiative should have at least three crucial boards to ensure that the strategy is aligned with the goals of the organization. These are the Executive Steering Board, Demand Board, and Technical Board. As an implementation partner, it is crucial to discuss this with your customer. As a platform owner or customer, it is important to have the support of your executives in implementing these boards. This will help ensure that your ServiceNow strategy is on the right path.
For deployment, we suggested using Update Sets per User Story and, finally, creating a Batch Update Set containing all user stories from that sprint to be deployed in Prod. (never merge!)
It was an interesting week, especially because I was the one to present. I started the prep work on Friday night to put on content that could easily be a 1-hour-long meeting, but as per recording rules, it should last 10 minutes.
So, I recorded my first clip for over 25 minutes and it took me more than 10 tries to finally get a 10:54 clip that I felt was ok to submit to meet the deadline.
I wasn't 100% satisfied with the recording that I submitted. However, after reviewing the feedback from my cohort and considering the events that occurred during this week, I believe that it was a decent attempt. I will take the feedback into account for my next recording.
Key takeaways:
- The tool provided by ServiceNow for screen and camera recording is great for your first recordings, but for the definitive version, I would recommend using Teams/Zoom and then uploading it to the platform to be graded by the AI...
- Double-check lighting and microphone quality;
- Less is more - you don't need to add complex slides, so make sure to cover important points in the speech.
- Business-smart customizations are an essential part of good governance;
- You can accelerate your digital transformation with citizen development empowering your Business Units;
- Make sure your Organization Boards have metrics for measuring success, otherwise you'll lose control of it.
- I have used https://slidesgo.com for this week's presentation, pretty good tool and even the free templates can be useful.
Kudos to Mike Ward for being named Super Contributor of the Week. Inferno Squad is starting to rack up badges! 😎
Thanks for reading!
