I'm not totally sold on the whole points poker process though, but that could be a criticism of agile as a whole.
My understanding of agile is give your developers the tools they want, the information they want, and the ability and incentive to communicate widely, quickly, and frequently however they want, and get out of the way. You have to devolve responsibility and accountability for meeting business goals down to the team level though, and that team has to act as one.
None of that has anything to do with "points poker process", or any process. Obviously everyone has a process, even solo developers working on their own hobby, but that process is "what works best".
If it isn't in the 4 values and 12 principles, it's not required in Agile. If it isn't in the guide, it isn't required in Scrum.