September 2010
31 posts
Layering social on top of ERP could be viewed like putting Facebook icing on top of the old ERP (cake) stack.
A complete ground up rethink of ERP goes against the precedents of incremental evolution and senior managements comfortable in avoiding risks.
The type of innovation needed likely matches the leap of faith taken to author purpose built languages for ERP by visionaries unsatisfied with waiting around for oop derivatives C++ and Java.
Three examples that leapt ahead and generated huge ERP profits: ABAP from SAP, Dexterity from Great Plains and X++ from Axapta.
Today, Facebook and SNS peers have leapt ahead utilizing distributed storage of social data using NoSQL from Cassandra, instead of living waiting around for the SQL server database vendors.
Back in 97, MRP/Accounting was redefined as ERP. This meant adding people relationship modules like CRM, SCM, and HRM. Marketing updated the brochures, and sales sold more.
Typically, it’s taken new companies like Agile to add external relationship management for engineering change management. And ERP has been stuck in a rut defined by the code written to live behind the firewall.
Since then, the leap to Enterprise Relationship Pull has been limited to incremental steps within existing ERP products.
An accident of haphazard innovation, from a startup or a lab deliberately focused on solving the enterprise relationship pull problem across the firewall, is surprisingly overdue.
Sameer Patel’s excellent write up on Oracle Fusion covers the technology leader efforts on injecting social into ERP source code.
[My opinion the heart of MRP needs rethinking for relationships]
We are, as software developers, in various states of alone-ness.
A company I worked at once had been operating for years under the assumption that it was OK for software to take months to integrate and deploy; they had never heard of continuous integration. They thought it was normal to rewrite…
thoughtbot currently consists of 14 developers and 5 designers. This summer, we organized into 4 smaller teams. We rotate teams every 2 months.
We started our third rotation this week, a moment which prompted the designers to create movie posters for their new teams.
The benefit of team…
“We manage our sales pipeline so that we don’t start new projects right before a rotation.
Another goal is for teams to work on as few simultaneous projects as possible. With our previous free-for-all, some people had to work on 3-4 projects a week. That’s too much context switching. With the rotations, it’s easier to schedule fairly and easier to keep the weekly projects down to 1-2 per team.”
Hell yeah.
I find myself guilty of the ctrl-enter trick. What about you? - via http://michaelduong.com
Mentoring is sharing experiences…
I’ve been pretty MIA about my awesome internship and am dying to hear about yours. Let’s all catch up come Sept. 20 (or whoever’s here for my birthday on the 18th)!
A guest post I wrote for my mentor’s career blog:
——————————————————————————————————————————————————————
At a…