0 2013 Roadmap Brent Halliburton 215.439.0163.

Slides:



Advertisements
Similar presentations
Object Oriented Analysis And Design-IT0207 iiI Semester
Advertisements

Building the Balanced Scorecard
Essential Lifestyle Planning Facilitator Training - Day 2
Top 10 User Mistakes with Static Analysis Sate IV March 2012.
Comparative Study of MOPAN and EvalNet Approaches to Assessing Multilateral Organizations’ Development Effectiveness James Melanson Director, Development.
Business Plan What? Overview & reflection of the business and its owner – thorough explanation of a business idea and how it will be executed Story of.
How to… Create an Annotated Bibliography
PROJECT RISK MANAGEMENT
Agile Planning Dealing with Reality. Reality Basic agile principle – don’t expect static plans to hold, be flexible and expect changes.
Agile development By Sam Chamberlain. First a bit of history..
Important concepts in software engineering The tools to make it easy to apply common sense!
Software Quality Engineering Roadmap
Software Quality Metrics
Chapter 5: Project Scope Management
Iterative development and The Unified process
Managing a Project Using an Agile Approach and the PMBOK® Guide
SEG4911 – Projet génie logiciel en fin d’études / Software Engineering Capstone Project Thoughts about Agile Design and Release Management Timothy C. Lethbridge.
Chapter 10: Business Plan1 Copyright 2002 Prentice Hall Publishing Company Crafting a Winning Business Plan.
The Project AH Computing. Functional Requirements  What the product must do!  Examples attractive welcome screen all options available as clickable.
Maths Counts Insights into Lesson Study 1. Tim Page and Joanne McBreen Transition Year or Senior Cycle Introducing Tolerance and Error (Leaving cert.
Version Control with git. Version Control Version control is a system that records changes to a file or set of files over time so that you can recall.
Information Security Governance 25 th June 2007 Gordon Micallef Vice President – ISACA MALTA CHAPTER.
McGraw-Hill/Irwin Copyright © 2008 by The McGraw-Hill Companies, Inc. All rights reserved. Reaching Goals: Plans and Controls Today’s smart supervisor.
Patrick Mallon Creating change through Collaboration & Partnership 22 May 2007.
Developing a Library Marketing Plan, Part 2 Implementing the Plan Mark E. Ibach Marketing & PR Coordinator South Central Library System.
Project Tracking. Questions... Why should we track a project that is underway? What aspects of a project need tracking?
Chapter 5: Project Scope Management Information Technology Project Management.
IT Project Management, Third Edition Chapter 5 1 Chapter 2: Project Scope Management.
This material is approved for public release. Distribution is limited by the Software Engineering Institute to attendees. Sponsored by the U.S. Department.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 7: Focusing on Users and Their Tasks.
IT Project Management, Third Edition Chapter 6 1 Chapter 3: Project Time Management.
Developing a Teaching Portfolio for the Job Search Graduate Student Center University of Pennsylvania April 19, 2007 Kathryn K. McMahon Department of Romance.
Goals of this Session: Brief discussion on core and web.. What is your mandate? Where are you at? Our “notes” Discuss satisfaction, issues, features still.
XP Explained Chapters 7-9. Primary Practices  Sit together Ideal Resistance Multi-site  Whole Team All the necessary skills in a single management structure.
© 2001 Change Function Ltd USER ACCEPTANCE TESTING Is user acceptance testing of technology and / or processes a task within the project? If ‘Yes’: Will.
INFORMATION X INFO415: Systems Analysis Systems Analysis Project Deliverable 1 Project Statement of Work Outline.
Executive Focus 2007 Take Control of Your Career Tools to Jumpstart Your Stalling Career Executive Focus 2007.
10 Aug 2010 ECE/BENG-492 SENIOR ADVANCED DESIGN PROJECT Meeting #7.
STEP 4 Manage Delivery. Role of Project Manager At this stage, you as a project manager should clearly understand why you are doing this project. Also.
Project Portfolio Management Business Priorities Presentation.
Software from Requirements Brent Haines April 12, 2007 Why Methodology Doesn’t Really Matter.
Chapter 7 The Practices: dX. 2 Outline Iterative Development Iterative Development Planning Planning Organizing the Iterations into Management Phases.
Mtivity Client Support System Quick start guide. Mtivity Client Support System We are very pleased to announce the launch of a new Client Support System.
Planning in Organizations Why supervisors and managers plan: Knowing what the organization is trying to accomplish helps them set priorities and make decisions.
 A plan of attack for your games content  Or (more specifically)  A detailed description of all games mechanics, objects, characters, stats, ect… that.
1 Software Quality Engineering. 2 Quality Management Models –Tools for helping to monitor and manage the quality of software when it is under development.
NEGOTIATION SKILLS Suwarn Kumar Singh Sudip Tripathee.
Measuring Development Impact: Beyond Satisfaction Deloitte Services LP Janelle HughesJohn DeVille Development LeaderTalent Analytics Manager.
Cruise Training Introduction of Continuous Integration.
A business plan is an essential roadmap for business success. This living document generally projects 3-5 years ahead and outlines the route a company.
The Project Management Process Groups
MAINTAINING PRODUCTIVITY 7 KEYS FOR SETTING REALISTIC GOALS.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
Baby Steps to Agility How to Grow Into Agile. A little about me A little about Agile Growing into Agile Questions Goals.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Agile Project Management
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Agile Scrum Management
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
September 20, 2017 Agile Techniques Workshop Susan Futey
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Chapter 3: The Project Management Process Groups: A Case Study
Johanna Rothman Know What “Done” Means Chapter 11
Introduction If you have got a call for an Agile testing interview, then congratulations are in order. You may be feeling nervous, but it sure to be felt.
The business plan Mr Kuhn.
CPD made clear.
Software Design & Production Methodologies
Driving Successful Projects
Presentation transcript:

Roadmap Brent Halliburton

1 First Principles Cogmap is the tool people use for building, maintaining and sharing organization charts online The goal is data accumulation and a sustainable revenue stream with minimal effort First Principles - Clearly explain why your product exists and your approach to running it. This could be a mission statement, tenets, or principles. The important thing is that you believe in them, and by pinning them at the top of every roadmap it will be clear if what follows in the roadmap doesn't match your principles. For Quora, a couple principles might be, "We help the world get their questions answered now, and we create a lasting resource for others who may have the same question in the future. We focus on getting high quality questions and answers, not the most questions and answers."

2 Goals for 2013 Grow page views to 5m per month Grow contributed charts to 10,000 per month Goals & Progress Against Goals - If the roadmap is new, lay out your (numeric) goals. Explain what the metrics are, what time period the goal is set on, and what the starting and ending values are. If the roadmap is an update, state (numerically) how you are doing vs. plan for each goal. For each goal, give some context and explain what has happened in the time since the last roadmap update. State whether you are on track to meet the goal, and if not, what you are doing to get on track.

3 Recent Updates Gave private mappers ability to manage ACLs more easily in response to user requests – decreased support time by 50% Force users to add a comment when they edit and save a map to create more historical reference data Recent Updates - What's been going on recently with the product? What has been delivered since the last roadmap update? Explain what's gone well, what hasn't, and what you've learned. Don't just say a project was a win, show it numerically. If you don't have a clear metric that shows it was a win, try to demonstrate it in other ways (e.g. by comparing to a benchmark or including some sample user feedback). Many people are shocked at what actually has gotten done.

4 Q1 Themes Refresh UI for 2013 – UI has not been improved in several years Bug fixes – Code has not been edited in two years, backlog of bugs is significant, lay the framework for new features in second half Themes (near-term) - What are you going to be focusing on between now and the next roadmap update (e.g. next quarter)? Don't just list individual projects, list the important themes, and explain why the themes are important. The reader should understand why you picked each theme, and why you prioritized it above other ones. Potential themes for Quora might be, "Increasing question volume", "Automating spam prevention and detection", or "Moderation tool scaling". It's okay to list individual projects that will be key in supporting each theme, but don't fall into the trap of just listing projects. You would like to live in a world where you commit to themes on a quarterly basis and dont do non- theme things, but that has rarely been practical for me.

5 Long Term Themes Introduce monetization schemes Improve ability to scale large maps and performance Themes (long-term) - What are the most important themes over the next year? These are similar to the near-term themes above, and possibly a continuation, but over a longer time horizon. The near or long term themes should not be comprehensive and cover everything your team is working on, but they should cover the significant pieces, and roughly line up with how you are allocating your team's resources. Historically, my long-term themes tend to be moremeta and encompass my short term themes. Short term themes may relate to a specific aspect of product adoption. Long term themes may speak to the nature of product adoption.

6 Cogmap 2013 Roadmap Q1Q2Q3Q4 Public Maps Improve layout speed Improve outbound updates Allow users to delete maps Improve blog formatting Improve admin functions for bad addresses Integrate sunnytrail Private Maps Allow users to change map state Individual Projects - List each project you plan to deliver throughout the year with a brief description, a size estimate, which theme it corresponds to, and when you expect to deliver it. Most organizations expect the document to get sparser as you look further into the future, reserving increasing amounts of capacity forsurprises. Rather than tie it directly to themes or put out size estimates, people tend to want to know when it will ship, so I present a table like this organized by product.

7 Out of Scope for 2013 Monetization Viral marketing strategies This is my addition to Ian McAllisters work. I think it is worth it, frequently, to tell people what you are not doing.