1. Introduction
1.1 The Bay Area Agile Project Leaders Network local chapter (BayAPLN) was founded in 2006
1.1.1 to support a community of practice in the greater San Francisco Bay Area to discuss, develop, and promote techniques for the management of agile projects and agile organizations. BayAPLN is a local chapter of the national Agile Project Leaders Network (APLN).
Old APLN tri-fold Brochure
1.2 BayAPLN seeks to provide developers, practitioners, and managers
1.2.1 with a venue to share practical advice, experiences and insights from the application of agile software development methodologies to project management. We are also exploring and developing agile tools, understanding, and practices at the project, department, organization, and enterprise levels.
1.3 BayAPLN will explore project and organizational management in an agile context as defined by the Declaration of Interdependence for Agile-Adaptive Management:
1.3.1 Declaration of Interdependence (DOI) http://www.pmdoi.org/index.html
We increase return on investment by making continuous flow of value our focus.
We deliver reliable results by engaging customers in frequent interactions and shared ownership.
We expect uncertainty and manage for it through iterations, anticipation and adaptation.
We unleash creativity and innovation by recognizing that individuals are the ultimate source of value, and creating an environment where they can make a difference.
We boost performance through group accountability for results and shared responsibility for team effectiveness.
We improve effectiveness and reliability through situationally specific strategies, processes and practices.
2. Vision
2.1 The Bay Area APLN is a renowned community of project leaders which demonstrates meaning and value through the use of Agile principles.
3. Mission
3.1 We develop, promote, and sustain a learning community of Agile project leaders through: * monthly learning events * opportunities for networking * experimenting with new ways to create Agile project leaders
4. Principles/Values
4.1 Principle Acorns:
4.1.1 Sharing
4.1.2 Adaptive
4.1.3 Leadership
4.1.4 Pragmatic
4.1.5 Cooperative
4.1.6 Knowledge Sharing
4.1.7 Simplicity
4.1.8 Responsibility
4.1.9 Clear Communication
4.1.10 Quality
4.1.11 Pride
4.2 Values
4.2.1 General
Sharing
Adaptive
Pragmatic
Cooperative
Leadership
Knowledge Sharing
Simplicity
Responsibility
Clear Communication
Quality
Pride
4.2.2 Money
Values
14-Supporting and Enabling Community Members
4-Supportive
6-Enabling
11 Low-Maintenance
9 - Transparency
8-Prudent
Cost-Effective
7 - Integrity
7-Adaptive
3-Forward-Thinking
1-Tool
4.3 Principles
4.3.1 Our highest priority is to support our community through continuing creation of opportunities to deliver insight, learning, and networking .
4.3.2 We actively support collaboration within our community.
4.3.3 We embrace the energy of the motivated individuals in our community. We lean towards new initiatives and towards trust in those individuals to support our values while pursuing those initiatives.
4.3.4 Value delivered to the community is the primary measure of our success.
4.3.5 Simpler is better.
4.3.6 The best outcomes emerge from self-organizing teams.
4.3.7 At regular intervals, we reflect on how to become more effective, then tune and adjust.
4.3.8 Participants are free from sponsor intrusion; sponsors may make themselves accessible; participants always have choice
4.3.9 We publicly appreciate supporters of our community
4.3.10 We fulfill our obligations to sponsors
4.3.11 We clarify sponsor expectations before engaging.
4.3.12 We value and foster connections to enhance the local agile community.
4.3.13 Money
Our accounting books are always open
Our spending decisions come from open consensus of CoCo, and are captured in public minutes.
For spending decisions, community support comes first.
The burden of managing the money must be less than it's value
It's not about the money.
BayAPLN treats money matters in a way that complies with the values and legal requirements of our fiscal administrator: Dayspring, Inc.
BayAPLN avoids debt
Our financial dealings are congruent with our charter.
We apply continuous improvement methods to our financial processes.
We actively solicit community involvement and suggestions about BayAPLN's resource allocations.
4.4 Candidate Principle
4.4.1 We are guided by ongoing assessment of value to participants
5. Objectives
5.1 Areas of Measurement
5.1.1 10-Effectiveness
Value to members
Repeat Attendance
New Participants
Membership Growth
User Utilization of BayAPLN Knowledge
Success Stories
How well we use our resources
Networking
Social Networking
Business Networking
5.1.2 7-Sponsorships
In
Out
5.1.3 7-Attendance
At Public Events
At CoCo Meetings
5.1.4 4-Job Offers for members
5.1.5 4-Career advancement
5.1.6 3-Incoming Contributions/Dollars
Dollars
Charge for Attendance rather than membership fees
In-Kind Contributions
speakers
Meeting Space
Corporate Sponsorship
5.1.7 2-Publications
5.1.8 2-Education
5.1.9 2-Awareness
Article in SF Chronicle
Website hits/month
BayAPLN Yahoo Group hits/month
Survey
Other groups acknowledge us
5.1.10 0-Website Hits
5.1.11 0-SIGs
book groups
philanthropy
5.1.12 0-Seminars
5.1.13 0-Regional Diversity
5.1.14 0-Membership
5.1.15 0-Food
5.1.16 0-Events
5.1.17 0-Diversity
5.1.18 0-Cooperative Ventures with Local Companies
5.2 Project (Organization)
5.2.1 By 31 Dec 2009, 400 Sign-Ups BayAPLN Yahoo Group
5.2.2 By 31 Dec 2009, 400 Sign-Ups BayAPLN Linked-In Group
5.2.3 By 31 Dec 2009, BayAPLN has Cash Reserves of $10,000 available for discretionary spending.
5.2.4 By 31 Dec 2009, We will average 75 event attendees per month for 2009
5.2.5 By 31, Dec 2009, we will have TEN "Metal" Sponsors
5.2.6 By 31 Dec 2009, 50% of persons in event attendance will have provided feedback declaring the value they perceived from each event.
5.2.7 By 31 Jan 2010, 80% BayAPLN participants agree, by vote, that the BayAPLN organization has run consistently in alignment with Agile Values during 2009.
5.2.8 By 31 Dec 2009, 100 BayAPLN folks have offered online public commentary and/or actionable feedback about the BayAPLN in 2009.
5.2.9 Hold
Every year BayAPLN increases membership by 20%.
Membership is defined as being signed up with the Yahoo Group.
By 31 Dec 2009, we will have ## members
Retrospectives
Measures of Activity
Web Site
Blog
Attendance at events
Success Stories
By Mid-June 2007, 10 current members offer endorsements/stories describing BayAPLN as a source of help, appearing on the BayAPLN website.
Patrons write success stories
Members write success stories
Incoming Contributions
5.3 System
6. Boundary Exhibits
6.1 Context Diagram
6.1.1 Boundary Visio File
Draft20090606
Untitled
Draft20061005
Untitled
6.1.2 Boundary PDF
6.1.3 BayAPLN
National APLN
Guidance
Representation
Funding
Bay Area Membership
Sponsor
Funding
Press
Press Release
Thought Leader
Invitation
Presentation
Endorsement
Learning Event
Hosting
Local Special Interest Group
Interest
Invitation
Corporation
Prospective Member
Invitation
Membership
Member
Meeting Notice
Announcement
Contribution
6.2 Key Event Roster
7. Committed Resources
7.1 Personal time
7.2 Energy
7.3 Web Site
7.4 Yahoo Group
7.5 Meeting Space
7.5.1 Outformations - Oakland
7.5.2 Saleforce.com
7.6 Meeting Sponsorship
7.6.1 Outformations - Oakland
7.6.2 Saleforce.com
7.7 Personal Networks
7.8 Money
7.9 Decision Making from external and internal resources
7.10 Permission to Iterate
7.11 Support for Retrospectives
8. Authorizing Players
8.1 Members of the Coordinating Committee
8.2 Decisions by Consensus
8.2.1 Thumb UP = Agree/Support
8.2.2 Thumb Sideways = OK
8.2.3 Thumb Down = Disagree/Block
8.2.4 Silence = sabotage
9. Appendix A:
9.1 Design Mandates
9.1.1 Stuff that we discovered during Chartering re: technical requirements
10. Charter Meeting Notes:
10.1 Meeting 3/28/2009
10.1.1 Visit with Liturgy
Our highest priority is to support our community through continuing creation of opportunities to deliver insight, learning, and networking .
Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
We actively support collaboration within our community.
We embrace the energy of the motivated individuals in our community. We lean towards new initiatives and towards trust in those individuals to support our values while pursuing those initiatives.
The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
Value delivered to the community is the primary measure of our success.
Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
Continuous attention to technical excellence and good design enhances agility.
Simpler is better.
The best outcomes emerge from self-organizing teams.
At regular intervals, we reflect on how to become more effective, then tune and adjust.
10.1.2 Roadmaps from Mar 17 BayAPLN Event
10.1.3 Chartering
Review work to date
Objectives
Refine Boundary Model
10.1.4 Pace of Change
10.1.5 Guidance for spending sponsor money
10.1.6 Subtopic
10.1.7 Issues:
10.1.8 Action Items:
10.1.9 Next Meeting Agenda:
10.2 Meeting 4/14/2009
10.2.1 Objectives
10.2.2 Action Items:
10.3 Meeting 6/6/2009
10.3.1 Participants
III
Ainsley
Paul
Cesar
Tom Schiff
Joanna
David
10.3.2 Affirm Agenda
10.3.3 Test for Done?
10.3.4 Chartering
Vision
Mission
Principles
Objectives
Boundary Exhibits
Committed Resources
Authorizing Players
10.3.5 Road Map
10.3.6 Issues
Mothership Expectations about us
Mothership attendees become APLN Members
Input and participation with the National level?
Understanding expectations about our involvement with the national organization
Our expectations of the mothership
Candidate Principle
We are guided by ongoing assessment of value to participants
A formal membership protocol
Process for embracing (onboarding) new members
Our strategic view of our online presence
Event-Centric measure of value for participants
Task force to design template for event-centric "smile sheet" to be answered by participants
About
Title
BayAPLN Charter
Subject
-
Company
-
Author
-
Version
381
Comments
The Mindjet MindManager 6 default map template.