I just received my annual TCP-1 letter from LLNS and a summary of the LLNS Pension Plan. Looked in pretty good shape in 2013. About 35% overfunded (funding target attainment percentage = 134.92%). This was a decrease from 2012 where it was 51% overfunded (funding target attainment percentage = 151.59%). They did note that the 2012 change in the law on how liabilities are calculated using interest rates improved the plan's position. Without the change the funding target attainment percentages would have been 118% (2012) and 105% (2013). 2013 assets = $2,057,866,902 2013 liabilities = $1,525,162,784 vs 2012 assets = $1,844,924,947 2012 liabilities = $1,217,043,150 It was also noted that a slightly different calculation method ("fair market value") designed to show a clearer picture of the plan' status as December 31, 2013 had; Assets = $2,403,098,433 Liabilities = $2,068,984,256 Funding ratio = 116.15% Its a closed plan with 3,781 participants. Of that number, 3,151 wer...
Comments
This type of sharing cooperation with Russia has been in effect for many years, for reasons of helping to secure nuclear materials, and the fact that reconsideration based on recent events has not occurred yet is not a "scandal" or "criminal," it is just another excuse for congresspeople with nothing better to do but blather to the media.
It is not hard to find stories of offshore software development firms over-promising and under-delivering. With increasing competition among offshore vendors, some of the companies would go to any length to land contracts. In a desperate attempt to keep up the volume of work, they tend to start telling the clients exactly what the clients want to hear, all the time. They end up saying Yes to everything that comes their way. '
2
Get involved, stay engaged
Some people still think that you can put a bunch of software developers in a room, feed them project specifications, pizza and soda, and the complete product magically appears in a few weeks or month, only to discover upon delivery that project has gone way off-track. Not being passionately involved with your offshore team is a recipe for failure. Your team is not addressing a technology challenge; they are addressing your business challenge using technology. And no one knows your business and your vision better than you.
3
Communication is key
It's easy to underestimate this, but communication failures are the biggest IT project killers; whether they are onsite or offshore. Putting good communication frameworks in place is ever more critical while working with global teams. One of the most important things you should do is to demand a seasoned project manager located offshore who works directly with the developers. This person should manage all communication since developers are not the best communicators and should provide you daily status reports. I
offshore company formation
NNSA Gives Russia Free Military Equipment
Who posted about software development and why (especially under this topic)?!