Skip to main content

Home/ SoftwareEngineering/ Group items matching "planning" in title, tags, annotations or url

Group items matching
in title, tags, annotations or url

Sort By: Relevance | Date Filter: All | Bookmarks | Topics Simple Middle
kuni katsuya

Top 10 Lessons Learned From 10 Years in Agile | Agile Zone - 0 views

  • Top 10 Lessons Learned From 10 Years in Agile
  • 1.  Simplicity is Sophistication.  
  • 2.  Define your Rhythm.  
  • ...18 more annotations...
  • start cutting down on wasted meeting time
  • 3. Agile is Fundamentally About Discipline.  
  • areas of planning, unit testing, test driven development, continuous integration, and test automation.
  • 4.  Software is Hard to Scale, Agile is Not.  
  • Focus on business goals
  • 5.  Think of the Big Picture.   
  • success requires a
  • consideration of the system as a whole
  • before making changes to its parts, or else the change will likely be fraught with risk.
  • 6.  Lose the Religion  
  • adapt agile to your need.
  • 7. Continuous Focus on Business Value.
  • get caught in the weeds of a technical story's delivery and velocity at the expense of overall business value, company and project goals
  • 8. Agile - It's Not Just For Software Anymore.
  • 9. Continuous Planning. 
  • Plan on a daily basis if possible
  • Keep your focus on maximizing value
  • 10.  Doing agile and being agile aren’t the same.
kuni katsuya

OpenTravel Forum - 0 views

  • OpenTravel Codes in Schema
  • If you are an inventory supplier, you would reference a rate plan code known to your system, such as “DELUXE” or “Deluxe Room”
  • RoomTypeCode
  • ...2 more annotations...
  • assigned by the inventory supplier
  • If you are not a supplier, you need to work with your supplier trading partners to get a list of room types supported by their CRS (central reservation system) or PMS (property management system.)
kuni katsuya

Start multiple sprints simultaneously - Atlassian Answers - 0 views

  • one 'Planning' Rapid Board that selects all of the issues you wish to work
    • kuni katsuya
       
      overall product backlog
  • two other 'Work' Rapid Boards, one for each team
    • kuni katsuya
       
      scrum team-specific rapid boards
  • "project = x and component = TeamA"
  • ...4 more annotations...
  • "project = x and component = TeamB"
  • parallel sprints labs feature
  • Unfortunately this will make the velocity chart less usable because velocity is heavily based on the estimations of an individual team
  • scenario of having multiple JIRA projects containing work items to be picked up by / distributed to multiple scrum teams
    • kuni katsuya
       
      exactly our scenario!
kuni katsuya

NetBeans Release Roadmap - 0 views

  • NetBeans Release Roadmap
  • defines what the NetBeans open source project strives to achieve, and our plans to reach these goals
  • graphical representation of the NetBeans Release Roadmap:
kuni katsuya

CDIFeatures72 - NetBeans Wiki - 1 views

  • CDIFeatures72
  • CDI Enhancements Functional Specification
  • pre-planning purposes ONLY
1 - 13 of 13
Showing 20 items per page