Difference between revisions of "WestCoast2008:Product Management for Nonprofit Software"

From Managing Nonprofit Technology Projects Wiki
Jump to navigation Jump to search
 
Line 1: Line 1:
 
=== Description ===
 
=== Description ===
  
While a best practice for Nonprofit technologists is to try and utilize existing tools and services, there are invariably times when the appropriate tools and applications don’t exist. But software development is not a core competency of most Nonprofits, and too often Nonprofit software development efforts spiral out of control or end in less-than-complete realization of vision. This session will explore how best to get from concept to running code with out losing focus on mission.
+
While a best practice for Nonprofit technologists is to try and utilize existing tools and services, there are invariably times when the appropriate tools and applications don’t exist. But software development is not a core competency of most Nonprofits, and too often Nonprofit Software Development Efforts spiral out of control or end in less-than-complete realization of vision. This session will explore how best to get from concept to running code with out losing focus on mission.
  
 
=== Session Notes ===
 
=== Session Notes ===

Latest revision as of 00:08, 14 January 2016

Description

While a best practice for Nonprofit technologists is to try and utilize existing tools and services, there are invariably times when the appropriate tools and applications don’t exist. But software development is not a core competency of most Nonprofits, and too often Nonprofit Software Development Efforts spiral out of control or end in less-than-complete realization of vision. This session will explore how best to get from concept to running code with out losing focus on mission.

Session Notes

Notetaker: none

(Session Note Taker will enter notes here)