10 tips on how to prevent business value risk
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Floyd Marinescu on Jun 08, 2007
Agility at scale, become as agile as you can be
Complimentary Gartner (Hype Cycle for Cloud Security Report)
Modeling Your Cloud Services Brokerage
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!
Content has been tremendous on this site. Opportunities for improvement:
1) Content is more in-depth than the 'other' sites, but it takes longer to generate. Turnaround time can be better. Waiting a few extra hours for journalistic research on breaking stories is great, but when it takes a couple of days the story starts to feel a little stale.
2) Need a more active community. It's nice to be in a place without the Rolf Tolleruds, but quite frankly those types of people are the cost of having a lot of people participating in active discussions.
3) Take a few more risks. Remember how TSS used to do a bunch of stupid crap like playing cards and rewards for user reviews and begging people to send in funny cartoons? Yeah, most of that stuff didn't work out, but it was entertaining and kept things moving. It tended to drive up user involvement.
Thanks Corby. There is definitely always more 'stupid crap' to try out. :) It's nice to be in a place without the Rolf Tolleruds, but quite frankly those types of people are the cost of having a lot of people participating in active discussions.
Actually I think that in many cases (at least early on TSS' life) they were the catalyst, and later after people go used to participating the momentum kind of just carried on.
The discussions will come. TSS didn't get any regular meaningful discussions going on until near the middle of its third year, so we're on our way. :)
Hi There,
I like your "AJAX"ian approach to building this site. Sometime back, on TSS, there was an article describing how TSS was built. Is it too early for the same on InfoQ ?
More community participation would certainly help. But there are other communities today(IBM developerworks, java.net, javablogs) than existed for TSS during the early days and there are lot many blogs which consume user/dev. time than just these portals. So, the growth of InfoQ cannot be expected to grow like TSS. I still wish that InfoQ grows and enriches the community.
BR,
~A
Congratz guys! InfoQ is awesome. The quality of its article is by far the best in the community. Continue your great work. I enjoy reading the articles. It's nice to see a web site caring about the content quality instead of posting 3 times a day about another framework getting released.
InfoQ has been around for just one year? Really?!! This is amazing. Great job, guys.
InfoQ is definitely one of the must useful sites out there right now. A constant stream of really good content.
So thank you, and congratulations.
Yes, the balance between good, detailed coverage at the cost of time (potentially feeling 'stale') and rapid coverage that lacks depth is a hard balance. I personally lean towards the former, because in the era of newsreaders and rss feeds, the basic facts of the news have a tendency to spread with or without sites like InfoQ, but good detailed commentary that assembles more than the base facts can be difficult to find consistently.
That said, it's good to get feedback on which side people feel we're erring in that balance.
I thoroughly enjoy InfoQ. Keep up the great work!
A year really?, It's been so fast.
Nice job.
As they would say in my country:
Felicidades.
A year really?, It's been so fast.
Nice job.
As they would say in my country:
Felicidades.
I'm not sure if we share a country, but we certainly share the sentiment. Congrats!
One year has passed so fast!
InfoQ is awesome! Congrats on the excellent work! Really good (and excellent) content!
InfoQ in Chinese...that is so cool! Any plans for InfoQ in Spanish?
Cheers,
-Alex.
Congratulations to InfoQ and to Alex as well. :)
As for the community activeness, I guess most people (me at least) visit InfoQ constantly and read the articles and comments but just didn't post anything.
Cheers.
InfoQ had done a great job. Let's enjoy InfoQ and InfoQ China now and InfoQ *** in the near future!
Cheers.
InfoQ is the first site I bring up every morning when I get to the office. Always something new and interesting.
Congratulations and keep up the outstanding work.
PS: I second the request for a technical article describing how infoq.com was designed and built. (Including the pains and mistakes)
Gavin
A great year, a great site. Keep it up, Floyd & team!
Congrats Floyd and to the entire infocrew!
2) Need a more active community. It's nice to be in a place without the Rolf Tolleruds, but quite frankly those types of people are the cost of having a lot of people participating in active discussions.
PLEASE NO! This is what I like about InfoQ.
Any plans for InfoQ in Spanish?
Not at this time, but if a company came forth wanting to provide InfoQ in Spanish we would gladly facilitate it.
Thanks everyone. The most thanks should go to the editorial team and the entire staff for making this all possible, I am but one of many. :)
First time I came to know about this site was at the Spring Experience in Dec, 2006. Since then I have been a regular visitor. It is a very informative site. Enjoyed several video interviews and presentations posted.
CONGRATULATIONS.
Congratulations! You accomplished a great deal in one year, Floyd and Alex.
I don't think the discussion part is all that necessary, really. What people want is a portal to find the kind of news and information that interests them, and InfoQ has done a great job at doing that. Good job by the contributors/editors Scott, Obie and Stefan (the ones that I read, at least)!
I second the request for a technical article describing how infoq.com was designed and built. (Including the pains and mistakes)
Last year I have given a couple of presentations at different conferences on this topic, so you may already find something online. Hopefully, I will get the time to start writing a detailed article. However, for the moment I am pretty sure I will not call it Lessons learnt, as I am learning something every day :-).
./alex
--
.w( the_mindstorm )p.
________________________
Alexandru Popescu
Senior Software Eng.
InfoQ TechLead&CoFounder
While Floyd is thanking the whole crew -- and I am doing the same -- I would also like to thank our readers that send us feedback all the time. They helped me a lot making things right and improving every day. So, please keep them coming!
./alex
--
.w( the_mindstorm )p.
________________________
Alexandru Popescu
Senior Software Eng.
InfoQ TechLead&CoFounder
Congratulations Floyd, Alex, Scott, Diana, and crew! It's been great watching InfoQ grow over the last year. Keep up the excellent work!
Keith
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.
Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.
Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?
Sean Cribbs explains what Map-Reduce and Riak are, why and how to use Map-Reduce with Riak, and how to convert SQL queries into their Map-Reduce equivalents.
24 comments
Watch Thread Reply