Friday Feb 05, 2016

OUM Key Work Products

Wondering about which tasks and work products are essential for your project? A good resource provided by OUM is a list of key work products for each phase of Implement to assist you in planning, estimating and delivering projects. A key work product is a work product that represents the culmination or end result of work effort that contributes to the achievement of milestone objectives for a phase.

Key work products may be considered as candidate deliverables. Not every key work product is created for every project and most likely a project would not be completed by only completing key work products. Additional work products may be required as prerequisites for completing key work products. For example, the Reviewed Use Case Model (RA.180) is a key work product. Both the Use Case Model (RA.023) and the Use Case Specifications (RA.024) contribute to this work product and therefore, would need to be completed. In addition, the unique characteristics of each particular project will necessitate completing additional work products.

For the most part, OUM recommends these key work products for all project types. However, there are some work products that become key depending on the specific project requirements. In this case, there is guidance provided in the "Usage Criteria" column of the list.

You can locate the link to the list of key work product at the top of the Implement views (except Cloud Application Services) and the Manage view under the "Method Resources" heading.  Check it out the next time you need to build up from the essential work products for your project.

Monday Oct 26, 2015

Access to the Oracle Unified Method (OUM) for Oracle Customers and Partners

This blog entry contains the process and navigation steps for Oracle customers and partners who wish to access OUM, including the Cloud Application Services Approach.

Oracle Customers

The OUM Customer Program allows customers to obtain copies of the method for their internal use – including guidelines, templates, and tailored work breakdown structure in one of two ways:

  • OUM Customer Program – No-Cost Option:
    Customers, who have a signed contract with Oracle for a consulting engagement of two weeks or longer meeting some additional minimum criteria, are permitted to download the current release of OUM for their perpetual use. They may also obtain subsequent releases published during a renewable, three year access period.
  • OUM Customer Program – Purchase Option:
    Customers who do not qualify for the free option, and who do not wish to engage Oracle consultants, can opt to purchase the OUM Method Pack. The price for an unlimited, perpetual license is 16,000 USD. This allows the customer to distribute OUM within their enterprise for internal use. At the time of purchase, customers are also able to purchase an initial three year subscription for 15% of the purchase price or 2,400 USD. After the initial subscription period, the subscription may be renewed annually for 2,400 USD. This subscription allows them to download updates to OUM during the subscription period.

Contact your local Oracle Sales Representative about enrolling in the OUM Customer Program.

Oracle PartnerNetwork (OPN) Diamond, Platinum, and Gold Partners

OPN Diamond, Platinum, and Gold Partners are able to access the OUM method pack, training courses, and collateral from the OPN Portal at no additional cost:

  • Go to the OPN Portal at partner.oracle.com.
  • Select "Sign In / Register for Account".
  • Sign In.
  • From the Product Resources section, select "Applications".
  • From the Applications page, locate and select the "Oracle Unified Method" link.
  • From the Oracle Unified Method Knowledge Zone, locate the "I want to:" section.
  • From the I want to: section, locate and select "Implement Solutions".
  • From the Implement Solution page, locate the "Best Practices" section.
  • Locate and select the "Download Oracle Unified Method (OUM)" link.

Saturday Sep 26, 2015

MoSCoW Grooming

I was recently asked whether the MoSCoW List (list of known business requirements classified by the first letter of: Must, Should, Could or Won’t) is a static document. The short answer to this is No – the MoSCoW List is intended to be evolved, some use the term “groomed”, as the project progresses. MoSCoW grooming is a good process to indicate what is inside or outside scope for the project as a whole, as well as for a given phase and/or iteration.

The MoSCoW List is initially created in the Inception phase, but this does not mean that you do not continue prioritizing further into the project. In fact, you groom the MoSCoW list using prioritization techniques throughout the project. You indicate priorities for each use case defined. However, all the detailed requirements should be related to the requirements given in the MoSCoW List.

When the project moves into the Elaboration phase, you also use these priorities to determine on which use cases to start. The Should Haves are not as important as the Must Haves and may not even be considered during the Elaboration phase.

This classification makes our understanding explicit as soon as project progress changes. New functionality can appear and be prioritized as necessary while other initial requirements turn out to be less important.

The ultimate MoSCoW List should be a mutually exclusive and completely exhaustive set of functional and supplemental requirements. Each requirement should relate to at least one of the objectives stated in the Business and System Objectives (RD.001).  

Do you have any tips for MoSCoW grooming?  Please share them in the comments.

Saturday Aug 15, 2015

Can OUM Support Agile Development?

We are asked from time-to-time whether OUM is considered to be "agile".  There is not really a short answer to this question so this blog entry addresses the key characteristics of OUM that make it an agile method.

First of all, OUM is not "waterfall", but instead promotes an iterative and incremental approach to development and deployment of information systems. Any of the tasks within OUM may be iterated. Tasks may be iterated to increase quality of the work products to a desired level, to add sufficient level of detail, or to refine and expand the work products on the basis of user feedback.

In addition to having an agile iterative and incremental development approach, OUM also:

Is flexible and scalable – OUM is designed to support a broad range of project types. As such, it must be flexible and scalable. The appropriate point of balance for a given project will vary based on a number of project risk and scale factors. The method has been developed with the intent that the approach for a given project be “built up” from a core set of activities to implement an appropriate level of discipline, rather than tailored down.

Allows for frequent customer interaction and feedback – OUM encourages regular sessions with stakeholders to review and confirm priorities, and ensure the project continues to meet the overall objectives. Through several prototyping and testing tasks, business stakeholders are given the opportunity to review the development work completed to that point, and provide feedback in time to catch missed requirements and/or possible errors.

Employs a layered planning approach – OUM recognizes that plans need to be scalable for different project sizes and complexity, and contain the right level of detail for the current planning horizon. The layered approach to planning an OUM project allows project teams to take an agile approach to their immediate project tasks, while keeping a focus on the major milestones, controls, and objectives of the project.

Encourages the use of an empowered team – OUM encourages cross-functional and technical team training and knowledge sharing. In addition, the use of OUM’s common language and visual models (use cases and business process models) throughout the project helps ensure the development team and other project stakeholders are on the same page, which promotes team communication and collaborative decision making.

Integrates testing throughout the development lifecycle – Testing in OUM starts early in the project, and developed components are integrated and tested as an integrated set as soon as possible. This allows for early discovery of errors that eventually reduces the risk of project delays that often are caused by heightened error detection at the end of the project.

Promotes an architecture-centric approach –  People will sometimes question whether spending time and energy on architecture is compatible with an agile approach. The answer is that a robust architecture is crucial to the project’s success since it is the blueprint upon which requirements are transformed into a working system. Poor architecture decisions can result in software that is not stable, is unable to support business requirements, could require substantial re-work, may not accommodate future development, or could even prevent the application from working properly in a production environment. Nothing about poor architecture sounds too agile, does it?

I could go on for a while about OUM’s agile underpinnings; the bottom line is that OUM supports all kinds of projects – from the very lean and adaptable, to those that require more rigor and discipline. If you want to find out more about how OUM can be applied in an agile manner, check out the Scrum View which brings together in once place all of the OUM tasks associated with managing a Scrum project as well as all the OUM supplemental content.  

So the answer then is a resounding "yes" (which I suppose is actually the short answer to the question posed in the title of this blog) - OUM is indeed considered to be "agile" and can support agile development.

Tuesday Mar 31, 2015

OUM Spotlight - Keeping Stakeholders Engaged

Congratulations! Your new project is off to a great start and all of the stakeholders came away from the project kickoff meeting informed and enthused. Now you may be wondering how do I keep these very busy stakeholders informed and enthused as the project moves along?  One technique used by successful OUM projects is to communicate the project's status to all of the stakeholders upon the completion of the phase end milestones, and take this milestone opportunity to inform these stakeholders of upcoming critical events and decisions. This practice connects stakeholders into the flow of the project, thus promoting collaborative working relationships and reducing risk by continually demonstrating project progress and driving decision making.

Another widely used technique is to demonstrate configurations and extensions to ambassador users at key points in the development cycle. This gives ambassador users the ability to conduct testing throughout the project, which facilitates a smooth UAT and mitigates any potential surprises at the end of the project.

Have any tips and techniques on keeping stakeholders engaged on your projects?  Please share in the comments.

Saturday Jan 17, 2015

Oracle Unified Method (OUM) 6.3

ORACLE® UNIFIED METHOD RELEASE 6.3

Oracle’s Full Lifecycle Method
for Deploying Oracle-Based Business Solutions

About | Release | Access | Previous Announcements

About

Oracle is evolving the Oracle® Unified Method (OUM) to achieve the vision of supporting the entire Enterprise IT Lifecycle, including support for the successful implementation of every Oracle product. OUM replaces Legacy Methods, such as AIM Advantage, AIM for Business Flows, EMM Advantage, PeopleSoft's Compass, and Siebel's Results Roadmap.

OUM provides an implementation approach that is rapid, broadly adaptive, and business-focused. OUM includes a comprehensive project and program management framework and materials to support Oracle's growing focus on enterprise-level IT strategy, architecture, and governance.

Release

OUM release 6.3 provides support for Application Implementation, Cloud Application Services Implementation, and Software Upgrade projects as well as the complete range of technology projects including Business Intelligence (BI), Enterprise Security, WebCenter, Service-Oriented Architecture (SOA), Application Integration Architecture (AIA), Business Process Management (BPM), Enterprise Integration, and Custom Software. Detailed techniques and tool guidance are provided, including a supplemental guide related to Oracle Tutor and UPK.

This release features:

  • OUM Cloud Application Services Implementation Approach to the Application Implementation Method (AIM) Mapping
  • OUM Project Workplan, available in Primavera format, includes Tasks from OUM's Manage and Implement Focus Area
  • RACI - Responsibility Assignment Technique, Template, and Examples
  • Document Application Configuration Changes [MC.055] Task and Template
  • Top-Level Business Capabilities Diagram [EA.040] Template and Capability Analysis Results Presentation [EA.040] Template
  • Maturity Analysis Presentation [ER.015] Template
  • Access to Oracle Managed Cloud Services (OMCS) Implementation Training to Aid Project Managers Interfacing with OMCS
  • Updated/Enhanced:
    • OUM Cloud Application Services Implementation Approach Guidance and Templates updated based on Field Input
    • Template Functionality and Format revised based on Field Requests, specifically removed Oracle Method Template Engine (OMTE) and converted to Microsoft Office 2007 format
    • Template User's Guide revised to address Template Functionality and Format revisions such as Changing Variables, Updating Field Codes, and Removing Yellow Notes
    • OUM Microsoft Project Workplan updated to include Document Application Configuration Changes [MC.055] Task and Activity Filter, converted to MS Project 2007 format, and removed reliance on
    • OUM-specific Microsoft Project Template [Global.mpt] *OUM Microsoft Project Workplan User's Guide updated to reflect changes to OUM Microsoft Project Workplan
    • Project Management Framework supporting Tasks and Templates updated based on Subject Matter Experts Feedback
  • For a comprehensive list of features and enhancements, refer to the What's New page of the Method Pack

Upcoming releases will provide expanded support for Oracle's Enterprise Application suites including product-suite specific materials and guidance for tailoring OUM to support various engagement types.

Access

Oracle Customers

The OUM Customer Program allows customers to obtain copies of the method for their internal use – including guidelines, templates, and tailored work breakdown structure in one of two ways:

  • OUM Customer Program – No-Cost Option:
    Customers, who have a signed contract with Oracle for a consulting engagement of two weeks or longer meeting some additional minimum criteria, are permitted to download the current release of OUM for their perpetual use. They may also obtain subsequent releases published during a renewable, three year access period.
  • OUM Customer Program – Purchase Option:
    Customers who do not qualify for the free option, and who do not wish to engage Oracle consultants, can opt to purchase the OUM Method Pack. The price for an unlimited, perpetual license is 16,000 USD. This allows the customer to distribute OUM within their enterprise for internal use. At the time of purchase, customers are also able to purchase an initial three year subscription for 15% of the purchase price or 2,400 USD. After the initial subscription period, the subscription may be renewed annually for 2,400 USD. This subscription allows them to download updates to OUM during the subscription period.

Contact your local Oracle Sales Representative about enrolling in the OUM Customer Program.

Oracle PartnerNetwork (OPN) Diamond, Platinum, and Gold Partners

OPN Diamond, Platinum, and Gold Partners are able to access the OUM method pack, training courses, and collateral from the OPN Portal at no additional cost:

  • Go to the OPN Portal at partner.oracle.com.
  • Select "Sign In / Register for Account".
  • Sign In.
  • From the Product Resources section, select "Applications".
  • From the Applications page, locate and select the "Oracle Unified Method" link.
  • From the Oracle Unified Method Knowledge Zone, locate the "I want to:" section.
  • From the I want to: section, locate and select "Implement Solutions".
  • From the Implement Solution page, locate the "Best Practices" section.
  • Locate and select the "Download Oracle Unified Method (OUM)" link.

Previous Announcements

Wednesday Oct 22, 2014

Join the OUM User Community on LinkedIn and Twitter

As a member of the Oracle Unified Method (OUM) User Community you are able to share your knowledge and insight and benefit from the advice and experience of the global OUM user community.

You can quickly locate information; find other knowledgeable users; and provide answers, feedback, and experiences.

The OUM Group on LinkedIn and OUM on Twitter help to facilitate communications among members of the OUM Professional Community.

If you haven't already, we encourage you to join now and get involved!

Saturday Oct 11, 2014

Questions to Ask When Organizing Your OUM Workplan

So you’ve read all the tips and blogs about how to tailor OUM for your project and you’ve figured out what tasks you need. Now you have to put them into a workplan. What do you do? Do you use the traditional activity wbs structure highlighted in the method or do you need something else? The possibilities are endless. Think about how you implement your projects now. Think about what works now and what doesn’t. Consider this blog my Questions to Ask When Organizing Your OUM Workplan.

  1. Does the traditional OUM activity-work-breakdown structure fit my project?
  2. Does your project involve more than one custom-off-the-shelf (COTS) product? If so, maybe you want to do this work in partitions. Determine which activities/tasks should be duplicated into each partition.
  3. Do you need to consider copying sections of your workplan and putting them into iterations for accommodating use case packages?
  4. Can certain processes be run as “mini projects?” Some processes can almost be run as a side project on their own, for example, Technical Architecture (TA), Performance Management (PT), Documentation (DO), Training (TR), and Organizational Change Management (OCM). If so, it may make more sense to group and track these tasks under a process/activity heading and not space them out into the various phases.
  5. Do you use one workplan or a master workplan with individual plans that report or roll up into the master? This might work if you have Team Leaders that manage specific pieces of work. Use a placeholder activity/task in the master workplan and the detail can be managed in a sub workplan.

The bottom line is, be creative. Build your workplan(s) to suit your project. As you start another project, don’t be afraid to change something that isn’t working. Finally, share your workplans and experiences.

Wednesday Sep 24, 2014

Checklists Are Leading Edge

I recently ran across this blog on The Power of Checklists by Ivar Jacobson. In it he describes the value of using checklists on software projects since they: “keep software projects on track, and help maximize the delivery of value, and minimize the risk of project failure.” OUM practitioners know this since the method contains checklists in many places - templates, phase overviews, activities, tasks, etc.  In fact, the WBS itself could be considered a checklist since the activities and tasks are merely “placeholders for work.”

The OUM checklists which I find particularly valuable are the Activity Checklists found in each of the Lifecycle Milestone Summaries. These checklists are designed to assist you with the determining “completeness” of the project at that point. They also contain lists of key decisions and common risks that should be addressed during that particular phase of the project – kind of like a “you are here” checkpoint for the project's progress.

I think Ivar would agree with me about the value of the OUM Activity Checklists since he is a fan of Barry Boehm’s standard project milestones. You can read more about Barry Boehm’s standard project milestones in his seminal work – “Anchoring the Software Process” [Barry Boehm, November 1995].

Which OUM checklists do you find to be of the most value? Please share your opinion in the comments.

Wednesday Sep 03, 2014

Oracle OpenWorld and OUM

Oracle Unified Method (OUM) Enthusiasts:

I am excited to announce that I will be attending Oracle OpenWorld (OOW) from September 29th to October 2nd  representing Oracle's Global Method Group and the Oracle Unified Method (OUM).  If you are planning to attend, and are interested in discussing OUM, then send me a message on LinkedIn and we can arrange a convenient time to meet face-to-face.

I would love to discuss your experience using OUM and/or answer OUM-related questions.  

Hope to see you there!

Linda Lowitz

Wednesday Aug 06, 2014

Guard Against the Multitasking Brain Drain with OUM

Most people are aware of the perils of multitasking – it is bad for productivity, increases the possibility of distractions, and basically creates a mental traffic jam. It not only wreaks havoc in everyday life but also causes major problems on projects. If you look at OUM you might be thinking, “Hey wait! Isn’t the fact that OUM’s processes run in parallel and that it takes a cross-functional approach really multitasking?” My response to you (to borrow from Lee Corso) is, “Not So Fast, My Friend!”

The answer is directly related to magnitude of the shifts in focus. We know that those broad deviations in requirements and technology require more adjustment and time to switch gears. Human brains are okay with shifting tasks within reasonable limits. On a well managed OUM project, the team is focused on a discrete, prioritized list of functionality and technology. Only a limited number of logically grouped requirements are being worked at a time in order to achieve specific milestones. This means there is a narrow span of scope being addressed at any point in the project, even there may be a wide range of tasks and processes in play.

Extensive detours such as new requirements and major shifts in priorities are the catalysts that can lose the project to the nemesis known as multitasking. Fortunately, OUM has a number of tools to keep the focus and guard against the multitasking brain drain – timeboxes, MoSCoW lists, use cases, and system context diagrams...just to name a few.

What are some tools you use to keep your projects focused? Please share with us in the comments section below!

Wednesday Jul 23, 2014

OUM Training Program: Project Workplan Overview

Course Description | Access | Training Program

 
Course Description

The Oracle® Unified Method (OUM) Project Workplan Overview training consists of a collection of short, independent modules that provide information about and a demonstration of key features of the OUM Project Workplan.

The OUM Project Workplan, available in Microsoft Project format, includes tasks from OUM's Manage and Implement Focus Areas and can be: executed at the activity-level or task-level, tailored easily for most OUM Implement views, and updated with effort from the OUM Estimating Model.

  • Audience: Bid Management, Risk Management, Quality Management, Project Management, Program Management, Solution Architects, Team Leads, Delivery Consultants
  • Prerequisites: None
  • Delivery: This training can be taken on-line or downloaded and taken off-line at your leisure
  • Time Required: The duration of the modules ranges from 3 to 40 minutes

Access

Oracle Customers
Customers enrolled in the OUM Customer Program are able to access the training courses from the Oracle Learning Library.

  • Go to the OUM page on the Oracle Learning Library.
  • Select the "OUM Project Management Skills" tab. 


Learn about the OUM Customer Program.

Oracle PartnerNetwork (OPN) Diamond, Platinum, and Gold Partners
OPN Diamond, Platinum, and Gold Partners are able to access the training courses from the OPN Portal.

  • Go to the OPN Portal at partner.oracle.com.
  • Select "Sign In / Register for Account".
  • Sign In.
  • From the Product Resources section, select "Applications".
  • From the Applications page, locate and select the "Oracle Unified Method" link.
  • From the Oracle Unified Method Knowledge Zone, locate the "I want to:" section.
  • From the I want to: section, locate and select "Implement Solutions".
  • From the Implement Solution page, locate the "Best Practices" section.
  • Locate and select the "Download Oracle Unified Method (OUM)" link.
  • Expand the "Training " section.
  • Select the "OUM Training Program" link.
  • Expand the "Level 2" section.
  • Go to the "Level 2 - OUM Project Workplan Overview" sub-section.

Training Program

The Oracle® Unified Method (OUM) Training Program helps to ensure that individuals in delivery and management roles have the level of knowledge about OUM that is required for them to competently perform their job.

The Program consists of four levels of training:

  • Level 1 – Overview and Awareness
  • Level 2 – Focus Area Overviews for Manage, Envision, Implement
  • Level 2 – Cloud Application Services Implementation Approach Overview
  • Level 2 – Use Case Overview
  • Level 3 – Gathering Requirements using OUM
  • Level 4D – Discipline-specific Delivery Readiness

Levels 1, 2, and 4 are online, self-service courses. Level 3 is a two-day, instructor-led course available for a fee. 

Monday Jul 14, 2014

Eleven Questions to Ask When Tailoring OUM for Your Project

I’ve posted several blogs in the past on tailoring OUM. Here’s one more. As you can see from the title, I call this one Eleven Questions to Ask When Tailoring OUM for Your Project. 

Start with the Core Workflow and adjust it based on the following questions.

  1. Do you need additional Business Requirements (RD) and Requirements Analysis (RA) tasks?  If so, add them.
  2. Are you implementing a custom-off-the-shelf (COTS) product?  If yes, review the Mapping and Configuration (MC) process and add any tasks not already included in the Core Workflow.  If no, remove the Configuration Sub-Flow tasks.
  3. Is there custom work?  If yes, add additional Analysis (AN), Design (DS), Implementation (IM) and Testing (TE) tasks, as appropriate.  If no, you may be able to remove the tasks in the Custom Development Sub-Flow.
  4. What are the Technical Architecture (TA) requirements?  Add TA tasks as appropriate.
  5. Will there be any data conversion?  Add any Data Acquisition and Conversion (CV) tasks as appropriate.
  6. Are there any Performance Management (PT) requirements?  Add PT tasks as appropriate.
  7. What are the Documentation (DO) requirements?  Add DO tasks as appropriate.
  8. What are the Organizational Change Management (OCM) requirements?  Add OCM tasks as appropriate.
  9. What are the Training (TR) requirements?  Add TR tasks as appropriate.
  10. What are the Transition (TS) requirements?  Add TS tasks as appropriate.
  11. What are the Operations and Support (PS) requirements?  Add PS tasks as appropriate.

Now that you’ve identified all the tasks you need, consider how you want to approach your project.  Can you use the traditional OUM WBS approach or do you need to configure your workplan a little differently.  The possibilities are endless, but that’s a discussion for my next blog.

Monday Jun 16, 2014

OUM Success Story: Multi-Product Implementation for a Leading Travel and Transportation Client

More success! Or in honor of the 2014 World Cup in Brazil we should say: "¡GOL!"  As follow-on to my previous blog entry on the OUM Success Quote, here we have an example of how OUM was used successfully on a highly complex, multi-product project.

Project Profile:  A leading Travel and Transportation Company increased customer satisfaction and streamlined accounting functions through an implementation of Oracle E-Business Suite, Oracle Business Intelligence Applications, and Hyperion Solution. 

Use of OUM provided significant value to the project by providing the framework to establish an Integrated Project Plan: Using the same phasing and terminology on the overall project workplan for the separate E-Business Suite, OBI EE / OBIA, and Hyperion project partitions, enabled the project to leverage an Iterative and Incremental approach while enabling a complete view of the major milestones and touch points between the different partitions.

One aspect of particular significance is that this project utilized the technique of partitioning the project plan so that the work was divided into more manageable pieces. When dealing with large and/or complex projects it is advisable to split the functionality that is targeted to be implemented into smaller bits of effort.  We call these partitions in OUM, but they can also referred to as workstreams, subsystems, pillars, etc..  No matter what they are called, the whole idea is to logically break up the work, while still allowing for a common approach and integration of the tasks at key points in the project.  As you can see, the result on this project was a successful implementation and a very satisfied client.  

Do you have an OUM project success you would like to share?  Please let us know in the comments. 

Thursday May 29, 2014

Success Quote: A Hybrid Approach for Success

We recently received this quote from a project that successfully used OUM: “On our project, we applied a combination of the Oracle Unified Method (OUM) and the client's methodology. The project was organized by OUM's phases and a subset of OUM's processes, tasks, and templates. Using a hybrid of the two methods resulted in an implementation approach that was optimized for the client-specific requirements for this project."

This hybrid approach is an excellent example of using OUM in the flexible and scalable manner in which it was intended. The project team was able to scale OUM to be fit-for-purpose for their given situation. It's great to see how merging what was needed out of OUM with the client’s methodology resulted in an implementation approach that more closely aligned to the business needs.

Successfully scaling OUM is dependent on the needs of the particular project and/or engagement. The key is to use no more than is necessary to satisfy the requirements of the implementation and appropriately address risks. For more information, check out the "Tailoring OUM for Your Project" page, which can be accessed by first clicking on the "OUM should be scaled to fit your implementation" link on the OUM homepage and then drilling into the link on the subsequent page.

Have you used OUM in conjunction with a partner or customer methodology? Please share your experiences with us.

About

OUM Logo
The Oracle® Unified Method (OUM) is Oracle’s standards-based method that enables the entire Enterprise Information Technology (IT) lifecycle.

Read:

· Brief

· White Paper

· Customer Program Data Sheet

Connect:

· OUM on Twitter

· OUM on LinkedIn

Search

Archives
« May 2016
SunMonTueWedThuFriSat
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
    
       
Today