by Josh Yeager, Swift SoftwareOur development team uses an “agile” software process, which means that we work in a series of two-week plan->code->test->polish iterations. As we complete each iteration, we install a small new feature set on our internal production server for alpha testing. Each iteration completes a small portion of the overall development plan. After two to ten iterations, a whole set of features that have passed QA are designated as complete, and we build a final release and announce it to our customers. Our JobTraQ system manages this process for us in several ways. First, it manages our feature wishlist and roadmap. We have a parent project called “Future”, which contains subprojects that stage all of our feature ideas, enhancements, and strategic goals that are not on our immediate roadmap. A second project is called “Planning Queue”, and that project contains all of the tasks and projects that we plan to complete in the next two releases. We simply drag and drop the appropriate features into this “Planning Queue” project as we approach the iteration they will be developed in. Over time, our product management team prioritizes these items, plans their details, and reviews them with the development team to ensure they are technically sound. We work together to refine the time estimates and identify possible problems, so that all the basic details are decided by the time we’re ready to start working on each task. Second, JobTraQ manages our iterations. At the start of each iteration, the development team sits down and pulls the top items from the planning queue into a new project for the iteration. They select a set of tasks that can be completed within a two-week iteration, and then they plan those tasks in detail. All of the decisions and designs that they create are recorded in the JobTraQ tasks. Then, throughout the iteration, they track their progress and time spent in those tasks, record notes about their designs and code, and close the tasks when they are complete. To help usall stay coordinated, JobTraQ sends email notifications to the team when tasks are updated and closed, and we have a “burn-up” chart report that is sent to the team every day to compare our closed tasks to our goal. Example Burn Up ChartThe third thing that JobTraQ manages is customer support. When a new email request comes in, we use the new beta version of our two-way email processing feature to automatically create a task for the request and log the time that it came in. Then, as our support team and the customer reply to each email, all of the replies are logged in that task. Screenshots or attached files are also extracted from the emails and attached to the task. When the issue is resolved, the task is closed. Along the way, JobTraQ email notifications inform the team about the state of the active support cases, and the support task list reminds us about support requests that have not been resolved and questions that the customer has not replied to in a while. These tools help us ensure that no customer request is forgotten or mishandled. We use the same process for support phone calls, although we have to update JobTraQ manually after each call. The common thread among all three of these processes is that JobTraQ holds all of the information about our plans and our current work, as well as the status and progress of the tasks that we are working on. As a result, we almost never lose track of a project or request. We don’t forget about our bigger plans while we’re working on the details. And we can predict and evaluate our development timelines, support responsiveness, and team productivity. All these benefits are extremely helpful to me as the product leader and to the individuals and teams that work on our product. In future posts, we will be discussing the ways that we use JobTraQ to manage other parts of our business, and we may even highlight some of our customers’ processes if anyone is interested in sharing. As always, if you have any questions, please comment below. If you are in need of a full-featured Task Management software tool - I recommend you check out JobTraQ. Take a tour of the product or request a demo. Trust me - it will be time well spent. - Brad Egeland
Call all PMs - The Project Butler is ready to help you create meaningful project schedules for your project. By taking you through it's automated Q & A process, you can get approximately 80% of your project plan created for you. But if you don't learn about it, you'll never take advantage of it. The third and final scheduled webinar for this new product is scheduled for 4/9/12 at 10am PDT. I've taken it - and it's definitely worth the one hour of your time. It's free AND you'll earn 1 PDU for your time. Sign up here to sit in on this excellent session.
Managing the project team and maintaining strong communication with the project customer can consume most of the PM’s time that is allocated to the project. Needless to say, there are a lot of tasks and much effort that goes into what sounds like a fairly simple activity. Well….it’s not – I have 9 kids and I can tell you that managing a project team and keeping the project customer happy and focused is harder than keeping 9 kids managed and focused. I’m not complaining - both are rewarding in very different ways…. So, we – as project managers – must manage all these different skills sets and, of course, egos. While doing that, we must also ensure that we’re doing everything possible for our project customer and keeping their confidence and satisfaction level high. Remember – our approval rating with the project customer is still one of the three key determiners of project success…so don’t take that part of the responsibility lightly. Stick with basic best practices We must do weekly status calls with our customer and we should always provide our customer and team with revised weekly project schedules and up-to-date status reports – both of which are great tools to use to drive the weekly status call or meeting with the customer. To that end, I always plan an internal call or meeting with my team one or two days prior to the weekly call with the customer so I can ensure that everything is up to date. If I’m working with a collaborative PM tool, that means my team must be in there in advance make sure their tasks and info are up to date as well. Who will you collaborate with? Now consider this…in a collaborative project environment who all should be involved in those collaborative activities? The project sponsor? Yes, probably – especially if they are hands on and want that type of access. Some don’t, but when they do it’s more of a help than a hindrance, in my opinion. What about other external entities? Which external entities need access to the platform to view, update and close tasks? Which additional project resources outside of your immediate team and possibly the project sponsor should have access to make changes to their tasks in the project schedule and the issues that have been assigned to them in the issue management tool? That’s can be a tougher call because it can really open the project manager up to more effort, more tracking, more oversight, and more babysitting depending on how reliable these external project entities are and how accountable they are to maintaining useful information in the online tool. If most are updating their own tasks and two people are constantly slacking, then you may rely on their updates only to find that you walking into a status meeting with only 80% accurate information. When you are considering opening the collaborative issue and project tracking platform up to the entire team – meaning all resources and stakeholders beyond just your immediate delivery project team – education will definitely be in order. Kickoff the project by setting expectations for all involved as to how you will manage the project and how you expect information to flow from them into the tool and to you. It’s very important that you make them own their own tasks and drive home the concept that without their accurate weekly updates, your project information will not be accurate and the project and customer may suffer as a result. For issue management and project tracking on your ongoing engagements, check out Gemini. Gemini is extremely flexible as a collaborative project tracking and issue-tracking tool and gives the project manager and team a full-featured dashboard for great oversight into ongoing project and issue status.
Below is the text from resolution SR0255 which passed in October 2007 in the state of Illinois - officially declaring April 1st every year to be Cheap Trick Day. Celebrate tomorrow by playing Cheap Trick music loud and often to celebrate one of the greatest bands of all time. Thank you....
SENATE RESOLUTION
WHEREAS, One of the most prolific musical groups to come from the State of Illinois has been the rock group Cheap Trick; and
WHEREAS, Cheap Trick's roots lie in Fuse, a late-1960s Rockford band formed by Rick Nielsen and bassist Tom Petersson; during the early 1970's the band toured throughout the State, performing at every State university in Illinois; and
WHEREAS, Cheap Trick signed with Epic Records in 1976, releasing their self-titled debut in early 1977; the record sold well in America; however, the group became a massive success in Japan, going gold upon release; later that year, the band released their second album, "In Color"; due to their constant touring, the record made it into the U.S. charts, peaking at number 73; and
WHEREAS, The band realized that they were virtual superstars in Japan when they toured the country in early 1978, selling out the Budokan Arena; the Budokan Arena concert was recorded for a television program, which ended up becoming an album that appeared after their third album, 1978's "Heaven Tonight"; Heaven Tonight led to their first Top 100 single, "Surrender," which peaked at number 62; the live performances on "At Budokan" resulted in their commercial breakthrough in the U.S.; the album stayed on the charts for over a year, peaking at number four and eventually selling over three million copies; a live version of "I Want You to Want Me" pulled from the album became their first Top Ten hit; later that year, the group released their fourth studio album, "Dream Police"; the album also went into the Top Ten, selling over a million copies and launching the Top 40 hit singles "Voices" and "Dream Police"; in the summer of 1980, the group released an EP of tracks recorded between 1976-1979 called "Found All the Parts"; and
WHEREAS, Petersson left the group in the summer of 1980 after recording the album "All Shook Up"; he was replaced by Pete Comita, and shortly thereafter Jon Brant; the first album recorded with Brant was "One on One", the group's seventh album that appeared in 1982; The album was followed with "Next Position Please", released in 1983, "Standing on the Edge" in 1985, and "The Doctor" in 1986; Petersson rejoined the band in 1988 and began working on a new album; the resulting album, Lap of Luxury, was a platinum Top 20 hit, featuring the number one song "The Flame" and a Top Ten version of Elvis Presley's "Don't Be Cruel"; "Busted", released in 1990, peaked at number 48 on the charts; and
WHEREAS, In 1994 Cheap Trick released "Woke Up With A Monster"; the record spent two weeks on the chart, peaking at 123; That same year, they released a sequel to At Budokan, entitled Budokan II; the band opened for The Smashing Pumpkins in 1995 and the group performed on the 1996 Lollapalooza tour; That same year, they released the box set Sex America Cheap Trick to good reviews; early in 1997, the group released "Baby Talk on Sub Pop", which was followed by "Cheap Trick", their critically acclaimed debut for Red Ant/Alliance in the spring; in 1998 the band established their own record company, Cheap Trick Unlimited; they toured behind the re-mastered re-releases of Budokan: the Complete Concert, and their first three records; the tour resulted in the live effort "Music For Hangovers"; in 2001 the band produced their album "Special One"; their latest album, "Rockford", was released on June 6th, 2006; and
WHEREAS, Cheap Trick has performed over 5000 live performances, including USO tours in 12 countries with the 1st Airborne Rock and Roll Division; they have made 28 albums and have sold over 20 million records; their songs have been featured on many television shows, such as That 70's Show, The Colbert Report, and ABC's Sons and Daughters, and many movies, such as Top Gun, Daddy Day Care, Caddyshack, and Fast Times at Ridgemont High; the band has appeared on the cover of Rolling Stone magazine and has been named by Rolling Stone in their Top 10 Greatest Live Acts and Top 100 Greatest Songs lists; the band performed on Saturday Night Live in 1981; their songs have been covered by many famous artists, such as Chris Issac, Dwight Yoakam, Smashing Pumpkins, Alice Cooper, and many others; the individual members have produced songs for Kiss, Aerosmith, Motley Crue, and John Lennon, among others; and they have been commemorated with a special Rockford Illinois Vehicle Sticker in 2007; and
WHEREAS, Despite their monumental success in the music industry, Cheap Trick's band members still consider the City of Rockford and the State of Illinois to be their home; therefore, be it RESOLVED, BY THE SENATE OF THE NINETY-FIFTH GENERAL ASSEMBLY OF THE STATE OF ILLINOIS, that we designate April 1 of every year as Cheap Trick Day in the State of Illinois; and be it further RESOLVED, That suitable copies of this resolution be presented to Rick Nielsen, Robin Zander, Bun E. Carlos, and Tom Petersson as a symbol of our esteem and respect.
I suggest your check out Comindware and try their 30-day fully-functional trial of their new workflow automation software. It's free and it supports an unlimited number of users, tasks and subtasks. The graphical Workflow Builder enables visual drag-&-drop design and editing of workflow processes — no IT programming or technical expertise required. Go to http://www.comindware.com to check it out and signup for the free trial. Your feedback to them is welcomed on the site.
Recently I was brought in to manage a data warehouse IT project for a global software giant (name withheld to protect the innocent…and my client). I did the usual stuff since the project had already been somewhat defined…I grabbed the statement of work and any pre-engagement documentation I could find, I talked to some of the stakeholders, got an idea of the resources I’d be working with, was able to get my hands on the estimate (hours and dollars) for the project, and then sat down with my project scheduling tool of choice. And I sat. And I sat. Where to start? I hadn’t managed a project just like this ever. And I hadn’t managed a project somewhat like this in a while. I hate this part…building the schedule from scratch or taking a recent schedule and starting from there only to dismantle it and end up with something far different…but still maybe not right. If only there was an interactive tool that could help me build a good schedule from the start that I could then tweak along the way. You know, something that would get me 80% there….and I do the rest. Good news…there actually is such a product. It’s called The Project Butler. Designed and developed by adaQuest, this tool uses some interactive Q & A to get you on the path to a great project schedule. It will use the answers you give to build a framework of pre-defined tasks into your schedule. After a few minutes of interacting with the tool, you have a workable project schedule that is nearly complete – you put the finishing touches on it and you’re ready to kick off the project. No more headaches, no more wondering where to start, no more frustrations during the first month of the project as you work and re-work the schedule to get it to where you want it. Don’t take my word for it…adaQuest is offering a free webinar on this new product on three different dates. It’s only one hour and it will be well worth your time to check it out. Times are 10-11am PDT on 3/26/12, 4/2/12, and 4/9/12. Go here to sign up for one of the three sessions…you won’t be sorry.
In Part 1 of this six-part series on issue management we discussed understanding our users and project types in terms of how we go about managing project issues. In Part 2, we discussed the practice of identifying and understanding the business processes that are part of the customer’s organization on the projects we manage. Now, in this third part of the series, I’d like to discuss the how we determine the data requirements for our issue management and our change control needs on the projects we manage. We capture issues, but what else do we need to capture? What data is needed to fully understand the issues, track them, assign them, and ultimately resolve them? What data do we need to capture and track for change requests and change orders on the projects we manage? All of these are key questions and all highlight the fact that the data we capture is critical to the ongoing nature of the work we do and report on for these engagements. Without the right data, what are we tracking? How can we know that we’re working on the right stuff and resolving the right issues? What issue info do we need? What is critical to capture when we’re performing issue tracking, management and resolution? First, we need to know the normal who, what, and why information. Who is reporting, who and what is affected, what the issue is at a high level and why it has been reported…meaning basically what are the symptoms or problems that brought it to someone’s attention. We need to know if it’s a showstopper, top priority issue or if it’s a small bug that can be taken care of with the next release or the next batch of work that gets performed. What else do we need? As we perform further analysis of the issue, we certainly need to capture additional detail – much more than the initial high-level detail we captured when the issue was first reported. We need to capture dates as well. When was it reported, when does it need to be resolved, when do we think it will be resolved…realistically. Next, we need assignment and accountability information. Who is the issue assigned to – which individual or group? And finally, we need to understand how we’re going to test this issue upon resolution to know that it’s resolved and ready for implementation. Along with that, we need to capture customer signoff and approval including dates for these. What change request info do we need? Does the change request info differ from the issue information we must capture, track and report on? Well, yes and no. Basically, it’s the same. However, since change requests concern work that is to be performed beyond the original scope of the project, there is definitely a financial aspect to them. Estimates may be gathered for issues – and likely they will be. But they MUST be for change requests because they’ll be affecting the bottom line on the project. The budget will change as a result of change requests and often the customer must pay additional funds so there’s documentation, accountability and customer approval of any effort and cost estimation that goes into the change request. Beyond the cost info, most other key data will remain about the same – we still need to track the who, what, why, and when. It still must be assigned, tested and implemented. That’s why issues and change requests are generally very closely related and are often tracked together and reported together on project engagements. If you’re looking for a solid enterprise issue management tool, check out Gemini. Gemini gives maximum flexibility with minimal effort to manage real world problems efficiently and quickly.
Well, there may be trouble in paradise again. The iPhone 4 had an antenna problem and now it seems that the iPad 3 overheats. Not to the point of not being functional, just pretty hot to the touch. Users are complaining and tests are confirming. When used intensely for 45 minutes straight, the new iPad reaches temperatures as high as 116˚. That's 13˚ hotter than the iPad 2, though it's still 24˚ cooler than a sauna.
Apple isn't apologizing or planning to do anything about it. Their official stance is, if you have a concern contact AppleCare.
To me, the customer relations aspect of project management and consulting is a top priority. I goes right along with effective and efficient communication as the most important acts that the project manager or consultant must carryout throughout the engagement. I pride myself on excellence in the customer relationship area of project management. I certainly don't do all things perfectly. Far from it. But when it comes to managing the customer, interfacing with the customer, understanding their needs, and doing whatever I can to meet those needs, I believe I am always giving 110%. I may not be always getting it exactly right, but I know I’m always trying - and generally, I see that reflected in the feedback I get from my customers. That doesn't mean that every engagement goes well.... and it certainly doesn't mean that every customer is happy with me and that none have complained. They have...and I do tend to take it personally because of the way I always try to approach the customer. If you find yourself on this situation or if customer relations are not your forte, what do you do to try to mend a strained relationship with a customer? Something has to be done obviously or the customer's frustration level and dissatisfaction will likely only mount. Soon you may be shown the door on the project and even with your company if the customer starts calling your CEO....and some customers just may do that. Let’s lay this out again – you’re project is having issues or you’re having customer issues and you have a strained relationship with the customer. The project may not be on the verge of collapse, but your relationship with the customer definitely is. What do you do? How do you get back to a reset point with them? How do you win them back over to your side? Based on my own knowledge of managing customers, as well as any difficulties I’ve encountered with customers and discussions I’ve had with other project managers with troubled customer relationships, I’ve narrowed the actionable responses to these three: Have a frank discussion with the customer I’m a firm believer that the best thing you can do is go directly to the offended or dissatisfied party. It’s your best chance to get real, solid information on what’s wrong with the situation without running through any he said, she said scenarios. Go in with a few questions in mind… - What is your opinion of the status of the project?
- How do you feel about the way the project is being managed?
- Are there issues or concerns that you feel aren’t being adequately addressed?
- Are there members of the project team that are specifically causing you concern and why?
After you get some real answers to those questions, take it from there. Project managers are creative problems solvers – you should be able to unearth some information from one or more of these questions or similar questions. Involve your senior management If you feel like you can’t make any discussion progress with the customer, take the leap and sit down with them and someone from your senior management. Do it before they sit down with your senior management by themselves. Take the initiative to schedule this meeting so that you are on the inside of the information-sharing process … not on the outside looking in. Ideally, this will be a PMO director or even a CEO depending on the size of your organization and the visibility of the project (or the whininess of the customer – that’s sometimes a factor!). Formally present a new course of action If you feel like you can make some progress with this customer and if you think (or know) that some of their discomfort is due to their interpretation of how the project has been run, then by all means set up a reset point meeting. Gather all critical parties and take it back to a kickoff meeting type discussion. Review – or revise – how things are going to be done on the project. How project status will be reported going forward. How financials will be managed and reported. How issues and risks will be managed, assigned, and worked. How meetings will be led and what will be covered. Do everything you can to get that customer back to the point where they are comfortable that everything on the project is under control – your control – and that their needs will be addressed. Summary No matter what, the customer is unhappy and you have to do something. It may not even be your fault, but you can’t get past it with the customer until you resolve it. So resolve it in any way you can. And, in the end, if none of these three steps do the job – whether they are taken individually or stacked on top of each other – you may have face the reality that some other project manager needs to be at the helm of this project and manage this particular customer. Most situations can be turned around – but some simply can’t be. One key thing that any project manager or consultant can do to help ensure good customer relations is to provide an accurate project schedule at the beginning of the project and throughout. One great product that can help you get there is The Project Butler from adaQuest. Through a Q&A type situation, The Project Butler will help the project manager build a more accurate schedule so that he can kick the project off right. For more information, signup for one of these free hour-long upcoming webinars… Mon, Mar 26, 2012 10:00 AM - 11:00 AM PDT. Mon, April 2, 2012 10:00 AM - 11:00 AM PDT. Mon, April 9, 2012 10:00 AM - 11:00 AM PDT.
As a project manager, when I think of issue tracking, management and reporting I think…..spreadsheet. Or a table on the weekly status report. After all, that’s how I’ve always done it. It’s adequate. It’s there. Reporting from it isn’t really possible – save for the spreadsheet version where you can write tedious macros or do some sort and filter combos. But it’s not easy and it’s not fun. Fast forward to my introduction to Gemini. My PM life may never be the same. What does Gemini do you ask? Well…it does a lot. It does issue management very well. But it doesn’t stop there. Gemini can perform many of the functions that simply run your organization and help you stay in control. For example, Gemini can perform bug tracking, project and task management functions, help desk and ticketing, integrate with QuickBooks for your financial tracking needs, and plan and manage testing and quality assurance for you. Gemini has so much to offer so I probably didn’t test it out as much as I would have liked to…but I ran it through it’s paces for a few days and I better understood why organizations like Disney, Motorola, Domino’s Pizza, and Intel are already using various functionality within the Gemini Platform. It freakin’ performs…that’s why. I don’t have enough space here to write detail on all of its functionality, so let me briefly tell you about what it can do… Key functionality Issue management. Gemini provides you with full-featured issue management, tracking and reporting. This is where the wheels meet the road for Gemini – this is its key feature….and it performs mightily. I wish I had thrown out the spreadsheet and discovered it long ago. Project management. The PM functionality within Gemini focuses on task and time management, provides detailed dashboards to monitor project progress and activity, and does an incredible job of managing resources across projects and throughout the organization. Forget MS Project resource pools…go with Gemini. Bug tracking. Like issue management, Gemini provides the organization with great bug tracking oversight and reporting. Know what’s outstanding, know what’s a priority, and know what’s resolved. Unlike other organizations I’ve consulted with or worked for, Countersoft actually uses their own product – this product – for this functionality. That says a lot. Testing. While I didn’t get to really ‘test’ this feature out, the product purports to help with test cases and test plans and integrate with Visual Studio. Managing quality with Gemini will become a less complicated process in your organization. Financial analysis. Gemini fully integrates with QuickBooks making your financial planning and analysis a snap. No other comparable product offers this level of integration. Help desk functionality. Finally, Gemini can offer your organization it’s very own help desk and ticketing functionality…it’s built right into the Gemini platform. Again, I played with this functionality enough to see that it was very full-featured and could definitely perform what it proposes to do on their website, though I couldn’t run it too far through it’s paces in my limited testing. I was very impressed with this feature as it can be a critical tie-in to your support organization as you deploy project solutions. The inclusion of this functionality alone would sell me on the product. Pricing Countersoft offers pricing plans for their Gemini product starting at 5 users for $399 up to 1000 users for $4,899 with several incremental prices in between. There is even an unlimited user license for the larger organizations. Bottom line It was a pleasure to test out the Gemini product. Any one of the key functionalities would be valuable standalone products, but all these features are available to you for the one user-based pricing structure. Buy it for issue management and the help desk features and then reap the extra benefits from all the rest of its included functionality. The site offers a free 30 day team trial. You either download and install or take advantage of the instant on-demand trial. Both are available here.
|