Showing posts with label Information Automation. Show all posts
Showing posts with label Information Automation. Show all posts
Thursday, June 5, 2008
Information Automation, Day One
Projects compete for scarce developer hours.
A project can have failure modes as a project, or have failure modes specific to attracting sufficient developer hours. (obviously, if a project fails as a project, the developer hours it will be able to attract will go to zero)
Also, not all development hours are equal, because not all developers are equal.
There are many ranking of fitness of developer that are demonstratively faulty. Be careful. Make sure the ranking of fitness matches concrete results.
What are the paths to be developed?
Management; Business; Personal Effectiveness; Information Automation; Effectiveness Modeling; Teaching Personal Effectiveness
OK, got Day Zero, what would be Day One?
Business: singular, consistent source of increasing value, at lower total cost; or else, race to the bottom
Management: if considering a group of more than one person, either Value the Differences, or Continually Fight the Differences, until 100% of the effort, attention, focus is spent fighting the differences, and nothing of value gets done
Image via Wikipedia
- Throughput
- Latency
- Sustain Increasing Bandwidth
- Integrity and Correctness
- Respects Rules of Trust Relationships
- Respects Rules of Security
- Reliability
- Availability and Accessibility
- Scalability (and Distribution of Working Instances)
- Economic use of Limited Resources
- Timely Implementation with Available Resources
- Satisfying Human Value
- Not Violating Human Sensibilities (including Regulatory requirements)
- Iterative Development
- Ability to be Sustained by Attracting enough developer hours
- Distributed Development
Subscribe to:
Posts (Atom)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=9f41b957-b8a0-4c70-8d52-0cb76d721b68)