Perhaps this is subject to experience. For the most part, development and infrastructure project IT lifecycles or frameworks/methodologies are the same. Loosely speaking, in the development project lifecycle, there are the discovery, design, development and release phases with sign-off/approval stop gates between each phase. In infrastructure, there is also a discovery and design phases; however, the development and release phases are commonly referred to as the build and deploy phases respectively. Good examples of methodologies to use are the Microsoft Solutions Framework/Solution Delivery Methodology which consists of envision, plan, build, stabilize and deploy phases.
I think that if one steps outside of the specific activities of a development framework/methodology and takes a more abstract look at the process, and management thereof, then it becomes apparent that many of the same principles can be applied.
There are more methodologie and frameworks out there and the correct one for a given IT infrastructure project will depend on the size, scope and complexity of the project itself.