Download to read offline
Uploaded byGrip QA
How to use GitHub to Predict the Success of your Application
The document discusses leveraging GitHub analytics beyond traditional code metrics to inform business decisions, emphasizing the value of information contained in repositories. It outlines various aspects to analyze, including product details, collaboration metrics, and process artifacts, to improve decision-making regarding project maintenance, team dynamics, and delivery timelines. Ultimately, the document promotes data-driven strategies to enhance project success through insights derived from code, people, and processes.
More Related Content
Similar to How to use GitHub to Predict the Success of your Application
![Matrix and determinant URT [Autosaved].pptx](https://cdn.slidesharecdn.com/ss_thumbnails/matrixanddeterminanturtautosaved-251018190340-9e6a6deb-thumbnail.jpg?width=600ounds&width=560&fit=bounds)
How to use GitHub to Predict the Success of your Application
- 1. How to getmore out of your code than technical metrics GitHub Analytics to Predict the Success of your Application
- 2. Traditional Code Analysis(Tools) Reviews – Internal / External – Pros – Great improvement, learning opportunity – Cons – Time consuming Static Analysis – Analyzing Source Code Without Executing – Pros – Scans entire code base – Cons – Rule based, false positives Focus on Technical Metrics But what is the business impact?
- 3. What else canyou get from your repos that helps you with business decisions? Your repos contain a wealth of information and value, in addition to code storage! • Product • People • Process
- 4. $ curl https://api.github.com/repos/coreos/fleet { "id":13512328, "name": "fleet", "full_name": "coreos/fleet", "owner": { "login": "coreos", "id": 3730757, ... "events_url": "https://api.github.com/users/coreos/events{/privacy}", "received_events_url": "https://api.github.com/users/coreos/received_events", "type": "Organization", "site_admin": false }, ... "collaborators_url": "https://api.github.com/repos/coreos/fleet/collaborators{/collaborator}", "teams_url": "https://api.github.com/repos/coreos/fleet/teams", "hooks_url": "https://api.github.com/repos/coreos/fleet/hooks", "issue_events_url": "https://api.github.com/repos/coreos/fleet/issues/events{/number}", "events_url": "https://api.github.com/repos/coreos/fleet/events", ... "updated_at": "2015-03-04T08:09:16Z", "pushed_at": "2015-02-27T22:09:53Z", ... "size": 11543, "stargazers_count": 1594, "language": "Go", "has_issues": true, ... }, "network_count": 166, "subscribers_count": 122 }
- 5. Product Focus of codereviews & static analysis Beyond Code, you can extract info from your repo: • Total # Lines of code • Change in the # of lines of code over time • Size (roughly, server side disk usage) • Programming Languages Used
- 6. People • Collaborators / Active collaborators/ Contributions • Stars • Followers
- 7. Process • All ofthe push/pull/clone/fork/branch artifacts that we normally associate with Git repos • Issues / Problems • Commits - seeing the history and correlating to milestones • History of events that occurred on the repo
- 8. How will thishelp me? - Rebuild or continue maintenance? - Outsource or in house? - Add team members or downsize? - Specific skills - Personalities - What technologies? - Will I make delivery date? - Will this satisfy my users? - Will I run over budget?
- 9. Success • You canleverage data about code, people and process info to make better decisions • Data driven decisions will help you to consistently meet your business objectives
- 10. Machine Learning, Analytics,Simulation • Deep insight into success factors like resource allocation and sprint planning • Predictions from our AI • Minimize uncertainty Can’t I just do this myself? Could track it all yourself, but w/ Grip you’ll get: • Visual presentation -> improved perception • History -> trends & inflection point • Benchmarks -> compare with other efforts
- 11. Q and A info@grip.qa Followus on twitter: @gripqa
Editor's Notes
- #2 Jan: I can open Dean: Do you want to say something distinguishing this topic from the GitHub Traffic Analytics that they offer, or do you want me to do it when the flow gets down to me.
- #3 Conversation on how code reviews are currently done and the pros and cons of it Dean: focus is on the correctness of your code, not on giving you data to make the best possible decisions on how to meet your business objectives.
- #4 But you can get more out of your code.
- #6 What product info can we get and why is this important? This is mostly the stuff that you’re already familiar with, but a lot of it is much more interesting plotted against time, instead of just looking at the values in a snapshot.
- #7 What people info can we get and why is it important? Who is contributing to your project? Who is the most active? Who is following you. How popular is your repository. Gives you insight into both your customers / users and your team
- #8 What Process information can we get and why is it important?