I was working with a client recently and we had a challenge, the organisation wasn't used to Agile ways of working. It's pretty old hat now and I thought the days of Agile evangelism were behind us. But evangelism of some methodology is always going to exist in our life time so the manifesto may well be useful for years to come.
Your manifesto is a rallying cry to those around you to declare that you are here, you have a mission and this is how you're going to do it! Things you'll want to cover in your manifesto can include:
Your goal gives your team a shared purpose, something to orient around and work together towards. There's nothing unusual about this, just to say don't forget it here because everything you say in your manifesto herein hinges off it.
Saying how your going to measure success is pretty important. It may demonstrate a new way of doing it (e.g. OKRs) and it's important people understand why you've chosen you how to measure your success if it's off-piste from how the rest of the organisation does it.
The other key reason to define your measures of success is it makes your team accountable, a little pressure on yourself is no bad thing. I like to think it helps focus the mind, just be sure you've set the right measures to achieve your goal.
The identity of your team is more than just the job roles, although I would include that too. The identity of your team should include the characteristics of how you work and behave.
Think about how you work, is it cross-functional, multi-disciplinary, agile, lean? Put each one you are or strive to be and say why it's important to your team.
Apart from these management and organisational systems think about the soft skills your team want to champion. Are you candid, are you radically candid? Do you believe in an adversarial environment, do you want to promote getting shit done?
"Psychological safety – We believe everyone makes decisions in good faith to the best of their ability, we use open feedback loops to learn when things don’t go well rather than look to find a scapegoat."
Possibly the most important part of a team manifesto is your principles. Some of your principles may be borne out of your identity, put them wherever feels right. But lots of them are about how to do business like how you plan to disseminate your work and if you prioritise accuracy over speed or vice versa. You may be committed to leaving a strong legacy and so strong documentation might be a principle to highlight.
It's important to call out the tools you wish to employ to enable you to achieve your goals. Explain the benefit they bring and why you use them over other tools. Failure to do so may lead to you losing those tools completely or to other less favourable ones.
Think about listing your collaboration tools, your planning software and development environments.
Finally, the output. All teams are expected to produce some sort of output even if they don't deliver a positive outcome. It's kinda sucky thing to commit to, so keep it light and as non-commital as possible. Remember the mission here is to get acceptance and buy-in for your 'whacky' new mindsets. Pointing to outputs keeps the neighsayers at bay because it's gives them the fallace certainty their comfortable with.
Ways of working like Lean, SAFe, Agile, and so on. They're all belief systems preached to one another. Our Manifesto is no different. Once it's defined you have to spread the good word. Snag influential folks early to really help prop up your manifesto. Maybe not only will you achieve buy-in a freedom to work as you wish but you'll find some others looking to join the movement.
UX is like a joke. If you have to explain it, it's probably not that good*.