At least while writing technical papers, avoid creating compound statements! Here is a classic case - an excerpt from a paper that some how got published in Project Management Practitioners Conference (PMPC) 2006.
"Challenges faced by a program manager managing sustaining activities include, but not limited to, managing uncertainties in release timeframes based on availability of resources, communicating with end customers through technical support team to understand reproducibility in local test environment, communicate a schedule, maintaining open channels with customers to understand any modification requests for the product, negotiate with business leaders to incorporate scope changes as needed, and so and so forth."
Whew!! That was one hell of a statement. Does that make any sense to you? It's kinda muddled. Certainly it did tickle my funny bone. I wonder if the selectors gave benefit of doubt to the author. But hey, you don't dish out an à la carte of verbal spaghetti;)