The Agile Philly User Group has been in existence since 2003-2004. It's a very active user group and was approved as an official affiliate of the Scrum Alliance on April 23, 2014. Agile Philly meetings are free and open to the public - and common sense Security procedures of our hosting companies require attendees to RSVP at our AgilePhilly event webpages - or notify us so we can notify the hosting company. Anyone can attend. Meetings are held twice a month; 1) the second or third Tuesday of every month in the suburbs. Meetings in Center City are sporatic.
AgilePhilly embraces all aspects of Software Development using practices and frameworks such as Lean, Kanban,Scrum, and even Waterfall, with the proper amount of Testing, Team Building, and other areas included in our meetings. The mission of the group is to helping it's members build better software.
Our members have identified themselves as being broadly distributed across the range of experience: ( April 2016)
15 % Expert
15 % Intermediate
15 % Novice
15 % Curious
40 % = 0 = ( joined before question was added to enrollments in Nov 2012 )
This is a volunteer run, non-profit organization which aims to provide a community for individuals involved in agile software development. This group aims to provide an environment where its members can exchange ideas and meet with individuals involved in agile community. The AgilePhilly listserv has all meeting announcements. Discussions throughout the month are encouraged at our AgilePhilly.Slack.com channel.
Our website crossposts events of other Technical User Groups and Vendor Events that we feel our members will appreciate learning about. RSVP's for those other Meetups & events are done on their own websites.
Moderation Policy
To promote the flow of free information, we restrict advertisements for job offers, paid events, surveys, and commercial advertising--these may only appear on our Job Listings and Local Events and Announcements pages.
Moderators are in place not to guarantee high standards (which tend to be subjective) but to prevent low standards (which can usually be expressed more objectively). In that regard, posts should generally be let through unless they are clearly either:
1. Not relevant to the group
2. Not consistent with the publicly stated standards or guidelines for the group (listed above)
Find out More
Book Recommendations
Please follow the link for book recommendations
Comment
© 2019 Created by Ravindar Gujral.
Powered by
You need to be a member of Agile Philly to add comments!
Join Agile Philly