Operations is everything that happens to software after it is written: releasing it, giving it an address, keeping it patched and backed up, watching it, and repairing it when it breaks. For a long time that was the job of a separate team, and developers handed their work over to it.
The word NoOps dates from 2011, when analysts at Forrester Research argued that cloud computing would move the effort from collaboration between developers and operations to automation. If a cloud service can release, scale, and repair an application by itself, the developers can use that service directly.
The name promises more than the idea delivers, and people who run systems for a living have criticized it for that since it appeared. Nothing removes the work. What changes is who does it: software takes the routine, a platform or a provider takes the infrastructure, and the team keeps the decisions.