Agile For Open Source
-Open Source development depends a lot on community, their feedback,
their suggestions, their reviews and their enthusiasm.
-For an open source development project, the community itself is the first customer.
-Product release for the community provides a good starting point to assess
how the product will be accepted in the market.
-This is very beneficial as it gives the software development team an edge over
its competitors as it gets the pulse of the customer
-In many ways the open source development has the culture similar to that of
an Agile enterprise.
-The principles guiding open source development are similar to Agile principles
-The session presents views on above as well as how open source development projects employ agile for
both the community development and for their own licensed version of the software.
Outline/structure of the Session
-A word about open source development
-upstream and downstream development
How Agile applies to open source
-Engagement between community and developers
-role splitting and clarity
-quality of delivered software
-agile eco-system in open source development
-Agile vis-a-vis Open Source:
- how open source uses agile methodology?
- what new open source development offers to Agile
-engagement between product teams and user community
-impact on community software
-impact on quality and delivery of licensed software
-how does the user community benefit from this enagagement
-ROI for customers: how do users/customers benefit by using open source software
-Support: how does support mechanism work?
-Outlook: Why open source is catching up faster?
schedule Submitted 4 years ago
People who liked this proposal, also liked:
Johannes Brodwall / Niruka Ruhunage - Remote Pair Programming
Can you maintain agile engineering practices with a distributed team?
Johannes is the Oslo based Chief Scientist for the Sri Lanka based company Exilesoft. In order to promote agile engineering practices, he uses remote pair programming to connect with teams halfway across the world.
In this talk, we will go through a practical approach for remote pair programming adopted for high-latency situations. We will demonstrate remote pair programming with a live example and we will discuss the advantages and usages of the approach. We will also cover the practical parts of remote pair programming, such as tools and setup.
After seeing this talk, the audience should be able to remotely pair with members of their distributed team. They will also get a lot of tips on how to use pair programming effectively in both local and remote settings.
Nikhil Joshi - Build - Measure - Learn : Without spending a fortuneNikhil JoshiAgile Coach - Program ManagementPubMatic
schedule 4 years agoSold Out!
At times we have great product ideas but the biggest barrier to entry lies in answering few questions such as:
- How do I define and validate Problem hypothesis, Solution hypothesis and Underlying assumptions?
- How do I quickly setup a platform for people to register their interest?
- What will keep the potential customers engaged, excited until the first release (or beta) is out?
- How do I get feedback from the early adopters?
- And eventually when I have answers to some of these questions, how do I make a decision to persevere or pivot?
If you've faced a challenge while answering any of these questions while building/validating your product idea, this session is for you. We'll look at tools and techniques to validate the product hypothesis early-on without spending months or fortunes. We'll also look at a case study to highlight how some of these tools, techniques helped us validate our product idea.
Sharad Julka - Performance Appraisal For An Agile TeamSharad JulkaAgile Transformation ConsultantXebia IT Architects India Private Limited
schedule 4 years agoSold Out!
Our affection with Bell Curve has been for long.
-It is (one of) the most "natural" scheme(s) of evaluating
and judging performance of an employee in an enterprise.
-It provides a fair view of the employee performance level
of all employees to the management.
-However, in an Agile world, where everyone in the team is expected
to exercise equal responsibility and accountability,
does Bell Curve PMS act as a hindrance?
-Does it motivate a few and demotivate others?
-Is it the right tool to use?
-Is it used in the right manner?
-Does it affect the performance of a highly productive and efficient team?
-Do we have a choice?
Savita Pahuja - Battlefield AgilitySavita PahujaAgile ConsultantPalo-IT
schedule 4 years agoSold Out!
Battlefield Agility® is a quest to make our deliveries better, more collaborative, faster and effective. It relies on age old principle from the Army to provide a holistic view of the problem landscape which a project team needs to solve and be able to succeed in this, through small collaborative groups working in coordination to achieve the bigger goals.
Battlefield Agility® derives from the Agile manifesto and principles and adds to it the key ingredient of individual wisdom to create a plan for a team which will help it succeed in successful deliveries . This is a goal based approach to increase MVP and ROI.
The purpose of this method is to make team members more focused about their work, equal distribution of work in the team and increase productivity.
Battlefield Agility enumerates the mechanisms of planning, better field view to all team members, ease of multitasking, reduce task switching.
Key benefits of Battlefield Agility®
- A focused approach to software development as development proceeds through small battles to be won
- Reduced multitasking and better efficiency of team members
- Faster deliveries as the work is divided to right sized battles to be won
- Parallel efforts by team members ensure the time to market is significantly lesser
- Less process overhead as the collaboration is real time and more time is spent on the ground than on meetings
- Small teams ensure close camaraderie and collaboration among team member
- The team can even work on disparate work areas ( if required) in order to make best us of their expertise